Deploying Windows Server VMs with Microsoft Deployment Toolkit 2013 – Part III

This posting is ~6 years years old. You should keep this in mind. IT is a short living business. This information might be outdated.

In part I and part II of this series I showed how to install the WDS role, MDT 2013 and ADK for Windows 8.1. I showed the process to import the OS images and the necessary drivers for our deployment. Now it’s time to bring MDT to life. Let’s start with part III of this series.

User for deployment share access

During the deployment process Windows PE needs access to the deployment share. For this, we need to create a user account that has the priviledges to access the deployment share. You can simply create a local user on your MDT server.

mdt2013_create_user_1

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

VMware Tools package

Before we can install the VMware Tools during the deployment, we have to build a package. Building a package is nothing more than adding the source files to the deployment share and providing a command line for the unattended installation. Right click the menu item “Application” and choose “New Application” from the context menu.

create_app_step_1

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

In the “New Application Wizard” select the first menu item “Application with source files”.

create_app_step_2

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

After clicking “Next” we need to provde a publisher (optional) and a name for the application. Because we need the 64-bit version, we add this to the application name.

create_app_step_3

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Now we need access to the VMware Tools sources. This can be the extracted or mounted VMware Tools ISO. In my case I pointed to the mounted ISO.

create_app_step_4

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

The name is automatically generated from the publisher and application name.

create_app_step_5

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Now we have to provide the command line for the installation. The necessary command line can be found in KB1018377.

The switch “REBOOT=R” suppress the reboot. The reboot is triggered by MDT. We will enable this in the properties of the application.

create_app_step_6

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Go through the summary and click “Next”.

create_app_step_7

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

At the end just click “Finish”.

create_app_step_8

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Enter the properties of the application and take a look at application GUID. You can use the GUID and add it to the CustomerSettings.ini. Then the application will installed during every deployment, regardless of the OS. We will use another way: We use the task sequence to install the application.

create_app_step_9

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

On the “Details” tab enable the reboot after the installation of the application.

create_app_step_10

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Congratulations. You’ve just created your first application package with MDT. :)

General settings

Open the Deployment Workbench and right click the deployment share. Select “Properties”. On the “General” tab enable multicast for this deployment share.

mdt2013_general_enable_multicast_1

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Switch to the “Rules” tab.Yo will see the content of the CustomSettings.ini, which can be found in the Control directory on the deployment share, e.g. D:\DeploymentShare\Control. The CustomSettings.ini is used to control the deployment. It controls which settings used by the deployment wizard. This is the content of my CustomerSettings.ini.

The settings will skip all wizards, set the time zone, language settings etc.

There’s another button: “Edit Bootstrap.ini”. The bootstrap.ini contains the information how to access the deployment share, e.g. user credentials or IP settings. We need to add the credentials of our newly created user to the bootstrap.ini. Because it’s a local user, the domain is set to the computername of the MDT server.

Creating a Task Sequence

A task sequence provides the mechanism for performing multiple steps or tasks on a computer without requiring user intervention. Right click “Task Sequence” in the Deployment Workbench and select “New Task Sequence” from the context menu.

create_task_step_1

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Enter a sequence ID, a descriptive name and, if you like, a comment.

create_task_step_2

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

We have to use the “Standard Server Task Sequence” template.

create_task_step_3

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Now we need to select an OS image. Because we want to deploy a Windows Server 2008 R2 Standard, we select the appropriate image.

create_task_step_4

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

We don’t want to specify a product key now. Just hit “Next”.

create_task_step_5

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Enter full name, organization etc.

create_task_step_6

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Enter your incredible secret password.

create_task_step_7

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

That’s it. Check the summary and click “Next”.

create_task_step_8

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Finish the dialog and go to the task sequence properties. Select the “Task Sequence” tab and choose “Install Applications”. Browse the applications and select the VMware tools application that we created earlier.

create_task_step_10

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Click “OK”.

Update the deployment share

Before we can deploy our first server, we have to update the deployment share. During this process, the boot images are build and the applications are created on the deployment share. Right click the deployment share in the Deployment Workbench and select “Update Deployment Share”.

update_share_step_1

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Simply follow the wizard.

update_share_step_2

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Click “Next” and finish the dialog.

update_share_step_3

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Adding boot images to Windows Deployment Service (WDS)

Now we can add the Windows PE images to the WDS. Start the server manager or start the MMC. Right click “Boot Images” and then “Add Boot Image…”.

wds_image_import_2

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Choose the image you want to import. There are two images: A 64-bit and a 32-bit image.

wds_image_import_3

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Simply accept the default name.

wds_image_import_4

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Go through the summary and click “Next”.

wds_image_import_5

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Finish the dialog and repeat it, if necessary, for the 32-bit image.

wds_image_import_6

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

The deployment

Create a new VM. I used a standard W2K8 R2 VM with 1 vCPU, 4 GB RAM, VMXNET3 NIC and VMware paravirtual SCSI controller for my tests.. Start the VM. Usually the boot process goes directly into the PXE boot screen, because no OS is installed. Wait for the DHCP response and press F12 if offered. Choose the x64 Windows PE enviroment. Now the boot images is transferred from the WDS server.

deploy_step_1

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

Because we skipped most of the wizards during the deployment wizard, we only need to chosse a task sequence. Select the W2K8 R2 Standard sequence and start the deployment.

deploy_step_2

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

In the WDS MMC you can watch the transmission process of the image.

deploy_step_3

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

After several reboots you should see a shiny new W2K8 R2 standard VM with VMware Tools. The whole deployment from the  start of the VM until the VM is ready to use took on my HP Micro Server round about 15 minutes.

deploy_step_4

Patrick Terlisten/ www.vcloudnine.de/ Creative Commons CC0

If you have any further questions, just leave a comment.

Patrick Terlisten
Follow me

3 thoughts on “Deploying Windows Server VMs with Microsoft Deployment Toolkit 2013 – Part III

  1. Curtis Williams

    Followed your guide. During the deployment phase, I am getting “Not enough memory resources are available to process this command”.

    How can I over-come this obstacle?

    Reply
  2. Pravin kale

    Hello Sir,
    I want deployment window SOE 2016 using Vmware tool 10.01.and SSCM .How do I perform.need your help.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *