If I want a script to run on all machines. It is just a registry change. Can I choose 'do not run on a schedule' and Also run once at next client checkin. So when the clients check in the script will run even though I have do not run on a schedule checked?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Yes that's correct. Since it's an offline script they need to update their scripts first though.
Answered 01/13/2012 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
As a general reminder- run on all machines is typically a bad idea. (Which is wht the UI asks if you're really sure)

For example, would you want that same registry entry applied to WinXP & 7, Servers and Workstations, Mac and Windows?

Sure a registry hack fails easily on the Mac and no harm done, but you get the idea; "All machines" really does mean *all machines*, and what makes sense today and surprise you down the road when it does something unexpaected or unwelcome.
I recommend using it very sparingly and carefully.
Answered 01/15/2012 by: cblake
Red Belt

Please log in to comment
0
ORIGINAL: cblake

As a general reminder- run on all machines is typically a bad idea. (Which is what the UI asks if you're really sure)

That is true. The reason for this is that with offline scripts you are allowing the client to schedule itself instead of the konductor on the server side.

In this case we're using " Also Run Once at next Client Checkin" and I'm not sure if an inventory task from konductor is active while a script is running this way. If the task is active then this would be a safe scheduling option for all machines as it would implicitly be linked to konductor's resource scheduling.
Answered 01/15/2012 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity