I don't think you can use GPO to tell computers to go visit Windows Update and get the latest stuff. However you can download the individual updates and install them to computers vis GPO. However the updates have to be in MSI format. Microsoft usually provides MSI's of service packs, but not individual updates.
- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-
SUS works great for pushing software updates and security patches. However,I do not recommend that you use it to push out service packs as it frequently locks up computers for hours.
What I have found to work best it to use Group Policies for Service Packs and then SUS for updates/patches. SUS is pretty straightforward and easy to configure. The first time you approve updates in SUS is going to be the most taxing to the Users. Because it will most likely install a large amount of updates that will get all machines on the same page. So you might have 1 or 2 computers have a slight error during the first push.
But after the first push, the new updates are fairly seamless.
swabs is right on the money. SUS works a treat. We have it rolled out to all 7 sites from our central server via a distribution server at each site (slow links). Only thing to watch is servers restart automatically during the update, which can be a bit disconcerting. We leave somebody logged onto them and that stops the reboot until you start using the session and it asks you whether to reboot or not. A hint I found useful, in the console where you approve the updates (
Well, you configure the client Automatic Updates and BITS-services using GPO's to pull it off the SUS server. So from Windows 2000 and up you can force the updates to the clients. There are ofcourse clients available for older systems. Only drawback is the lack of proper reporting, but overall it works great.
It still pulls, but is under the control of a policy. You import a template into the GPO, which has all the settings for your SUS. On 2000 clients and up this modifies the Windows Update client to pull from the SUS server according to the policy settings. You can tell the policy has applied on a client by looking in Control Panel at the Windows Update settings. They will be greyed out when SUS policy has applied. Users can sideline the reboot once, but next logon it will automatically apply 1 minute after logon if you set the policy that way.
First of all, SUS rocks. But it doesn't "Push" the updates to the client, the server broadcasts that the updates are available to the clients, and THEN they go and download/install from the server. I just had to clear that up for those of you who think they get "pushed" to the clients.
If you want to "Push" them to the clients, I suggest Systems Management Server (SMS) from M$ or ZENworks from Novell. They can do what SUS cannot, but cost money, whereas SUS is free.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.