Again and again I miss "force run": A new bundle version must be immediately available after an update. (immediately after login - not after a refresh.)
by: Testus N. | over a year ago | Application Mgmt
by: Testus N. | over a year ago | Application Mgmt
Again and again I miss "force run": A new bundle version must be immediately available after an update. (immediately after login - not after a refresh.)
by: Testus N. | over a year ago | Application Mgmt
Comments
I couldn't agree more!! Waiting for a ZCM refresh has often forced us to use a vbs file so that it can be edited to achieve an immediate update of the installation.
"On Refresh" in the ZCM works exactly like "Force Run" in ZDM. It will run the next time the User Logs in or ZENworks refreshes. This is exactly what ZDM did.
"On Login" is new and may cause the delay you noted since the Login occurs before ZCM checks in.
ZDM never had an "On Login" only event....
Scrolling through again. In addition to may prior comment, make sure that "Assignment Optimization" is disabled to allow new assignments to appear quickly. The feature is generally only needed for the largest of customers and only if they refresh all their devices at the same exact time. In general, the setting saves less than 1/10th of a second per device, though the savings could vary from implementation to implementation.
Hello, Craig,
Thank you for the information. Where can I configure "Assignment Optimization"?
We need the ZfD "force run" very rarely. But when we need it, we miss it very much . . .
""On Refresh" in the ZCM" works very well.
It does not work if the client does not know the new version of the bundle yet.
I always calculate with a delay of one day. And in some cases this is too late (software update at a certain time: for example client upgrade after database upgrade).