Can i install wsus on windows xp

The first setting, Configure Automatic Updates, is used to enable or disable automatic updates. If it is enabled you can select one of the following settings as to how updates are downloaded and if the administrator is notified:. You also need to point the client computers to the WSUS server on the network. Double click the Specify intranet Microsoft update service location option and click Enabled.

Type in the same URL in the Set the intranet statistics server field. Group policy settings are automatically refreshed at a certain interval so the changes may not take effect immediately. The remaining settings that can be configured through a GPO are:. As already mentioned Automatic Updates can also be configured locally if your network does not use Active Directory. This can be done by editing the Local Group Policy object with the Group Policy editor or by creating and editing various registry entries.

Type in gpedit. The Group Policy editor will appear. The details pane will display the same settings that were outlined in the previous section. Finally, you can also configure the WSUS client settings through the local registry. This requires you to create several registry keys, some of which are outlined in the table below.

This option is used to specify whether a WSUS server is used. Setting the value to 1 indicates the client will download updates from a WSUS server. This option is used to configure how updates are downloaded and whether administrators are notified. The possible values are 2 notify of download and installation , 3 automatically download and notify of installation , 4 automatic download and scheduled installation , or 5 Automatic Updates is required, but end users can configure it.

This option specifies the day of the week that updates will be installed. This option specifies the time of day that installs will take place. The value is specified in 24 hour format. This defines how long to wait after restarting to computer for a missed scheduled install to take place. The value is specified in minutes Computer groups permit you to test and target updates to specific computers.

There are two default computer groups: All Computers and Unassigned Computers. By default, when each client computer first contacts the WSUS server, the server adds that client computer to both of these groups. You can create as many custom computer groups as you need to manage updates in your organization.

As a best practice, create at least one computer group to test updates before you deploy them to other computers in your organization. There are two approaches to assigning client computers to computer groups.

The right approach for your organization will depend on how you typically manage your client computers. Server-side targeting : This is the default approach. This approach gives you the flexibility to quickly move client computers from one group to another as circumstances change.

But it means that new client computers must manually be moved from the Unassigned Computers group to the appropriate computer group.

Client-side targeting : In this approach, you assign each client computer to computer groups by using policy settings set on the client computer itself. This approach makes it easier to assign new client computers to the appropriate groups. You do so as part of configuring the client computer to receive updates from the WSUS server. But it means that client computers can't be assigned to computer groups, or moved from one computer group to another, through the WSUS Administration Console.

Instead, the client computers' policies must be modified. You must create computer groups by using the WSUS Administration Console, whether you use server-side targeting or client-side targeting to add client computers to the computer groups.

In the Add Computer Group dialog, for Name , specify the name of the new group. Then select Add. 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. Log on to the server on which you plan to install the WSUS server role by using an account that is a member of the Local Administrators group. In the select installation type page, confirm that Role-based or feature-based installation option is selected and click Next. On the select destination server page, choose where the server is located from a server pool or from a virtual hard disk.

After you select the location, choose the server on which you want to install the WSUS server role, and then click Next. On the select server roles page, select Windows Server Update Services. Add features that are required for Windows Server Update Services opens. Click Add Features , and then click Next. On the select features page, retain the default selections, and then click Next.

On the Select Role Services page, leave the default selections, and then click Next. You must select one Database type. If the database options are all cleared not selected , post installation tasks will fail. On the Content location selection page, type a valid location to store the updates.