You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to provide some on-demand nopkg maintenance items in our Managed Software Portal.
Unfortunately, running these maintenance items also goes through the typical munki process with pre-flights, evaluating conditions, etc. The user prompts for our scripts pop up about 30-60 seconds after the user actually clicks the on-demand install.
In addition, running the maintenance item requires a connection to the our Munki server, which we don't have on the public internet. Therefore, the maintenance items will only work on our internal network, even though it is a nopkg that only runs a script.
I thought it would be cool to make it so that nopkg on-demand items run instantly without the typical munki pre-flight procedures and without a connection to the server.
The text was updated successfully, but these errors were encountered:
It's a reasonable request, and lines up with ideas I've had. No idea if/when I'd get around to implementing something like this since I don't currently have the need.
I'm trying to provide some on-demand nopkg maintenance items in our Managed Software Portal.
Unfortunately, running these maintenance items also goes through the typical munki process with pre-flights, evaluating conditions, etc. The user prompts for our scripts pop up about 30-60 seconds after the user actually clicks the on-demand install.
In addition, running the maintenance item requires a connection to the our Munki server, which we don't have on the public internet. Therefore, the maintenance items will only work on our internal network, even though it is a nopkg that only runs a script.
I thought it would be cool to make it so that nopkg on-demand items run instantly without the typical munki pre-flight procedures and without a connection to the server.
The text was updated successfully, but these errors were encountered: