Owner's manual

therefore will not appear. The Installation Progress window will appear to show the progress of the deployment as it

processes the steps of applying the image, installing applications, and installing Windows Updates.

Upon completion, the Installation Progress window will close and the computer will be left ready for use logged in as

the local administrator account. The computer will be joined to the domain, so an end-user only needs log in to begin

using the computer.

Creating the Offline Deployment Share

Now that the production deployment share is running and ready for deployment to computers connected to the

network, the next step is to create the offline deployment share. The offline deployment share will be linked to the

production deployment share and used to create offline media for deployment to systems which are not connected to

the network.

A separate offline deployment share will be used for two primary reasons:

1. To keep the size of stored components down to minimize storage requirements of the USB stick that will be

used as offline media.

2. To specify different deployment share rules. For example, without network connectivity, domain join will fail, so

in the offline deployment share the Windows Deployment Wizard will be configured to join the computer to a

workgroup instead of a domain. Another example is to leave at least one prompt to ensure that an accidental

boot to the USB stick does not overwrite the operating system if it was accidentally inserted into an unintended

computer.

Follow the procedure outlined in the Creating a Deployment Share section of Chapter 3 to create the offline deployment

share.

The offline deployment share can be created alongside the production deployment share on the same server, so that

once created the deployment server could have three deployment shares open. The deployment workbench can open

deployment shares from either a local drive or a network location, as shown in Figure 5.14.