Setup Windows Server Update Services - Revision history

Lars at 20:54, 27 June 2011

2011-06-27T20:54:02Z

← Older revision		Revision as of 20:54, 27 June 2011
Line 17:		Line 17:

	WSUS has no option to auto allow new updates to be accepted and given to clients, therefore each month (after Microsoft releases new updates) a Research Administrator must log into the WSUS server on Lancer and manually approve the new security updates.		WSUS has no option to auto allow new updates to be accepted and given to clients, therefore each month (after Microsoft releases new updates) a Research Administrator must log into the WSUS server on Lancer and manually approve the new security updates.



	[[Image:WSUS_Client_Diagnostic_Tool.tbz2]] - Windows exe which tests if WindowsXP has all required software installed for a WSUS client.		[[Image:WSUS_Client_Diagnostic_Tool.tbz2]] - Windows exe which tests if WindowsXP has all required software installed for a WSUS client.

			Note: Windows Update Software Services replaces [[Software Update Services]]

			== Disk Space Problems ==

	~~Note~~: ~~Windows Update Software Services replaces~~ [[~~Software~~ Update ~~Services]]~~		* If the update content directory or databases grow to the point where they fill up the disk drive or partition, operation of WSUS will be hampered. It will no longer be able to perform regular synchronizations (ie: download available updates from Microsoft) plus it may become impossible to migrate the files to a drive with more space by using the '''wsusutil.exe movecontent [destination path] [log file path and filename]''' command.
			* If the '''movecontent''' switch fails, then what you can try doing is installing another drive into Lancer, and then using a utility such as Symantec (Norton) Ghost to clone the existing WSUS drive to the new drive. After cloning has completed, shut down Lancer, remove the old WSUS drive, and restart. I did this in June 2011 when the 100gb HD filled up and had to be replaced with a 500gb unit.
			* An easy way to reduce the growth rate of the updates files is to limit WSUS to only consider updates for specific languages. In June 2011, I configured WSUS to only download updates for English and French.
			* To reduce disk clutter, you can use the '''Server Cleanup Wizard''' which is located in the '''Options''' tree menu item on the left side of the Update Service control panel.
			* When I changed the update settings to only update for English and French languages, the existing directory still contained all the previously downloaded updates for other languages. The '''Server Cleanup Wizard''' didn't delete them. To remove them, I launched a commandline window (Run As Administrator) and ran '''wsusutil.exe removeinactiveapprovals'''. After that, I ran '''Server Cleanup Wizard''' and it removed approximately 100gb's worth of files.

Hha13 at 17:09, 25 April 2007

2007-04-25T17:09:07Z

← Older revision		Revision as of 17:09, 25 April 2007
Line 24:		Line 24:


	Note: Windows Software Services replaces [[Software Update Services]]		Note: Windows Update Software Services replaces [[Software Update Services]]

Mmmark: /* Setup a Client to use WSUS */

2006-07-06T18:47:39Z

Setup a Client to use WSUS

← Older revision		Revision as of 18:47, 6 July 2006
Line 12:		Line 12:

	Registry file to uninstall:		Registry file to uninstall:
			[[Media:WSUS_uninstall.reg]]
	~~n/a~~

	== Monthly Maintenance ==		== Monthly Maintenance ==

Mmmark at 19:14, 27 June 2006

2006-06-27T19:14:47Z

← Older revision		Revision as of 19:14, 27 June 2006
Line 19:		Line 19:
	WSUS has no option to auto allow new updates to be accepted and given to clients, therefore each month (after Microsoft releases new updates) a Research Administrator must log into the WSUS server on Lancer and manually approve the new security updates.		WSUS has no option to auto allow new updates to be accepted and given to clients, therefore each month (after Microsoft releases new updates) a Research Administrator must log into the WSUS server on Lancer and manually approve the new security updates.



			[[Image:WSUS_Client_Diagnostic_Tool.tbz2]] - Windows exe which tests if WindowsXP has all required software installed for a WSUS client.



	Note: Windows Software Services replaces [[Software Update Services]]		Note: Windows Software Services replaces [[Software Update Services]]

Mmmark at 20:17, 26 June 2006

2006-06-26T20:17:40Z

New page

== Windows Software Update Services ==

Our local WSUS server is currently hosted on '''Lancer''' (because WSUS requires IIS) and directly mirrors all the updates available for Windows XP. The WSUS server can be administered through [http://lancer.iat.sfu.ca/WSUSAdmin/ http://lancer.iat.sfu.ca/WSUSAdmin/].

== Setup a Client to use WSUS ==

WSUS can be configured on any Windows 2000 SP3+ or Windows XP SP1+ by adding some registry information pointing automatic updates to our local WSUS server.
Note: In System Properties, the automatic update options will be grayed out once WSUS is configured.

Registry file to install:
[[Media:WSUS_install.reg]]

Registry file to uninstall:

n/a

== Monthly Maintenance ==

WSUS has no option to auto allow new updates to be accepted and given to clients, therefore each month (after Microsoft releases new updates) a Research Administrator must log into the WSUS server on Lancer and manually approve the new security updates.

Note: Windows Software Services replaces [[Software Update Services]]