Service Packs

A service pack is a cumulative set of all of the updates that have been created for a Microsoft product. A service pack also includes fixes for other problems that have been found by Microsoft since the release of the product. In addition, a service pack can contain customerrequested design changes or features. Like security updates, service packs are available for download and are accompanied by Knowledge Base articles.

The chief difference between service packs and other types of updates is that service packs are strategic deliveries, whereas updates are tactical. That is, service packs are carefully planned and managed-the goal is to deliver a well-tested, comprehensive set of fixes that is suitable for use on any computer. In contrast, security updates are developed on an as-needed basis to combat specific problems that require an immediate response.

Note Service packs undergo extensive regression testing that Microsoft does not perform for other types of updates. However, because they can make significant changes to the operating system and add new features, they still require extensive testing within your environment.

Microsoft does not release a service pack until it meets the same quality standards as the product itself. Service packs are constantly tested as they are built, undergoing weeks or months of rigorous final testing that includes testing in conjunction with hundreds or thousands of non- Microsoft products. Service packs also undergo a beta phase, during which customers participate in the testing. If the testing reveals bugs, Microsoft will delay the release of the service pack.

Even though Microsoft tests service packs extensively, they frequently have known application incompatibilities. However, they are less likely to have unknown application incompatibilities. It is critical that you review the service pack release notes to determine how the service pack might affect your applications.

Because service packs can make substantial changes to Windows 7, thorough testing and a staged deployment are essential. After Microsoft releases a service pack for beta, begin testing it in your environment. Specifically, test all applications, desktop configurations, and network connectivity scenarios. If you discover problems, work with Microsoft to identify the problem further so that Microsoft can resolve the issues before the service pack is released. After the service pack is released, you need to test the production service pack carefully before deploying it.

While testing a newly released service pack, stay in touch with the IT community to understand the experiences of organizations that deploy the service pack before you. Their experiences can be valuable for identifying potential problems and refining your deployment process to avoid delays and incompatibilities. Microsoft security updates can be applied to systems with the current or previous service pack so you can continue with your usual Microsoft update process until after you have deployed the new service pack.

More Info For more information about the Microsoft TechNet IT Professional Community, visit http://www.microsoft.com/technet/community/.

After testing, you should use staged deployments with service packs, just as you would for any major change. With a staged deployment, you install the service pack on a limited number of computers first. Then, you wait days or weeks for users to discover problems with the service pack. If a problem is discovered, you should be prepared to roll back the service pack by uninstalling it. Work to resolve all problems before distributing the service pack to a wider audience.