here is as far as i can see an issue with the option Deploy Immediately.
If you have all the patches downloaded and ready - e.g. like a software deployment, then option to deploy immediately to a number of boxes works fine.
But if there are patches to download - and the job has to wait until the Download In progress has finished, the patches job IS NOT started straight away, the boxes in the job have to wait until either
a) MANUAL service restart
b) MANUAL cfgupdate run
c) up to 90 minutes for refresh.
This might be okay IF you are not time bound OR do not have a large number of machines to manage. However if you do, then this is actually a rather large short coming and to be honest pushes us towards SYSTEM CENTRE!
I don't really see why this shouldn't be a big problem to fix..
All the JOB has to do is wait until the Status is Ready to Execute, then make a call to the local agent to run CfgUpdate.
Can you tell me if this is something that can be done?
Dan
If you have all the patches downloaded and ready - e.g. like a software deployment, then option to deploy immediately to a number of boxes works fine.
But if there are patches to download - and the job has to wait until the Download In progress has finished, the patches job IS NOT started straight away, the boxes in the job have to wait until either
a) MANUAL service restart
b) MANUAL cfgupdate run
c) up to 90 minutes for refresh.
This might be okay IF you are not time bound OR do not have a large number of machines to manage. However if you do, then this is actually a rather large short coming and to be honest pushes us towards SYSTEM CENTRE!
I don't really see why this shouldn't be a big problem to fix..
All the JOB has to do is wait until the Status is Ready to Execute, then make a call to the local agent to run CfgUpdate.
Can you tell me if this is something that can be done?
Dan