Symantec Management Platform (Notification Server)

Any job that is a sequential software delivery task will not install after the user requests it until the next configuration update. We have scheduled this to happen every hour, so if a user requests the installation it won't start until the next configuration update. Is there any way around this besides having the user reboot after the request?

You could force an update from the console or you could have them request and updated config through the Agent UI.

I always get nervous about asking an end user to do too much. When you say force an update from the console, how would you do that? I was thinking of calling the update configuration in the first part of the job but it doesn't even look at the job until the next configuration update.

If you have the power management feature enabled in the agent, you can (unfortunately, it's only one PC at a time) right click on the pc and select power management and then choose update configuration (it's checked by default).

Something isn't right there Tony. When a user requests an installation from the Software Portal what happens normally is:

* hidden collection with 1 workstation is created
* hidden task linking installation to workstation is created
* configuration update is triggered for the workstation

We have this working fine for both normal and sequential tasks, although sometimes the config update can be a bit slow. In those cases we can lookup the workstation in any old collection, right click it, go to Power Management and select Update Client Configuration. That will cause the workstation to refresh its information.

Greetz,