Getting started with Microsoft Windows Server Update Services 3.0, Part 5: Configure Client

After 4 parts have passed, you have finished basic configuration on WSUS server. Next, you need to configure client computers to contact the WSUS server to get some updates. The best way is to configure from the domain group policy so that you only configure once. Then, the policy will be apply to all clients in the domain but this approach requires you to have an active directory in domain. In this post, I’ll show how to configure clients using group policy to get updates from the WSUS server.
Note: You can also configure clients that in a non-active directory, too. But I won’t cover in this article.

Sections

  1. Configure new group policy
  2. Load the WSUS Administrative Template

Step-by-step to configure client

Configure new group policy

  1. On the Active Directory server, open Active Directory Users and Computers.
    Active Directory Users and Computers
  2. Create a new OU (Organization Unit) called ‘TestOU’. In next following steps, I’ll create a new policy for this OU and assign clients to the OU.
    Create a new Organization Unit
  3. Right click on ‘TestOU’, select Properties. On TestOU Properties, select Group Policy tab. Then, create a new group policy object links by click on New and named as ‘WSUS’.
    Create a new group policy
  4. Edit this ‘WSUS’ policy by click Edit.
    Edit the policy
  5. On Group Policy Object Editor, expand Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update. You’ll see on the right side are policy that you can configure for Windows Update.
    Note: If you don’t see Windows Update, you may need to load WSUS Administrative template first. See the next section at the bottom of this post for detail steps.
    Windows Update policies
  6. I’ll configure only some of policies for Windows Update. First, I’ll configure how automatic updates works. Double-click “Configure Automatic Updates”.
    The Configure Automatic Updates Properties appears, select enabled and leave other settings as default. You can see more details of this policy by click on Explain tab. Click OK.
    Configure Windows Update policy
  7. Next, enable “Specify intranet Microsoft update services location”. You have to specify a WSUS server which the automatic update will contact for updates. In this example, I have already configured WSUS server on BKKWSUS001 and I have customized port so I need to type “http://BKKWSUS001:8530”. Click OK.
    Note: You need to specify port if you have customized WSUS on the installation.
    Configure Windows Update policy
  8. Next policy that I’ll enable is “No auto-restart for scheduled Automatic Updates installations”. This policy prevents auto restart when the updates has been installed. Instead, it’ll ask the current logon user whether to restart or not. Next, close the Group Policy Object Editor and TestOU Properties. Click OK.
    Configure Windows Update policy
  9. Back to Active Directory Users and Computers, move a computer to ‘TestOU’ as client of WSUS. In this example, I drag BKKMISC010 from Computers to ‘TestOU’ to be as a client computer.
    Move a computer to the OU
  10. There is a warning pop-up message about moving a computer will affect policy on the object that you’re moving. Click Yes to continue.
    Confirm policy change
  11. Now I have a client computer ‘BKKMISC010’ on ‘TestOU’ which has configured policy to get updates from WSUS server.
    Finish configure policy
  12. Back to WSUS server, open Microsoft Windows Server Update Services 3.0 SP1 by select Start -> Programs -> Administrative Tools -> Microsoft Windows Server Update Services 3.0 SP1.
    Expand Computers -> All computers. You’ll notice that still no computer connect to this WSUS server. What’s wrong? The answer is that a group policy that you’ve configured a few minutes ago hasn’t apply to the client computer yet.
    Open Microsoft Windows Server Update Services 3.0 SP1
  13. You can force the client computer to update the policy immediately by execute “gpupdate /force” on the client computer. In this example, I open command prompt and type the command “gpupdate /force” on BKKMISC010.
    Force update the policy now
  14. Back to WSUS server, click refresh. Now you’ll see there is a new computer but you can’t see any detail.
    New computer on was added
  15. To view that computer, change filter status to any and click refresh again. Now you’ll see the detail of the client computer.
    Change filter
  16. That’s it. You have finished setup both on WSUS server and client. On the next part, I’ll talk about setting up a WSUS on a disconnected network (No Internet connection).

Back to top

Load the WSUS Administrative Template

  1. On Group Policy Object Editor, right click on Administrative Templates and select Add/Remove Templates.
    Open group policy template
  2. On Add/Remove Templates, click Add.
    Add a group policy template
  3. On Policy Templates, select wuau.adm. Click Open and close the Add/Remove Templates. Now you should see Windows Update.
    Select wuau.adm

Back to top

Series Navigation<< Getting started with Microsoft Windows Server Update Services 3.0, Part 4: ConfigurationGetting started with Microsoft Windows Server Update Services 3.0, Part 6: Disconnected network (1) >>

4 Comments

  1. Fernando September 18, 2008
  2. Plumtart January 31, 2011
  3. Giovanni Moster November 17, 2011
  4. free online calorie counter July 1, 2012

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.