Configuring deployment share rules – Microsoft Surface 3 User Manual

Page 70

Advertising
background image

© 2014 Microsoft

Page 70

Note: It is recommended to use generation 1 virtual machines for image creation because the resulting images are

compatible with a wider range of potential clients. To support PXE boot, generation 1 virtual machines must use a legacy
network adapter.

Configuring Deployment Share Rules

In

Chapter 3

, you learned how to create a new deployment share on the deployment server. If necessary, refer to

Chapter 3

to learn how to navigate to and create the deployment share. During creation, a several options can be

specified to control the behavior of the deployment process. These options result in the enabling and disabling of
specific prompts presented to the user/technician by the Windows Deployment Wizard. In the reference deployment
scenario, described herein, you’ll learn how to configure the options to suppress some of the prompts, thereby reducing
the amount of user interaction required from

Chapter 3

.

To suppress Windows Deployment Wizard prompts, follow this procedure:

1. Create a new deployment share by following the procedure you learned in the

Creating a Deployment Share

section of Chapter 3

, but stop at the Options page.

2. In

Chapter 3

, you selected all options, which resulted in every possible prompt during deployment. In the

reference deployment, some of those prompts are suppressed by unselecting these options, as shown in Figure
4.2:

Ask if a computer backup should be performed – This option can be unselected because no users or data
(except for tests accounts) will exist.

Ask for a product key – This option can be unselected because the product key will be specified in the
deployment task sequence.

Ask to set the local Administrator password – This option can be unselected because the password for the
local Administrator account will be supplied in the task sequence.

Ask if BitLocker should be enabled – This option can be unselected because encryption is not required in a
lab environment where no user data will exist on deployed systems.

Advertising