There are only two changes you need to make in order to install SUS on your users' client machines. But don't try this at home if your PCs are not running XP or Windows 2000 Professional. Here are some installation pointers from Douglas R. Spindler, president of the San Francisco Networking Technologies User Group.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Step 1: Configure the client while the SUS server download is occurring.
Step 2: Remember that the client can only be run on Windows 2000 Professional or Server; Windows XP, Home or Professional; or Server 2003.
Step 3: The client software can be found here on Microsoft's Web site. It's a quick download at 1MB WUAU22.MSI. But note that, if the client is running Windows 2000 Pro, you will need to install Service Pack 2 first. SP3 includes the SUS client, so you can skip the install for those machines. XP requires the client unless you have SP1, which includes the client. Server 2003 machines all include the client.
Step 4: Since you are not using Active Directory, you will need to make a registry modification. Copy the following text into Notepad and replace <YOUR DNS NAME OR IP ADDRESS> with your SUS server's IP Address. This is on the third and fourth line; be sure to leave the quotes.
Windows Registry Editor Version 5.00
"WUServer"="http://YOUR DNS NAME OR IP ADDRESS"
"WUStatusServer"="http://YOUR DNS NAME OR IP ADDRESS"
Step 5: Save this as a .reg file. We called ours "SUSregchanges.reg."
Step 6: Install the reg file modification by double clicking on the reg file icon. You will be warned that the reg file is being modified.
Step 7: Accept the modification.
Step 8: Reboot the client.
A word of warning: as new critical updates are downloaded by the SUS server, they will appear in the Approve Updates window on the SUS server. "New" unapproved updates appear at the top, above previously "approved" updates. Here's where you have to be careful; updates to previously "approved" updates appear below the section of "approved" updates and are unchecked, waiting for your approval. Below this section are the entries that appeared in previous approval sessions as "not approved." It would have been nice to have all of the items needing approval together rather than being broken apart by a section of "approved" in the middle. To avoid this trap, scan the list from top to bottom, looking for unchecked boxes.
That's it! Your test SUS server now is ready to supply your clients with the updates you just approved. The clients are configured to contact the SUS server at 7 a.m., download and then install the latest critical updates, and reboot the client (if needed).
About the author: Douglas R. Spindler is the Active Directory project coordinator at Lawrence Berkeley National Laboratory and a technology consultant living in the San Francisco Bay area. He holds an MCSE + Internet certification and is a freelance writer, lecturer and president of the San Francisco Networking Technologies User Group. He can be reached at firstname.lastname@example.org
FOR MORE INFORMATION
SUS Crash Course.