Backup Exec 10 and windows update
- Thread starter armatage
- Start date
Although not directly answering your question, my 10pence worth.
IMHO you shouldn't be patching production servers like this (I'll assume they are as you back them up). If you (and the business) hold any value on your live systems, then patch a test box and wait for a week. I know this is not always feasible, but personaly I think at the very least you should patch one box, and leave it for at least one week, during this time visit MS Support groups, and keep and eye on technet to see if any new patchs have broke systems. Visit your software vendors sites also, see if they have encountered issues.
Gauge the risk, are you more likely to loose system availablility because of an exploit, or a patch? (there's much you can do to avoid the first) It's in the eye of the beholder I suppose though at the end of the day.
Hope this helps
IMHO you shouldn't be patching production servers like this (I'll assume they are as you back them up). If you (and the business) hold any value on your live systems, then patch a test box and wait for a week. I know this is not always feasible, but personaly I think at the very least you should patch one box, and leave it for at least one week, during this time visit MS Support groups, and keep and eye on technet to see if any new patchs have broke systems. Visit your software vendors sites also, see if they have encountered issues.
Gauge the risk, are you more likely to loose system availablility because of an exploit, or a patch? (there's much you can do to avoid the first) It's in the eye of the beholder I suppose though at the end of the day.
Hope this helps
Group policy is the best bet. Just setup a policy for your servers telling them to detect and download updates just not to install them. This way you can still get the updates ready to install but it won't disrupt any work going on until you want it to.