Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Patchs distributing to all users
- Thread starter OLDMO
- Start date
grandpubah
MIS
Sure, just run Software update service on your server.
Jon
Jon
Yes, it's called Software Update Services from Microsoft.
It's basically the web update (Windows Update) but you can install it locally and force installations of the patches.
"In space, nobody can hear you click..."
It's basically the web update (Windows Update) but you can install it locally and force installations of the patches.
"In space, nobody can hear you click..."
Be wary of using this in a live environment, some patches can have detrimental effects on your workstations. Be sure that it is configured correctly, you do not want to apply every patch that MS bring out! Make sure that the patch has been fully tested with your environment before forcing it out to clients
I concur with DaFlex, be wary!
I recommend you never do automatic patches, always read exactly what is being patched, and check to see if anyone is having problems with the patches, especially on large server systems.
I have had to back out patches more than once because of problems with the patch. Anyone who applied Win NT SP6 (not SP6a) understands what is being stated here. That SP had to be patched within a day or two of its release becaus of the problems it caused to users (it is NOT NICE when your server crashes and can not be recovered after applying a patch). For critical systems, ALWAYS have a FUll backup before applying new patches, just in case.
Likewise, ALWAYS allow the system to back up the patch process so you can back out of the patch if needed. Note with care, that some patches do not have a capability to be removed because they make registry configuration changes, etc., that are not reversible, so ALWAYS READ THE PATCH INFORMATION FIRST. If your system does not use the recommended patched service, be careful of installing it.
Be aware that the "Automated Update" service offered by Microsoft is not fail safe, and sometimes recommends patches to software you may not even have installed, such as patches to Internet Explore 6, when you are running version 5, for example.
HTH
David
I recommend you never do automatic patches, always read exactly what is being patched, and check to see if anyone is having problems with the patches, especially on large server systems.
I have had to back out patches more than once because of problems with the patch. Anyone who applied Win NT SP6 (not SP6a) understands what is being stated here. That SP had to be patched within a day or two of its release becaus of the problems it caused to users (it is NOT NICE when your server crashes and can not be recovered after applying a patch). For critical systems, ALWAYS have a FUll backup before applying new patches, just in case.
Likewise, ALWAYS allow the system to back up the patch process so you can back out of the patch if needed. Note with care, that some patches do not have a capability to be removed because they make registry configuration changes, etc., that are not reversible, so ALWAYS READ THE PATCH INFORMATION FIRST. If your system does not use the recommended patched service, be careful of installing it.
Be aware that the "Automated Update" service offered by Microsoft is not fail safe, and sometimes recommends patches to software you may not even have installed, such as patches to Internet Explore 6, when you are running version 5, for example.
HTH
David
- Status
Similar threads
- Locked
- Question
