BRONZE PARTNER:
BRONZE PARTNER:
Industry News:
| |
| |
|
|
|
|
|
| SUS Registry Settings for Non-AD Environments |
|
|
|
By: Rod Trent
Posted On: 11/26/2002
If you've installed Software Update Services in a non-Active Directory domain, you'll need to modify the computers' registries to point to your internal Windows Update server.
If you have an AD environment, Microsoft includes a policy template file, Wuau.adm. This policy template contains the Group Policy settings that can be loaded into Group Policy Editor for deployment.
These same policies are also included in the System.adm file in Windows 2000 Service Pack 3 and Windows XP Service Pack 1.
But for those not yet migrated to Active Directory, the following registry modifications can allow your clients to still utilize SUS.
HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU
• NoAutoUpdate
Range = 0|1.
0 = Automatic Updates is enabled (default)
1 = Automatic Updates is disabled.
• AUOptions
Range = 2|3|4.
2 = notify of download and installation
3 = auto download and notify of installation
4 = auto download and scheduled installation. All options notify the local administrator.
• ScheduledInstallDay
Range = 0|1|2|3|4|5|6|7.
0 = Every day
1 through 7 = the days of the week from Sunday (1) to Saturday (7).
• ScheduledInstallTime
Range = n
where n = the time of day in 24-hour format (0-23).
• UseWUServer
Set this to 1 to enable Automatic Updates to use the Software Update Services server as specified in the WUServer value.
To force the clients to pull from a specific SUS server place the following two settings in the registry at this location:
HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate
• WUServer
Sets the Windows Update intranet server by HTTP name (for example, http://intranetSUSServer).
• WUStatusServer
Sets the Windows Update intranet statistics server by HTTP name (for example, http://intranetSUSServer).
|
|
|
|
|
|
