windows-server-2012

Windows Server 2012 R2 : WDS with MDT 2013 and WSUS installation and configuration – part 2

In the Part 1 of this tutorial we have:

  • Installed WADK
  • Installed WDS
  • Installed MDT 2013

Now that we have proceeded these installations we will start to configure it.


 

III – Configuration WDS with MDT

MDT configuration

We will now create the folder, called Deployment Share in which we will store our images, Task Sequences, etc.

Make a rightclick on Deployment Share and click on New Deployment Share.

mdt new deployment share

Enter the path where the Deployment Share will be stored.

deployment share path

Then, we can select the Share name through which the Deployment Share can be accessible.

mdt share name

We continue by entering a description for the Deployment Share (I was a bit in lack of imagination).

mdtp deployment share desc

The next step is to select the options we want to configure for our Deployment Share. Uncheck all and click on Next.

new ds options

We can see the Summary before the Deployment Share creation.

new deployment share summary

Once all the task are successfully completed you will see a confirmation window.

new ds confirmation

And now we can see our new Deployment Share

new ds overview

After creating our Deployment Share we must import the operating system we want to deploy. To begin we will import a Windows Server 2012 R2 Datacenter ISO. Feel free to import the OS you want.

First, you should mount the ISO of the operating system you want to import in order to be able to access some files inside the ISO. Right click on your ISO and click on Mount.

mount iso

In your Deployment Share right click on Operating System and then on Import Operating System.

new ds import os

Select Full set of source file to import raw file from an ISO.

Custom image file allow you to import WIM file from operating system you have already configured and prepared to be deployed.

Windows Deployment Services images import images already configured in an existing WDS server.

import os type

Select the source from where to import the files, here the drive with your ISO.

import os source

After selecting the directory we go directly to the Destination part. Enter the name for the directory where you want to store the images.

import os destination

After clicking on Next, you will see the Summary for the import. Click on Next.

You will then have a progress screen and finally this screen to confirm everything went fine during the importation. On this screen we can see the different images imported from our ISO.

As we can see on the screen above, we have in total four images imported:

  • Two images for Windows Server 2012 R2 Standard, one with GUI and one for Core edition.
  • Two images for Windows Server 2012 R2 Datacenter, one with GUI and one for Core edition.

import os confirmation

As we will only use the Datacenter Edition we will delete the Standard Edition images.
You can also rename your images to make them clearer.

In your Deployment Share go in the Operating System folder, select the two images related to Windows Server 2012 R2 SERVERSTANDARD and Windows Server 2012 R2 SERVERSTANDARDCORE, right click on it and click on Delete.

On the screen below, check “Completely delete these items, even if there are copies in other folders. (Force) and click on Next.

delet eselected item

The screen after will display the summary for the images we are going to delete. Click on Next.

delete item summary

After that, you will see a progress window, once the deletion complete you should see a window like this one. Click on Finish.

delete item confirmation

Ok, we have finished to import our raw images to be deploy in our Deployment Share. Now, we need to update it in order to apply/update the modifications.
Every time you perform modifications on your Deployment Share, it is good to update it before testing.

To update it, it is pretty easy…

Do a right click on your Deployment Share and select Update Deployment Share.

update deployment

On the Options screen select Optimize the boot image updating process and click on Next.

The option Completely regenerate the boot images will rebuild everything from scratch, if you want to start from a clean installation you can select this option, but for now we don’t need it.

update deploy option

The next screen display the Summary. Click on Next.

update deployment summary

During the progress you can see the creation of Lite Touch PE (x64) boot image. These images will be used later with our WDS to allow our client to boot on the WinPE.

update deployment progress

Once the process is over we can see if it is successful or not. Click on Finish to exit.

update deploy confirmation

After the completion, you can check on your Deployment Share path, inside the Boot folder, you should find the images like in the screen below. Remind these, we will use them later.

litepe iso

 

 

WDS Configuration

Our deployment server is now ready to use… or almost!

We now need to configure our WDS and add boot images to allow our client to access our WinPE environment.

Open you WDS console, right click on your server and Configure Server.

Before beginning Microsoft provide us some requirements information, you can read them and click on Next.

wds wizard 1

Our WDS server will be integrated with Active Directory.

wds wizard ad

We select to which client our WDS server will respond (i.e. accept the connection).

Respond only to known client computers this option will make your WDS server to respond only if the client computer has a prestaged Active Directory account.

Respond to all client computers (known and unknown) by selecting this option any computer will be allowed to connect to the WDS server. Selecting this option can be useful if you are deploying a lot of client computer without needing domain integration, for different customers for example.

Require Administrator approval for unknown computers allow you to respond to all computers known and unknown, but, for those which are unknown it still require an administrator to verify and approved it.

For us, it is only a lab so we can select Respond to all client computers, but inside an Active Directory environment it will be more secure to select Respond only to known client computer. Click on Next to continue.

pxe respond all

The next step is to select the path where we will store our images.

wds remote path

The following screen ask you if you want to add images now or later. Uncheck the box, we will add image manually. Click on Finish to exit the Configuration Wizard.

add image server now

It is time to add Boot Images to our WDS server. Right click on the Boot Images container and click on Add Boot image…

add boot image

In the next screen, click on Browse… and select the WinPE x64 image in your Deployment Share folder.

add image path

After, you will have the metadata from your image displayed, you can modify the Image name and Image description.

add image metadata

Then come the Summary for the process. Click on Next.

add image summary

If the process is successfully achieved, you should have displayed The operation is complete. Click on Finish

add image finish

 

We are now finished for the basic configurations for MDT and WDS, now let’s continue further in the part 3 🙂