Deployment Considerations for Windows To Go
Published: August 15, 2012
Updated: August 15, 2012
Applies To: Windows 8
From the start, Windows To Go was designed to minimize differences between the user experience of working on Windows 8 from a laptop and Windows To Go booted from a USB drive. Given that Windows To Go was designed as an enterprise solution, extra consideration was given to the deployment workflows that enterprises already have in place. Additionally, there has been a focus on minimizing the number of differences in deployment between Windows To Go workspaces and laptop PCs. The following sections discuss the boot experience, deployment methods, and tools that you can use with Windows To Go.
Initial Boot Experiences
Image deployment and drive provisioning considerations
Application installation and domain join
Management of Windows To Go using Group Policy
Supporting booting from USB
Roaming between different firmware types
Configuring Windows To Go Startup Options
Changing firmware settings
The following diagrams illustrate the two different methods you could use to provide Windows To Go drives to your users. The experiences differ depending on whether the user will be booting the device initially on-premises or off-premises:
When a Windows To Go workspace is first used at the workplace, the Windows To Go workspace can be joined to the domain through the normal procedures that occur when a new computer is introduced. It obtains a lease, applicable policies are applied and set, and user account tokens are placed appropriately. BitLocker protection can be applied and the BitLocker recovery key automatically stored in Active Directory Domain Services. The user can access network resources to install software and get access to data sources. When the workspace is subsequently booted at a different location either on or off premises, the configuration required for it to connect back to the work network using either Direct Access or a virtual private network connection can be configured. It is not necessary to configure the workspace for offline domain join. Direct Access can make connecting to organizational resources easier, but is not required.
When the Windows To Go workspace is going to be used first on an off-premises computer, such as one at the employee’s home, then the IT professional preparing the Windows To Go drives should configure the drive to be able to connect to organizational resources and to maintain the security of the workspace. In this situation, the Windows To Go workspace needs to be configured for offline domain join and BitLocker needs to be enabled before the workspace has been initialized.
|Applying BitLocker Drive Encryption to the drives before provisioning is a much faster process than encrypting the drives after data has already been stored on them due to a new feature called used-disk space only encryption. For more information, see What's New in BitLocker.|
DirectAccess can be used to ensure that the user can login with their domain credentials without needing a local account. For instructions on setting up a Direct Access solution, for a small pilot deployment see Deploy a Single Remote Access Server using the Getting Started Wizard for a larger scale deployment, see Deploy Remote Access in an Enterprise. If you do not want to use Direct Access as an alternative users could log on using a local user account on the Windows To Go workspace and then use a virtual private network for remote access to your organizational network.
The Image Deployment process can be accomplished either by a centralized IT process for your organization or by individual users creating their own Windows To Go workspaces. A user must have local administrator access and access to a Windows 8 Enterprise image to create a Windows To Go workspace or you must be using System Center Configuration Manager 2012 Service Pack 1 to distribute Windows To Go workspaces to users. The image deployment process takes a blank USB drive and a Windows 8 Enterprise image (WIM) and turns it into a Windows To Go drive.
The simplest way to provision a Windows To Go drive is to use the Windows To Go Creator. After a single Windows To Go workspace has been created, it can be duplicated as many times as necessary using widely available USB duplicator products as long as the device has not been booted. Once the Windows To Go drive is initialized, it should not be duplicated. Alternatively, Windows To Go Workspace Creator can be run multiple times to create multiple Windows To Go drives.
|When you create your Windows To Go image use sysprep /generalize, just as you do when deploying Windows 8 to a standard PC. In fact, if appropriate, use the same image for both deployments. Windows 8 includes most of the drivers that you will need to support a wide variety of host computers. However, you will occasionally need to download drivers from Windows Update to take advantage of the full functionality of a device. If you are using Windows To Go on a set of known host computers, you can add any additional drivers to the image used on Windows To Go to make Windows To Go drives more quickly usable by your employees. Especially ensure that network drivers are available so that the user can connect to Windows Update to get additional drivers if necessary.|
Unless you are using a customized Windows 8 image that includes unattended installation settings, the initial Windows To Go workspace will not be domain joined and will not contain applications. This is exactly like a new installation of Windows 8 on a desktop or laptop computer. When planning your deployment, you should develop methods to join Windows to Go drives to the domain and install the standard applications that users in your organization require. These methods probably will be similar to the ones used for setting up desktop and laptop computers with domain privileges and applications
In general, management of Windows To Go workspaces is same as that for desktop and laptop computers. There are Windows To Go specific Group Policy settings that should be considered as part of Windows To Go deployment. Windows To Go Group Policy settings are located at
\\Computer Configuration\Administrative Templates\Windows Components\Portable Operating System\ in the Local Group Policy Editor. The use of the Store on Windows To Go workspaces is also controlled by Group Policy. This policy setting is located at
\\Computer Configuration\Administrative Templates\Windows Components\Store\ in the Local Group Policy Editor. The policy settings have specific implications for Windows To Go that you should be aware of when planning your deployment:
Settings for workspaces
Allow hibernate (S4) when started from a Windows To Go workspace
This policy setting specifies whether the PC can use the hibernation sleep state (S4) when started from a Windows To Go workspace. By default, hibernation is disabled when using Windows To Go workspace, so enabling this setting explicitly turns this ability back on. When a computer enters hibernation, the contents of memory are written to disk. When the disk is resumed, it is important that the hardware attached to the system, as well as the disk itself, are unchanged. This is inherently incompatible with roaming between PC hosts. Hibernation should only be used when the Windows To Go workspace is not being used to roam between host PCs.
Important For the host-PC to resume correctly when hibernation is enabled the Windows To Go workspace must continue to use the same USB port.
Disallow standby sleep states (S1-S3) when starting from a Windows To Go workspace
This policy setting specifies whether the PC can use standby sleep states (S1–S3) when started from a Windows To Go workspace. The Sleep state also presents a unique challenge to Windows To Go users. When a computer goes to sleep, it appears as if it is shut down. It could be very easy for a user to think that a Windows To Go workspace in sleep mode was actually shut down and they could remove the Windows To Go drive and take it home. Removing the Windows To Go drive in this scenario is equivalent to an unclean shutdown which may result in the loss of unsaved user data or the corruption on the drive. Moreover, if the user now boots the drive on another PC and brings it back to the first PC which still happens to be in the sleep state, it will lead to an arbitrary crash and eventually corruption of the drive and result in the workspace becoming unusable. If you enable this policy setting, the Windows To Go workspace cannot use the standby states to cause the PC to enter sleep mode. If you disable or do not configure this policy setting, the Windows To Go workspace can place the PC in sleep mode.
Allow Store to install apps on Windows To Go workspaces
This policy setting allows or denies access to the Store application from the Windows To Go workspace. If you enable this setting, access to the Store application is allowed on the Windows To Go workspace. You should only enable this policy setting when the Windows To Go workspace will only be used with a single PC. When roaming Windows To Go devices to multiple PCs, installing applications from the Store is not a supported scenario. However, IT Pro side-loaded Windows Runtime-based line of business (LOB) apps can run in Windows To Go workspaces even when roamed between multiple PCs. If you disable or do not configure this policy setting, access to the Store application is denied on the Windows To Go workspace.
Settings for host PCs
Windows To Go Default Startup Options
This policy setting controls whether the host computer will boot to Windows To Go if a USB device containing a Windows To Go workspace is connected, and controls whether users can make changes using the Windows To Go Startup Options settings dialog. If you enable this policy setting, booting to Windows To Go when a USB device is connected will be enabled and users will not be able to make changes using the Windows To Go Startup Options settings dialog. If you disable this policy setting, booting to Windows To Go when a USB device is connected will not be enabled unless a user configures the option manually in the firmware. If you do not configure this policy setting, users who are members of the local Administrators group can enable or disable booting from USB using the Windows To Go Startup Options settings dialog.
Important Enabling this policy setting will cause PCs running Windows 8 to attempt to boot from any USB device that is inserted into the PC before it is started.
The biggest hurdle for a user wanting to use Windows To Go is configuring their computer to boot from USB. This is traditionally done by entering the firmware and configuring the appropriate boot order options. To ease the process of making the firmware modifications required for Windows To Go, Windows 8 includes a feature named Windows To Go Startup Options that allows a user to configure their computer to boot from USB from within Windows—without ever entering their firmware, as long as their firmware supports booting from USB.
|Enabling a system to always boot from USB first has implications that you should consider. For example, a USB device that includes malware could be booted inadvertently to compromise the system, or multiple USB drives could be plugged in to cause a boot conflict. For this reason, the Windows To Go startup options are disabled by default. In addition, administrator privileges are required to configure Windows To Go startup options.|
If you are going to be using a Windows 7 computer as a host-PC, see the wiki article Tips for configuring your BIOS settings to work with Windows To Go.
Windows supports two types of PC firmware: Unified Extensible Firmware Interface (UEFI), which is the new standard, and legacy BIOS firmware, which was used in most PCs shipping with Windows 7 or earlier version of Windows. Each firmware type has completely different Windows boot components that are incompatible with each other. Beyond the different boot components, Windows supports different partition styles and layout requirements for each type of firmware as shown in the following diagrams.
This presented a unique challenge for Windows To Go because the firmware type is not easily determined by end-users—a UEFI computer looks just like a legacy BIOS computer and Windows To Go must boot on both types of firmware.
To enable booting Windows To Go on both types of firmware, a new disk layout is provided for Windows 8 that contains both sets of boot components on a FAT32 system partition and a new command-line option was added to bcdboot.exe to support this configuration. The /f option is used with the bcdboot /s command to specify the firmware type of the target system partition by appending either UEFI, BIOS or ALL. When creating Windows To Go drives manually you must use the ALL parameter to provide the Windows To Go drive the ability to boot on both types of firmware. For example, on volume H: (your Windows To Go USB drive letter), you would use the command bcdboot C:\windows /s H: /f ALL. The following diagram illustrates the disk layout that results from that command:
This is the only supported disk configuration for Windows To Go. With this disk configuration, a single Windows To Go drive can be booted on computers with UEFI and legacy BIOS firmware.
Windows To Go Startup Options is a setting available on Windows 8 PCs that enables the computer to be booted from a USB without manually changing the firmware settings of the PC. To configure Windows To Go Startup Options you must have administrative rights on the computer and the Windows To Go Default Startup Options Group Policy setting must not be configured.
On the Start screen, type, type Windows To Go Startup Options, click Settings and then press Enter.
Select Yes to enable the startup options.
Tip If your computer is part of a domain, the Group Policy setting can be used to enable the startup options instead of the dialog.
Click Save Changes. If the User Account Control dialog box is displayed, confirm that the action it displays is what you want, and then click Yes
If you choose to not use the Windows To Go Startup Options or are using a PC running Windows 7 as your host computer you will need to manually configure the firmware settings. The process used to accomplish this will depend on the firmware type and manufacturer. If your host computer is protected by BitLocker and running Windows 7 you should suspend BitLocker before making the change to the firmware settings. After the firmware settings have been successfully reconfigured, resume BitLocker protection. If you do not suspend BitLocker first, BitLocker will assume that the computer has been tampered with and will boot into BitLocker recovery mode.