This is the time to wait before the AU client will re-prompt to restart after a scheduled restart has been issued. Table 7.5 continued AU Configuration Registry KeysĠ = Treat minor updates like other updates and use scheduled times.ġ = Silently install minor, non-intrusive updates.ġ = Enable detection Reg_DWORD frequency.Ġ = Disable custom Detection Frequency, which means use the default. ScheduledInstallDay and ScheduledInstal Time values).ĥ = AU is required, but local administrators can configure its settings. Matching Group Key Name Values Data Type PolicyĪUOptions Range = 2 | 3 | 4 |5 Reg_DWORD Configure AU.ģ = Automatically download and notify for installation.Ĥ = Automatically download and schedule installation (valid only when used with This policy is paired with WUServer īoth must be set to the same value in order for them to be valid. HTTP/HTTPS URL of Reg_String the server to which reporting information will be sent byĪU's client. WUStatusServer Reg_String both must be set to the same value in order for them to be valid. Table 7.4 continued Windows Update Agent Environment Registry Keys This policy is paired withĪllow non-administrators to receive update notifications. Hypertext Transfer Protocol (HTTP)/ Hypertext Transfer Protocol Secure Sockets (HTTPS)URL of your WSUS server used by your AU client. This is the name of Reg_String the computer group to which you want your computer to belong (e.g., Exchange Servers.) This policy is paired with TargetGroupEnabled.Ġ= Do not use client-side targeting. TargetGroupEnabled approve or disapprove updates.Ġ = Only users in the Administrators user group can approve or disapprove updates. Table 7.4 Windows Update Agent Environment Registry Keys The tables are divided to show you each key separately, the first showing the WSUS client environment variables and the latter showing the AU client's own configuration options.
Table 7.4 and Table 7.5 outline each of the possible registry key combinations, their possible key partners (if necessary), the registry key data type, and the corresponding Group Policy and Local Policy. ■ HKEY_LOCAL_MACHINESOFTWAREPolkiesXMkmsoft\ windows\WindowsUpdate\AU ■ HKEY_LOCAL_MACHINESOFTWAREPolkies\ Microsoji\wmdows\WmdowsUpdate In situations where Group Policy is not available due to the lack of an active Directory domain and where configuring local policy becomes too tedious because of each "logical" machine visit, a few scripting techniques might help you roll out the needed registry keys.Īs mentioned, both Group Policy and Local Policy place their settings in the registry hive and keys shown here: That being said, you can edit the registry directly to configure your WSUS-specific client configuration needs. Regardless of the front end, almost all software configurations ultimately end up manipulating the Windows registry for final client configuration commitments.
0 kommentar(er)
