(imported topic written by SystemAdmin)
I have an issue with a McAfee rollout that requires 2 new files to pushed to the clients
these files need to be rolled out with 1 hour between files, is there a nice way in BES
to wait for 1 hour in an action script, or would I be better off pushing the second file
1 hour later ?
(imported comment written by BenKus)
You can do something like this:
parameter “startClock”="{now}"
pause while {(now - (parameter “startClock” as time) < 1*hour)}
It is not particularly nice because the agent won’t do anything else while it is running this action, but it will wait an hour.
Ben
(imported comment written by jessewk)
Hi Mark,
Ben’s idea will probably result in undesirable performance characteristics because the client won’t be able to do anything else during the hour while the action is running.
I think you should write a registry key at the end of the McAfee rollout task that contains a timestamp. Make the second action only relevant when the key exists and the value of the timestamp is one hour less than ‘now’.
I believe there are some other ways you could create a baseline, and some re-applicability behavior, and inspect the time the first action finished, but my other way seems easier at the expense of being slightly “dirtier”.
Jesse
(imported comment written by SystemAdmin)
Im getting a failure on the code below, so the first one ran and then it failed before the second one
Action script output
Completed waithidden __download\Setup_agent_events.exe /s
Completed parameter “startClock”="{now}"
Failed pause while “{(now - (parameter “startClock” as time) < 1*hour)}”
PS: yes I agree that this would cause undesirable performance characteristics, I like the second option, but in this situation
I only have a limited number of systems (100)ish and this is a one shot
(imported comment written by SystemAdmin)
go it… it doesnt like the Quotes… in the pause line
parameter “startClock”="{now}"
pause while {(now - (parameter “startClock” as time) < 1*hour)}