Computers, How to Guides, News, Windows, Windows Home Server

How to: Install Windows Server Update Services on Windows Home Server 2011 (Part 3)

WSUS

In the first part of this How To guide, we installed Windows Server Update Services on Windows Home Server 2011. Then in the second part, we set up our network computers to work with WSUS. With those two steps done, you can configure WSUS to support update delivery on your network computers.

Let’s start by logging on to your home server using a remote desktop connection. Now open the WSUS Administration Console. You can do this by clicking on ‘Windows Server Update Services‘ in the ‘Administrative Tools’ folder.

1. Set Up Your Computer Groups

This step will allow us to create a group policy for your computers. This policy will push updates to your computers based on the rules you create for each group. This could include a TEST group, DEV group, or a Home group – what you name the group should have meaning to understand the purpose of the group. You could have a PRODUCTION group, that will not push updates until you approve the updates. For my network, I created an ‘APPROVED-GRP’ where all of my network computers will have updates pushed automatically.

In the Left Pane, Open your Server, Open Computers, Open All Computers. Now click on the ‘Add Computer Group‘ in the Right pane.

Give your Group a name. I choose ‘Approved-Grp’. Now click Add.

This brings us back to the Admin Snap-in. Highlight the ‘Unassigned Computers‘ group, in the center pane, change the ‘Status‘ drop-down box to ‘Any’, and click the ‘Refresh‘ button.

Now, right-click on each computer and select ‘Change Membership‘ to move the computer to your automatic approval group.

Check the group to which you want to place the computer and click OK.

Click Refresh to see that your computers are no longer in the ‘Unassigned Computer’ group.

Highlight the ‘Approved-Grp’ group, and change the ‘Status‘ drop-down box to ‘Any‘, and click the ‘Refresh‘ button. Notice that your computers are now in the new group.

Previous ArticleNext Article
Started in the information technology field in 1984 maintaining main frame computers and switching systems - My first personal computer was an Atari 800XL with an ATR8000 tied in for some CP/M fun - Currently work for a fortune 500 company providing global IT services - In my 'spare' time, I listening to music and helping others learn how to use their personal computers.
  • justin

    Bobbyc,

    What can I possibly do wrong when there are no computers to be found by the WSUS?
    Ofcourse the view has been adjusted to see all computers, added or not and so on. 

    But still no joy.

    Cheers,

    Justin

    • bobbyc

      Justin,

      I’m sorry about that, I tried to stream line the process, but I see that was not a good idea.

      You may need to configure your network computer first.  Jump over to the tutorial section and start with step 2.  Once that has been completed, then you can do the step that is not working for you.    Here is the link.

      http://forum.wegotserved.com/index.php/tutorials/category/13-installation/

  • bobbyc

    Did any one else have the same problem as Justin?

    • Millenios

      I also have the problem, can see my networked clients when  running the refesh

      • bobbyc

        M
        Open the WSUS admin snap-in, select options in the left-pane, then in the center-pane select computers.  The select Use the Update Service Console.

        You can toggle between the two setting and see what happens.  I can see my system on both, but I can only change Membership when the top one is selected.

        Let me know if that helped.

        • Paul

          I too had the no clients found problem. I (lazily) had cut and pasted the the http://SERVER:8530 from the Part 2 web page into the client config. This seems to have added a trailing space – hence the client had an invalid WSUS address and the client was not found on the server. Editing the WSUS address on the client using gpedit and removing the trailing space resolved the issue.

        • Paul

          I too had the no clients found problem. I (lazily) had cut and pasted the the http://SERVER:8530 from the Part 2 web page into the client config. This seems to have added a trailing space – hence the client had an invalid WSUS address and the client was not found on the server. Editing the WSUS address on the client using gpedit and removing the trailing space resolved the issue.

  • Anonymous

    Patiently waiting for the fix to run WSUS on Windows HP and XP? Any idea when that will be coming?

  • FuXXz

    All steps work fine for me, but my win7 Pc´s make Windows Update 800B0001 error. What can i do ?

Subscribe to We Got Served

Get the latest news and reviews from We Got Served in your inbox. Simply add your name and email address below. You can unsubscribe at any time.

x