I am sure many of you deployment guys out there have waited for the Windows 7 and Server 2008 R2 service pack. It is finally here. This raises two good questions.
- Should we deploy it to our workstations and servers?
- How should we deploy it?
When it comes to “should we install sp1” question, it leave it up to you guys to test and evaluate. But on the client side, the biggest reasons to install are:
- Additional support for communication with third-party federation services
- Improved HDMI audio device performance
- Corrected behavior when printing mixed-orientation XPS documents
On the server side, some of the improvements include:
- Dynamic Memory
- Microsoft RemoteFX
- Enhancements to scalability and high availability when using DirectAccess
- Support for Managed Service Accounts (MSAs) in secure branch office scenarios
- Support for increased volume of authentication traffic on domain controllers connected to high-latency networks
- Enhancements to Failover Clustering with Storage
How to deploy?
First off all, personal computers should get their SP1 from Windows Update. That is an easy and safe solution.
For those of you that work with enterprise solution, we have several options.
If you have Configuration Manager 2007, you can either deploy the service pack as an application, or use the WSUS integration to deploy it as an update.
I still recommend capturing a new reference image, using Windows 7 with integrated SP1. Remember that a service pack is a cumulative update of most of the hotfixes and updates that have been released to Windows 7 and Server 2008 R2 thus far (ca. 800 in total!!). A new image with SP1 integrated will speed up deployment, because fewer updates have to be downloaded from Microsoft Update/WSUS. The Windows 7 image with SP1 integrated is available from the Microsoft Volume License Service Senter, or from Technet subscriptions, if you have the appropriate license agreements/subscription.