Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. The latest version of the Windows Update Agent for Windows 8.
The latest version of the Windows Update Agent for Windows 8 is 7. A hardened infrastructure so that the Windows Update client will trust only those files that are signed by a new certificate. The certificate is used solely to protect updates to the Windows Update client. Version 7. This issue was not previously documented in a Microsoft Knowledge Base article:.
These issues were not previously documented in a Microsoft Knowledge Base article:. Windows Update helps keep your computer up-to-date and secure by downloading and installing the latest security and other updates from Microsoft. Windows Update determines which updates apply to your computer. Microsoft periodically makes software updates available to users of Windows and other Microsoft software.
These include updates that improve reliability and performance, updates that provide new protections against malware and other potentially unwanted software, and upgrades to Windows features. Thanks for the help. Thai Pepper. This topic has been locked by an administrator and is no longer open for commenting. The client computers must trust the certificate that you bind to the WSUS server.
Depending on the type of certificate that's used, you might have to set up a service to enable the client computers to trust the certificate that's bound to the WSUS server. If you're using local publishing, you should also configure the client computers to trust the WSUS server's code-signing certificate.
For instructions, see Local publishing. By default, your client computers receive updates from Windows Update. They must be configured to receive updates from the WSUS server instead. This article presents one set of steps for configuring client computers by using Group Policy.
These steps are appropriate in many situations. But many other options are available for configuring update behavior on client computers, including using mobile device management.
These options are documented in Manage additional Windows Update settings. If you don't use Active Directory in your network, you'll configure each computer by using the Local Group Policy Editor. These instructions assume that you're using the most recent versions of the policy editing tools. On older versions of the tools, the policies might be arranged differently. In the object that you expanded in the previous step, expand Administrative Templates , expand Windows components , expand Windows Update , and select Manage end user experience.
On the details pane, double-click Configure Automatic Updates. The Configure Automatic Updates policy opens. Select Enabled , and then select the desired option under the Configure automatic updating setting to manage how Automatic Updates will download and install approved updates. We recommend using the Auto download and schedule the install setting. It ensures that the updates you approve in WSUS will be downloaded and installed in a timely fashion, without the need for user intervention.
If desired, edit other parts of the policy, as documented in Manage additional Windows Update settings. The Install updates from other Microsoft products checkbox has no effect on client computers receiving updates from WSUS. The client computers will receive all updates approved for them on the WSUS server.
On the Manage updates offered from Windows Server Update Service details pane, double-click Specify intranet Microsoft update service location. The Specify intranet Microsoft update service location policy opens. Make sure to include the correct port in the URL. Select OK to close the Specify intranet Microsoft update service location policy.
If you've chosen to use client-side targeting, you should now specify the appropriate computer group for the client computers you're configuring. These steps assume that you've just completed the steps for editing policies to configure the client computers. On the Manage updates offered from Windows Server Update Service details pane, double-click Enable client-side targeting.
The Enable client-side targeting policy opens. Select Enabled , and then enter the name of the WSUS computer group to which you want to add the client computers in the Target group name for this computer box. If you're running a current version of WSUS, you can add the client computers to multiple computer groups by entering the group names, separated by semicolons.
For example, you can enter Accounting;Executive to add the client computers to both the Accounting and Executive computer groups. If you used an Active Directory-based GPO to configure the client computers, it will take some time for the Group Policy Update mechanism to deliver the changes to a client computer.
If you used the Local Group Policy Editor to configure an individual client computer, the changes take effect immediately. Restart the client computer. This step makes sure that the Windows Update software on the computer detects the policy changes. The client computer successfully scans for updates. It might or might not find any applicable updates to download and install. Within about 20 minutes, the client computer appears in the list of computers displayed in the WSUS Administration Console, based on the type of targeting:.
If you're using server-side targeting, the client computer appears in the All Computers and Unassigned Computers computer groups. If you're using client-side targeting, the client computer appears in the All Computers computer group and in the computer group that you selected while configuring the client computer.
If you're using server-side targeting, you should now add the new client computer to the appropriate computer groups. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.
0コメント