Discussion Locked

Windows Server Blog

0 helpful
505 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is page 2 of the discussion. Read the opening post

505 replies

by md.athifkhaleel

Here you will find WSUS Database Requirements for Windows 2000 & Windows 2003 Servers;

On Windows 2000: Install Microsoft SQL Server 2000 Desktop Engine (MSDE) prior to running WSUS Setup & install a security patch, http://go.microsoft.com/fwlink/?LinkId=47363 to MSDE to protect your WSUS server.

For Windows 2003: Although database software is required to install WSUS, it is not listed here because the default WSUS installation on Windows Server 2003 includes Windows SQL Server™ 2000 Desktop Engine (WMSDE) database software.

More on http://wsuswiki/WSUSDB

This post originally appeared on an external website

by md.athifkhaleel

Automatic Update Client Version 5.4 is compatible with SUS, WindowsUpdate v4, WindowsUpdate v5. This version of AU Client is normally installed in Windows XP SP1, Windows Server 2000 SP# 3 and Windows Server 2003 systems.

Automatic Update Client Version 5.7 was introduced by WUS beta client. This client talks to SUS and the WUS beta.

Automatic Update Client Version 5.8 was introduced by WSUS RC client. This client talks to WSUS RC & SUS.

Hope this gave an idea of Automatic Update Client Versions History.

This post originally appeared on an external website

by md.athifkhaleel

WSUS Requirements
The following lists the software requirements for WSUS servers and client computers.

WSUS Servers
• Windows 2000 Server with Service Pack 3 (SP3) or Windows Server 2003 Standard Edition, Enterprise Edition, Datacenter Edition, or Web Edition.
• Microsoft Internet Information Services (IIS) 5.0.
• Microsoft Internet Explorer 6.0.
• Background Intelligent Transfer Service (BITS)2.0;http://go.microsoft.com/fwlink/?LinkId=46794.
• Microsoft Internet Explorer 6.0 Service Pack 1; http://go.microsoft.com/fwlink/?LinkId=47359.
• Microsoft .NET Framework 1.1 Service Pack 1; http://go.microsoft.com/fwlink/?LinkId=47368.
• Both the system partition and the partition on which you install WSUS must be formatted with the NTFS file system.
• A minimum of 1 GB free space is required for the system partition.
• A minimum of 6 GB free space is required for the volume where WSUS stores content; 30 GB is recommended.
• On Windows 2000, install Microsoft SQL Server 2000 Desktop Engine (MSDE) prior to running WSUS Setup & install a security patch, http://go.microsoft.com/fwlink/?LinkId=47363 to MSDE to protect your WSUS server.

WSUS Clients
• A minimum of Microsoft Windows 2000 Professional with Service Pack 3 (SP3), Microsoft Windows XP Professional, with or without Service Pack 1 or Service Pack 2.

And, get started!

This post originally appeared on an external website

by md.athifkhaleel

Most of the folks want the patches to be installed quickly. This is one of the approach to accomplish Quick AU Client Detection & Installation. It involves both server & client configuration.

Server Configuration:

1. Automatic Detection Frequency: For Quick AU Client detection, you can set the value of “Automatic Detection Frequency” to 1 or 2 hours based on your clients in the network. It actually Specifies the hours that Windows will use to determine how long to wait before checking for available updates. The exact wait time is determined by using the hours specified here minus zero to twenty percent of the hours specified. For example, if this policy is used to specify a 20 hour detection frequency, then all clients to which this policy is applied will check for updates anywhere between 16 and 20 hours.

2. Set the deadline for a known missing update to a date in the past which will force the install as the deadline is already completed & the patch has to install immediately

Client Configuration:

3. Last but not the least, Run this command to force the client detection, "wuauclt /detectnow"

This post originally appeared on an external website

by md.athifkhaleel

Most of the folks want the patches to be installed quickly. This is one of the approach to accomplish Quick AU Client Detection & Installation. It involves both server & client configuration.

Server Configuration:

1. Automatic Detection Frequency: For Quick AU Client detection, you can set the value of “Automatic Detection Frequency” to 1 or 2 hours based on your clients in the network. It actually Specifies the hours that Windows will use to determine how long to wait before checking for available updates. The exact wait time is determined by using the hours specified here minus zero to twenty percent of the hours specified. For example, if this policy is used to specify a 20 hour detection frequency, then all clients to which this policy is applied will check for updates anywhere between 16 and 20 hours.

2. Set the deadline for a known missing update to a date in the past which will force the install as the deadline is already completed & the patch has to install immediately

Client Configuration:

3. Last but not the least, Run this command to force the client detection, "wuauclt /detectnow"

This post originally appeared on an external website

by md.athifkhaleel

In the See Also section on http://Your-SUSServer-IP/SUSAdmin, If you click on Troubleshooting and in the procedure to restart synchronization service, the step 3 says,

"In the results pane, right-click Windows Update Synchronization Service." In fact, there is no service by that name in SUS. In fact, it is "Software Update Services Synchronization Service"

BTW, MBSA 2.0 is finally released and it is compatible with Windows Server Update Services (WSUS)!

Happy Patching!

This post originally appeared on an external website