Professional Documents
Culture Documents
Deployment Guide For Windows Server 2008 R2 With SP1, Windows 7 With SP1
Deployment Guide For Windows Server 2008 R2 With SP1, Windows 7 With SP1
Deployment Guide for Windows Server 2008 R2 with SP1 and Windows 7 with SP1....................2
About this guide........................................................................................................................... 2
Terminology used in this guide................................................................................................. 2
In this guide.............................................................................................................................. 4
Overview of SP1.......................................................................................................................... 4
Before you deploy SP1................................................................................................................ 5
Plan your deployment.................................................................................................................. 5
Important considerations for virtualization................................................................................6
Hyper-V................................................................................................................................ 6
RemoteFX............................................................................................................................. 7
Dynamic Memory.................................................................................................................. 8
Remote administration.......................................................................................................... 8
Hyper-V clustering................................................................................................................ 8
Perform pre-deployment tasks.................................................................................................... 9
Deploy SP1................................................................................................................................ 11
Scenario 1: Installing by using Windows Update.......................................................................12
Scenario 2: Installing the stand-alone package by using the installer executable file................12
Command-line options for stand-alone installation....................................................................13
Large-scale scenarios............................................................................................................... 14
Scenario 3: Creating or updating a custom image.....................................................................14
Scenario 4: Deploying with WSUS............................................................................................15
Scenario 5: Deploying with Windows Deployment Services......................................................16
Scenario 6: Deploying with SMS, System Center Configuration Manager, or System Center
Essentials............................................................................................................................... 17
Uninstalling Windows Server 2008 R2 SP1 or Windows 7 SP1................................................18
Uninstall SP1 from the command line....................................................................................18
Removing backup files........................................................................................................... 19
Troubleshooting......................................................................................................................... 19
Definition
Integrated installation
Offline
Online
Term
Definition
Service pack
Stand-alone package
Update
Upgrade
Term
Definition
In this guide
Overview of SP1
Before you deploy SP1
Plan your deployment
Deploy SP1
Troubleshooting
Overview of SP1
Windows Server 2008 R2 and Windows 7 SP1 is a recommended collection of updates and
improvements to Windows that are combined into a single installable update. Windows Server
2008 R2 SP1 also provides a comprehensive set of innovations for enterprise-class virtualization,
including new virtualization capabilities with Dynamic Memory and Microsoft RemoteFX.
Notable Changes in Service Pack 1 for Windows 7 and Windows Server 2008 R2
(http://go.microsoft.com/fwlink/?LinkId=194726)
Hotfixes and Security Updates included in Windows 7 and Windows 2008 R2 Service Pack 1
(http://go.microsoft.com/fwlink/?LinkId=194725)
Windows 7 and Windows Server 2008 R2 Sp1 Beta Test Focus Guide
(http://go.microsoft.com/fwlink/?LinkId=194727)
Currently, no critical issues that require you to take corrective action either before or immediately
after installation have been reported or discovered in testing. Release Notes documents are
continuously updated, so if any such issues are discovered or reported, they will be available at
the following locations:
Release Notes: Important Issues in this Release of Windows Server 2008 R2 with
Service Pack 1
Release Notes: Important Issues in this Release of Windows 7 with Service Pack 1
For further details on specific features, see the documents linked from the relevant sections later
in this document.
Are you updating existing computers that are running Windows Server 2008 R2 or
Windows 7, performing new installations, or upgrading a previous version of Windows to
Windows Server 2008 R2 or Windows 7?
How should I test and validate the service pack or image installations before deployment?
What network capacity will you need to ensure that the service pack deployment does not
adversely affect the network or cause significant performance issues for other business
applications?
Review available deployment scenarios. For this release, six installation scenarios are
supported:
Scenario 1: Installing by using Windows Update
Scenario 2: Installing the stand-alone package by using the installer executable file
Scenario 3: Creating or updating a custom image
Scenario 4: Deploying with WSUS
Scenario 5: Deploying with Windows Deployment Services
Scenario 6: Deploying with SMS, System Center Configuration Manager, or System Center
Essentials
These deployment methods are discussed in detail in the Deploy SP1section.
5
Note
Check application compatibility. Application Compatibility Toolkit (ACT) 5.6 helps you identify
and manage your overall application portfolio, which reduces the cost and time involved in
resolving issues. For more information, and to download ACT 5.6, see
http://www.microsoft.com/downloads/details.aspx?familyid=24DA89E9-B581-47B0-B45E492DD6DA2971&displaylang=en.
Be aware of virtualization considerations. These considerations apply to you only if you intend
to apply this service pack to a computer running Hyper-V, especially if you use the new
RemoteFX or Dynamic Memory features on any of the virtual machines. Otherwise, you can skip
to the Perform pre-deployment tasks section.
Hyper-V
If you are using Hyper-V on computers on which you want to install this service pack, you should
be aware of the following considerations:
You can import and export virtual machines freely between virtualization servers running
Windows Server 2008 R2 and Windows Server 2008 R2 with SP1 as long as neither
Microsoft RemoteFX nor Dynamic Memory are enabled on the virtual machine.
Saved states and snapshots of virtual machines are compatible between the two
versions as long as Dynamic Memory or RemoteFX has not been enabled.
Virtual machines running Windows as a guest operating system that have R2 integration
services installed will run normally on virtualization servers that are running Windows
Server 2008 R2 with SP1. The Dynamic Memory and RemoteFX features, however, require
the SP1 version of integration services, which includes other updates and enhancements as
well. To get the SP1 version of these services, either install SP1 on the guest operating
system or user Hyper-V Manager (see http://technet.microsoft.com/enus/library/cc732470(WS.10).aspx for details).
Once you have installed this service pack, you will have to uninstall it prior to installing a later
release of this service pack. The settings of any virtual machines will remain intact during the
uninstallation and installation, but virtual machines that have RemoteFX or Dynamic Memory
enabled will not appear in Hyper-V Manager while the service pack is removed. In addition,
any snapshots taken when RemoteFX of Dynamic Memory was enabled will not appear in
Hyper-V Manager. They will reappear and functional normally once the later release of SP1 is
installed.
RemoteFX
For more information about Microsoft RemoteFX, see Whats New in RemoteFX at
http://go.microsoft.com/fwlink/?LinkId=192437.
To use RemoteFX, the virtualization server must be running Windows Server 2008 R2 with SP1,
the virtual machine must be running Windows 7 Enterprise with SP1 or Windows 7 Ultimate with
SP1, and the remote client computer must be running either Windows Server 2008 R2 with SP1
or Windows 7 with SP1.
For detailed information about important CPU and other hardware requirements for RemoteFX,
see Hardware Considerations for RemoteFX at http://go.microsoft.com/fwlink/?LinkId=191918.
Before you start working with RemoteFX, take note of the following considerations:
You should install drivers for the video card on the virtualization server before you enable the
Remote Desktop Services and Hyper-V roles. Otherwise, the RemoteFX 3D Video Adapter
will not be available in Hyper-V Manager.
Disable any graphics processing units that use a Windows XP Display Driver model (XDDM)
driver.
If you manage a KVM switch over IP with an onboard management adapter, install the
RemoteFX Cap driver once you have enabled the RemoteFX role. The RemoteFX Cap driver
supports KVM access over IP prior to the point where the Windows operating system loads
(so that you can access the BIOS). Once the operating system has loaded, you can access
the RemoteFX server using the Remote Desktop Protocol or a non-Microsoft solution for
KVM management over IP. For more information about the RemoteFX Cap driver, see
Deploying Microsoft RemoteFX on a Single Remote Desktop Virtualization Host Server Stepby-Step Guide.
If you do not manage KVM switches over IP with an onboard management adapter, be sure
to disable any such adapters in the BIOS.
Be sure to install this service pack on the Windows 7 guest operating system before you
enable a virtual machine with a 3D adapter. After installing Windows 7, enable Remote
Desktop Services and verify that you can remotely connect to the virtual machine. Then shut
down the virtual machine and add a new video card to the virtual machine by selecting Add
Hardware in the Settings menu of Hyper-V Manager and pointing to 3D Video Card. Boot
the virtual machine and connect to the virtual machine normally. For the full 3D desktop
experience, start Mstsc.exe and confirm that the Experience setting on the Options menu is
set to LAN (10Mbps or higher).
When you are using the virtual 3D video adapter, you will not be able to use the Virtual
Machine Connection. Use Remote Desktop instead. If you need to use Virtual Machine
Connection, you must remove the virtual 3D video card from the virtual machine.
Further guidance on setting up and working with RemoteFX is available in the following
documents:
Deploying Microsoft RemoteFX on a Single Remote Desktop Virtualization Host Server Stepby-Step Guide (http://go.microsoft.com/fwlink/?LinkId=177903)
Dynamic Memory
Dynamic Memory is a new Hyper-V feature available in this service pack. It allows the
virtualization server to pool memory and dynamically add or remove memory based on virtual
machine usage. This allows for higher consolidation ratios of virtual machines on the virtualization
server. To use Dynamic Memory, the virtualization server must be running either Windows
Server 2008 R2 with SP1 or Hyper-V Server 2008 R2 with this version of the service pack
applied.
Virtual machines running a wide variety of operating systems can use Dynamic Memory; for a
complete list, see the Dynamic Memory Evaluation Guide at http://go.microsoft.com/fwlink/?
LinkId=192444. The guide also discusses Dynamic Memory settings and usage in detail.
Remote administration
You can manage virtual machines with the Windows 7 version of the Remote Server
Administration Tools (RSAT), although you cannot configure RemoteFX or Dynamic Memory
settings with this version. The SP1 version of RSAT is not available as this time, so to manage
those settings on a virtualization server running Hyper-V Server 2008 R2 with SP1, use a server
running Windows Server 2008 R2 with SP1.
You can also manage virtualization servers running Windows Server 2008 R2 with SP1 with
System Center Virtual Machine Manager (VMM), but you cannot configure RemoteFX or Dynamic
Memory settings at this time. If you use VMM to move a virtual machine that has Dynamic
Memory enabled, Dynamic Memory will be disabled.
Hyper-V clustering
A Windows Server 2008 R2 Hyper-V Cluster can run as a mixed cluster of nodes running
Windows Server 2008 R2 and Windows Server 2008 R2 with SP1. For information about
installing a service pack in a cluster, see http://support.microsoft.com/kb/174799/en-us. Before
you install the service pack on a cluster, you should be aware of the following considerations:
Do not enable either RemoteFX or Dynamic Memory until the entire cluster is upgraded to
Windows Server 2008 R2 with SP1.
Migration of virtual machines that have Dynamic Memory enabled to a node that does not
have Dynamic Memory support will fail
Migration of virtual machines that have RemoteFX enabled to a node that does not have
RemoteFX enabled will fail.
To live-migrate virtual machines that have RemoteFX enabled, all nodes must be capable of
supporting RemoteFX, all nodes must use identical graphics processing units, and all nodes
8
Notes
must have RemoteFX enabled. For details of the CPU requirements for RemoteFX, see see
Hardware Considerations for RemoteFX at http://go.microsoft.com/fwlink/?LinkId=191918.
requirements
Stand-alone installation
Windows Update
x64-based: 7.4 GB
X64-based: 903 MB
Itanium-based: 3.6 GB
Itanium-based: 511 MB
x64-based: 850 MB
x64-based: 95.7 MB
Itanium-based: not
applicable
Itanium-based: not
applicable
requirements
Stand-alone installation
Windows Update
X86-based: 4.1 GB
X86-based: 537 MB
X64-based: 7.4 GB
X64-based: 903 MB
X86-based: 750 MB
X86-based: 44.3 MB
X64-based: 1050 MB
X64-based: 73.7 MB
For more information about system requirements for Windows 7 independent of this service
pack, see http://technet.microsoft.com/en-us/library/dd349342(WS.10).aspx.
9
2. Read the release notes In general, release notes include vital information about issues you
may encounter, along with steps to avoid or work around them either before or immediately
after installing this service pack.
Currently, no critical issues that require you to take corrective action either before or
immediately after installation have been reported or discovered in testing. Release Notes
documents are continuously updated, so if any such issues are discovered or reported, they
will be available at the following locations:
Release Notes: Important Issues in this Release of Windows Server 2008 R2 with
Service Pack 1
Release Notes: Important Issues in this Release of Windows 7 with Service Pack 1
Alternately:
10
To install
check and
the service
fix any servicing
pack by using
storeWindows
corruptions
Update
2.
3.
Deploy SP1
For this release, six installation scenarios are supported:
Scenario 2: Installing the stand-alone package by using the installer executable file
Scenario 6: Deploying with SMS, System Center Configuration Manager, or System Center
Essentials
Scenarios 1 and 2 are most appropriate for deployment to relatively small numbers of computers.
Scenarios 3 through 6 are best suited to large deployments.
If your computer is set to install updates automatically, when prompted, follow the
instructions to install SP1.
3. Click Start, click Control Panel, double-click Windows Update, and then click Check
for Updates.
4. Select the SP1 update and then click Install.
5. Setup will begin the installation. When prompted, click Restart now. While Setup
completes the installation, you will not be able to log on to the computer.
Caution
Do not restart the computer or turn the power off while installation is in progress.
If you do, the computer may go into an unbootable state.
6. When the Windows logon prompt appears, this indicates that Setup is completed. At this
time, you can log on to the computer. A dialog box will display the status of the
installation.
12
For example, to run the installation file in quiet mode without restarting the computer, type:
Windows6.1-kb976932-nnn.exe /quiet /norestart
Options
Description
/forcerestart
/nodialog
/norestart
/promptrestart
/quiet
/unattend
Options
Description
restarted.
/warnrestart[:<seconds>]
/?
or /help
Large-scale scenarios
These scenarios are applicable to businesses that want to deploy SP1 to multiple computers or
deploy custom images, or both. We recommend that you use the SP1 integrated DVD to install
SP1. Although it is not recommended, if you have custom Windows Server 2008 R2 or
Windows 7 images that you want to update, you can boot the Windows image, apply the service
pack, and then recapture the image. This online method is the only way to update images with
SP1; SP1 cannot be installed to or uninstalled from an offline image of Windows Server 2008 R2
or Windows 7.
The Microsoft Deployment Toolkit (http://go.microsoft.com/fwlink/?LinkId=108442) is the
recommended methodology and solution to help you deploy Windows Server 2008 R2. This
toolkit can assist you in building and deploying custom images, including zero-touch deployments
using Systems Management Server 2003 and System Center Configuration Manager 2007.
If your WSUS server is running Windows Server 2003, you will need to install an update to
ensure that SP1 is downloaded successfully. For more information, see Knowledge Base
article 938759 (http://go.microsoft.com/fwlink/?LinkId=108519).
If your organization is using the Service Pack Blocker Tool to block individual users from
installing SP1, publishing the service pack to WSUS will automatically override the block, and
SP1 will be installed.
Eventually, SP1 will sync automatically to your WSUS server as long as the server is configured
to synchronize Windows Server 2008 R2 or Windows 7 service packs. Until then, use the
following steps to manually import the service pack from the Microsoft Update Catalog site. The
package that is installed contains both the prerequisite packages and SP1. This entire package
will be downloaded to each destination computer, unlike with Windows Update, where only the
components that are needed for a specific computer are downloaded.
1. Open the WSUS Administrator console, expand the Update Services node, and then
expand the node for the WSUS server.
2. Right-click the Updates node and click Import Updates.
3. At the Microsoft Updates Catalog website, search for Windows 7 with SP1.
4. In the results, click Add to add one or more of the following updates to your basket:
Windows Server 2008 R2 Service Pack 1 Standalone (x86); Windows Server 2008 R2
Service Pack 1 Standalone (x64); Windows Server 2008 R2 Service Pack 1
Standalone (ia64).
5. Click View basket.
6. Confirm your selections and click Import to import these packages.
Add the Install.wim image from the DVD that contains the integrated version of Windows
Server 2008 R2 SP1 to your Windows Deployment Services server.
Create a customized installation image from a reference computer, and then add it to your
Windows Deployment Services server to create a capture image and reference computer and
then to create an installation image that contains the new image.
15
To create an
a capture
installation
image
image
and athat
reference
contains
computer
the new image
6.
7.
1. Add the Boot.wim file located in the \Sources folder on the Windows Server 2008 R2 with
SP1 DVD to your Windows Deployment Services server.
2. Create a capture image from the Boot.wim file, and then add it to the Windows
Deployment Services server.
3. Create a reference computer that contains Windows Server 2008 R2, SP1, and any
programs and settings that you want to include in the image.
4. At the command prompt, change directories to \Windows\System32\Sysprep.Run the
following command: sysprep /oobe /generalize /reboot.
1. Restart the computer, and then press F12.
2. Select the capture image that you created in Step 2 of the preceding procedure.
3. In the Image Capture Wizard, select the appropriate drive, and then provide a name and
description for the image.
4. Click Next. You will only see drives that contain operating systems that have been
prepared with Sysprep.
5. Click Browse and then browse to a local location where you want to store the captured
installation image. You must enter a local location to save the new image; otherwise, you
will not be able to capture the image. This will prevent the image from being corrupted in
the event of a network malfunction.
6. Type a name for the image by using the .wim file name extension, and then click Save.
You must use the .wim filename extension, otherwise the capture will fail.
7. Complete the Image Capture wizard.
With this custom installation image, you can boot a client computer into the Pre-Boot Execution
Environment (PXE) and install the image. For more information, see the Windows Deployment
Services Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkId=84628).
Be aware that System Center Configuration Manager and Systems Management Server will
not provide any warnings or errors that will prevent you from installing the service pack.
Prepare your support staff with information about how to recognize and correct driver issues.
16
Test SP1 installations before deployment. If needed, install updated drivers from Windows
Update or vendors as they become available.
For computers that have drivers for which updates are not yet available, correct the driver
issues after you have installed SP1. For more information, see
http://go.microsoft.com/fwlink/?LinkId=113723.
If you are using any of these deployment tools on a computer running Windows Server 2003,
install the KB938759 update http://go.microsoft.com/fwlink/?LinkId=108519) to ensure that
SP1 downloads successfully. For Systems Management Server and System Center
Configuration Manager, apply the update to each site server, software update point, and
administrative console. This update is included in Windows Server 2008 R2 and Windows
Server 2008 R2, but is not available for Windows XP. Start the Distribute Software Update
wizard from a computer running Windows Vista, Windows Server 2008 R2, or Windows
Server 2003 (with the KB938759 update installed).
See the following for additional information about each deployment method:
System Center Configuration Manager 2007: You can either distribute the software by
creating a software distribution package and advertisement or by using Software Updates
Management. For more information about using software distribution packages, see
"Software Distribution in Configuration Manager (http://go.microsoft.com/fwlink/?
LinkId=109191). For more information about using software updates management, see
Software Updates in Configuration Manager (http://go.microsoft.com/fwlink/?
LinkId=109202). An advantage of using Software Updates Management is that no commandline settings or detection logic are required. In Configuration Manager, SP1 will be listed as an
available update after a successful sync from the software update point.
System Center Essentials: For more information about System Center Essentials, see
Overview: System Center Essentials 2007 (http://go.microsoft.com/fwlink/?LinkID=89185).
Systems Management Server: You can either distribute the software by creating a software
distribution package and advertisement or by using the Inventory Tool for Microsoft Updates
(ITMU). For more information about using software distribution packages, see Distribute
Software (http://go.microsoft.com/fwlink/?LinkId=109218). For about using SMS and ITMU,
see SMS 2003 Inventory Tool for Microsoft Updates (http://go.microsoft.com/fwlink/?
LinkId=108463).
17
1. Open Control Panel, click Programs, and then click View Installed Updates.
2. In the Microsoft Windows list, right-click Service Pack for Microsoft Windows
(KB976932), and then click Uninstall.
3. When prompted, restart the computer.
Description
/norestart
/promptrestart
/quiet
/warnrestart[:<seconds>]
18
Important
Troubleshooting
To confirm that SP1 is installed, right-click Computer and then click Properties. You will find a
reference to the service pack in the Windows Edition section.
When installing SP1, some computers may run into issues that block the installation or otherwise
cause it to fail. These issues may include the following:
Memory failures
Software and file system synchronization issues. For performance reasons, the file system
keeps a copy of the contents of some files in the memory, and it can take a while for these
contents to be written back to the hard disk. Therefore, sometimes the contents of the files on
the hard disk may be slightly out of synchronization with the memory.
To work around installation problems, perform the following steps in the specified order:
1. Ensure that you have enough disk space, as specified in the "Check disk space
requirements" table under Perform predeployment tasks earlier in this guide. Then restart the
computer and try again to install SP1. This will ensure that all files are synchronized properly.
2. If the installation still fails, download and extract the KB976932 update from the Microsoft
Download Center. The Windows6.0-KB976932-NNN.msu file will ensure that the computer is
ready to be updated. Then try again to install SP1. For information about this update,
including information about how to obtain it, see http://go.microsoft.com/fwlink/?
LinkId=109180.
3. If the installation still fails, open an elevated Command Prompt window, and then run the
chkdsk /f command. The Chkdsk tool checks the file system and metadata for errors, and
then it fixes the errors, if possible. Then try again to install SP1.
19
4. If the installation still fails, open an elevated Command Prompt window, and then run the
MdSched.exe command. The Windows Memory Diagnostic tool tests the random access
memory (RAM) on your computer for errors. Then try again to install SP1.
20