http://download.microsoft...f/SUS_Deployguide_sp1.doc
Pagina 51
Policy Configuration
Depending on your environment, there are different ways to apply policies to your clients. The preferred method is Group Policy, but policies can also be set using Windows NT 4 System Policy, or by setting registry keys directly.
The behavior of Automatic Updates can be controlled by configuring Group Policy settings in an Active Directory environment. Administrator-defined configuration options driven by Group Policy always take precedence over user-defined options. In addition, Automatic Updates options in Control Panel are disabled on the target computer when administrative policies have been set.
Not:e The refresh interval for Group Policy can be set for a computer to check for updated policies. When policies are updated or refreshed, Automatic Updates immediately processes those changes.
Group Policy settings can be configured centrally using Active Directory or directly on a client computer by using the Local Group Policy Object. To learn more about Group Policy and the Active Directory, refer to the “Group Policy White paper” listed in the “Related Links” section of this white paper.
The following section details how to deploy policy settings to configure the client by using Group Policy.
Using Group policy
In a test or workgroup environment, the easiest way to deploy Group Policy settings is with the Local Group Policy Object. The following steps walk you through how to use the Local Group Policy Object to configure Automatic Updates.
To load policy settings using the Local Group Policy Object
1. You will need the WUAU.adm file that describes the new policy settings for Automatic Updates. WUAU.adm is automatically installed into the %windir%\inf directory when you install Automatic Updates.
2. You can load %windir%\inf\wuau.adm as an administrative template in the Group Policy Object Editor:
3. Click Start, and then click Run.
4. Type GPEDIT.msc to load the Group Policy snap-in.
5. Under Computer Configuration, right-click Administrative Templates.
6. Click Add/Remove Templates, and then click Add.
7. Enter the name of the Automatic Updates ADM file: %windir%\inf\WUAU.adm
8. Click Open, and then click Close to load the wuau.adm file.
Once it is loaded, you will be able to configure policy settings for Automatic Updates. For more information, see the following section, “Configuring Automatic Updates policy settings from the Group Policy Object Editor.”
Note: This ADM file is also available on the server running SUS in the %windir%\inf directory.
To load policy settings using Group Policy in Active Directory
1. You will need the WUAU.adm file that describes the new policy settings for the Automatic Updates client. WUAU.adm is automatically installed into the %windir%\inf folder when you install Automatic Updates.
2. You can load %windir%\inf\wuau.adm as an administrative template in the Group Policy Object Editor.
3. On an Active Directory domain controller, click Start, and then click Run.
4. Type DSA.msc to load the Active Directory Users and Computers snap-in.
5. Right-click the Organizational Unit (OU) or domain where you want to create the policy, and then click Properties.
6. Click the Group Policy tab, and then click New.
7. Type a name for the policy, and then click Edit. This opens the Group Policy Object Editor.
8. Under either Computer Settings or User Settings, right-click Administrative Templates.
9. Click Add/Remove Templates, and then click Add.
10. Enter the name of the Automatic Updates ADM file: %windir%\inf\WUAU.adm
11. Click Open.
Kijk voor meer info over SUS, incl. white papers e.d. op :
http://www.microsoft.com/...ersystem/sus/default.mspx
[
Voor 96% gewijzigd door
Luppie op 24-09-2004 12:51
]
Heb je iets aan mijn antwoord ? Een thumbs-up wordt zeker op prijs gesteld.
/u/35667/SP_Erik.png?f=community)