Deploying updates on clients in WSUS environment
Query:
I am little bit confused regarding deploying updates on clients using WSUS server, i have configured some four clients using group policy to point to WSUS server, that clients are shown in WSUS administrationtconsole but how to deploy updtes from server to client i want the procedure , also i want to schedule the client for getting updtes informtion from server. so plz help me out for this problem asap.
Solution:
Check this
Server Side after SUS Installation
Synchronizing SUS
- If you are not already viewing the SUS administration page, open Internet Explorer and navigate to http://yoursusSERVER01/SUSAdmin.
- To view the SUS administration site, you might need to add Server01 to the Local Intranet trusted site list to access the site. Open Internet Explorer, and choose Internet Options from the Tools menu. Click the Security Tab. Select Trusted Sites, and click Sites. Add yoursusServer01 and yoursusServer01.contoso.com to the trusted site list.
- Click Synchronize Server on the left navigation bar.
- Click Synchronization Schedule.
You will manually synchronize for this. However, you can examine synchronization options by clicking Synchronize Using This Schedule. When you are finished exploring settings, click Cancel. - On the Synchronize Server page, click Synchronize Now. If you have elected to download updates to the server, synchronization might take some time.
- After synchronization has occurred, you will be redirected automatically to the Approve Updates page. You can also click Approve Updates on the left navigation bar.
- Approve a small number of updates so that you can return later to experiment further with approval and automatic updates.
- Examine other pages of the SUS administration site. After you have familiarized yourself with the site, close Internet Explorer.
Configuring Automatic Updates Through Group Policy
The Automatic Updates client will, by default, connect to the Microsoft Windows Update server. Once you have installed SUS in your organization, you can direct Automatic Updates to connect to specific intranet servers by configuring the registry of clients manually or by using Windows Update group policies.
To configure Automatic Updates using GPOs, open a GPO and navigate to the Computer Configuration\Administrative Templates\Windows Components\Windows Update node.
Configuring Automatic Updates
- · Open Active Directory Sites And Services.NoteMost enterprises have found little reason to link GPOs to sites, rather than to OUs or the domain. However, SUS-related policies lend themselves well to site application because you are directing clients to the most site-appropriate SUS server.
- · Right-click the Default-First-Site-Name site, and choose Properties.
- · Click the Group Policy tab.
- · Click New, and name the new GPO SUS-Site1.
- · Click Edit. The Group Policy Object Editor opens.
- · Navigate to Computer Configuration\Administrative Templates\Windows Components\Windows Update.
- · Double-click the policy Specify Intranet Microsoft Update Service Location.
- · Click Enabled.
- · In both text boxes, type http://yourSUSserver01.contoso.com.
- · Click OK.
- · Double-click the policy Configure Automatic Updates.
- · Click Enabled.
- · In the Configure Automatic Updating drop-down list, choose 4-Auto Download And Schedule The Install.
- · Confirm the installation schedule as daily at 3:00 A.M.
- · Click OK.
- · Double-click the policy Reschedule Automatic Updates Scheduled Installations.
- · Click Enabled.
- · In the Wait After System Startup (Minutes) box, type 1.The Wait After System Startup policy is used to reschedule a scheduled installation that was missed, typically when a machine was turned off at the scheduled date and time. !
- · Click OK.
- · Close the Group Policy Object Editor and the Properties dialog box for Default-First-Site-Name.
- · To confirm the configuration, you can restart Server02, which is also within the scope of the new policy. Open System from Control Panel, and click the Automatic Updates tab. You will see that configuration options are disabled, as they are now being determined by policy.
Comments