Test Updates

  • Article

Applies To: Windows Server 2003 with SP2, Windows Server 2008 R2, Windows Server 2008 R2 with SP1, Windows Server Update Services, Windows Small Business Server 2011 Standard

Until you install an update, you cannot be certain about the impact it will have on other programs running on your systems. By installing an update in a test environment, you can assess its impact before you decide whether to deploy it to your production systems. This approach can prevent unplanned downtime and lost productivity.

WSUS enables you to create custom computer groups that you can use to test updates. For example, the following image depicts three computer groups: two custom groups that are created by the administrator (Test and Accounting), and the built-in All Computers group.

In this example, the Test group contains a small number of computers that are representative of the computers in the Accounting group. The administrator can first approve updates for the Test group. If the testing goes well, the administrator can roll out the updates to the Accounting group.

You can create multiple test computer groups with configurations that resemble the computers in departments in your organization.

Test service packs carefully

You should thoroughly test large bundles of updates such as service packs to ensure that they do not break line-of-business applications.

Important

Most notably:

  • Windows® 7 with Service Pack 1 (SP1)

  • Windows Server® 2008 R2 with Service Pack 1 (SP1)

Following is a typical test strategy:

  1. Set up test computer groups in which the test computers are configured with the same applications as the production groups.

  2. Approve installation only to these groups.

  3. Verify that the applications continue to function correctly.