Skip to main content

Windows Server Update Service (WSUS) Installation and Configuration

This tutorial will walk you through the process of installing and configuring WSUS Server 3.0 SP2 on Server 2008 R2, step by step.  WSUS is a great thing to have in an Active Directory environment as it saves precious bandwidth and allows a fine level of control in regards to client/server patch level.  You’ll need to do a little prep work before you can complete this lab successfully, so make sure that you’ve taken care of the following before jumping in.

1.)  Ensure that your Active Directory and DNS are functioning optimally and are healthy, this will save you a lot of headaches with workstations.

2.)  Download the latest copy of WSUS here, or you can try the newest WSUS 2010 version if you’re so inclined.

Once you’ve downloaded WSUS, you can kick off the installation which informs you that you need to install certain pre – requisites before continuing.  You can read more about them here, but the main roles that need to be installed are the Web Server IIS and Application Server role.  You can also install SQL Server ahead of time if you’re so inclined, but I’m going to work with the built in version that ships with WSUS as this is a small network.  Let’s jump into it – install the IIS and Application Server Roles from the Server Manager snap in.

Installing the Application Server & Web Server IIS Roles Server 2008
Once the Add Roles Wizard finishes installing IIS and the Application Server roles, give the machine a restart.  You’re now ready to start the process of installing and configuring WSUS.  Start the installer and accept the defaults – you’ll get to a screen warning you that you’re missing the Microsoft Report Viewer 2008 Redistributable.  Go ahead and pick up a copy here, install it, then restart the WSUS installation.
Full server installation including administration console
Now choose the default location of client updates – it’s best to store this on a separate volume if one exists, but I’m going to go ahead and pick the default location for this tutorial.
store updates locally wsus
And choose the default internal database option unless you are going to go with SQL Server.
install windows internal database on this computer
Use the existing IIS Default Web Site.
use the existing iis default web site
The installation wizard is done with the prompts at this point and get’s down to the good stuff.  Before finishing the wizard you’ll need to make sure that the firewall is configured correctly ( ports 8530 & 8531, ) that the WSUS server is able to connect to the upstream server, Windows Update in this case, and that you have credentials for a proxy server in your organization if applicable.   Once you’ve confirmed that you’re good to go, continue the installer.  Since we’re going to be using Windows Update to receive our updates, designate it as the upstream server.
designate the wsus upstream server
Designate a proxy server if applicable –  If you do not have a proxy in your organization, you can skip this part.
use a proxy server when synchronizing
Now hit the “start connecting” button to query windows update for relevant updates to your environment.
wsus start connecting
From here on it’s simply a matter of setting a sync schedule, and determining which updates you will be sending out to your clients.  Let’s choose a list of products that we want WSUS to manage :
choosing the products
Now let’s choose the classifications that we want to enforce in our environment.  It’s generally a best practice to enforce critical updates and security updates at a minimum – the rest is up to you.  I would advise to avoid having WSUS be in charge  of your driver updates unless it’s absolutely critical for compliance reasons, otherwise it can be a bit of a headache to have 250 workstations bluescreen on a Monday morning because the video driver that was pushed out is glitched
choose the wsus classifications
Set a schedule for synchronization – you can have this manually requested or automatic.  Since we all aspire to be lazy admins, let’s go ahead and set it for automatic synchronization on a sensible schedule ;)
set a wsus sync schedule
You’re done and your brand new WSUS server is ready to do it’s thing – let the first sync begin and you can start configuring your organization as you see fit.  Make sure to review the “what’s next” option to better familiarize yourself with WSUS and how best to apply it to your environment.

Comments

Popular posts from this blog

Creating NLB Cluster Windows 2008 Server

Creating an NLB Cluster There are three key steps to creating an NLB cluster in Windows Server 2008: Install the NLB Feature into Server 2008 on each host that you will add to an NLB cluster. Use the New Cluster wizard to create the cluster and add the first host. Use the Add Host wizard to add one ore more nodes to your cluster Installing NLB in Server 2008 This is extremely easy. First you run Server Manager, and select Features from the tree and click on Add Features: From the Add Features wizard just select Network Load Balancing and click Next: Finally from the Confirm Installation Selections click Install: After a few seconds, NLB will be installed on the first host. You need to repeat this installation on each host you plan to add to your NLB Cluster. Installing the NLB feature does NOT require a reboot, but removing it does. Creating your NLB Cluster Once NLB is installed, you create your cluster by first bringing up the NLB Cluster Manager: The right c...

How to Clean Up Your Messy Windows Context Menu

One of the most irritating things about Windows is the context menu clutter that you have to deal with once you install a bunch of applications. It seems like every application is fighting for a piece of your context menu, and it’s not like you even use half of them. Today we’ll explain where these menu items are hiding in your registry, how to disable them the geeky way, and an easier cleanup method for non-geeks as well. Either way, your context menu won’t look like this one anymore… Cleaning the Context Menu by Hacking the Registry If you want to clean things up the truly geeky way, you can open up regedit.exe through the start menu search or run box, and then browse down to one of the following keys… sadly the context menu items are not stored in a single location. Most of the menu items that used for all files and folders can be found by looking at one of these keys: HKEY_CLASSES_ROOT\*\shell HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers HKEY_CLASSES_...

Use Portable VirtualBox to Take Virtual Machines With You Everywhere

Install Portable VirtualBox to an External Drive First, get started by downloading the Portable VirtualBox installer from vbox.me . Run the downloaded file and extract it to an external drive or wherever else you want to store your portable VirtualBox system. You can always move it later, if you like. Launch the Portable-VirtualBox.exe program from here and you’ll be prompted to download and install VirtualBox’s program files on your external drive. The tool can automatically download VirtualBox’s files for you. After it does, click the OK button to unpack them. If the full version of VirtualBox is already installed on your computer, you won’t see this screen and VirtualBox will just open instead. You’ll want to uninstall VirtualBox first or set this up on a computer without VirtualBox installed. Launch the program again after it finishes unpacking files. After you agree to a UAC prompt , you’ll see the standard VirtualBox window. A VirtualBox system tray icon...