Share this post!

Back to Part 2: Creating MDT Applications and the Moonshot Task Sequence

Installing and Configuring Windows Deployment Services for Unattended PXE

Now for a little piece that I didn’t previously document in my MDT posts…Configuring Windows Deployment Services. Seeing that Moonshot nodes don’t have physical or virtual optical drives, we need PXE boot to get the devices on the network and connected to MDT to install the image.  This process is actually pretty straight forward, let’s get started…

Open Server Manager and click Manage in the top right, then Add Roles and Features:

042

Click Next, Next, Next. Under the Server Roles section scroll down and select Windows Deployment Services.

043

Click Add Features:

044

Click Next four times and then Install:

045

When finished, click Close. Launch Windows Deployment Services console from the Start Menu:

046

Expand Servers. Right click the server name and click Configure Server:

047

Click Next:

048

Select Standalone Server and click Next:

049

Click Next:

050

Click Yes:

051

Select Respond to all client computers and click Next:

052

Uncheck Add images now and click Finish:

053

Right click Boot Images and select Add Boot Image:

054

Type ‘C:\DeploymentShare\Boot\LiteTouchPE_x64.wim’ in the path and click Next:

055

Click Next:

056

Click Next:

057

Click Finish:

058

Right click the server and click Properties:

059

On the Boot tab, change both settings to ‘Continue the PXE boot unless the user presses the ESC key’:

060

Next to x64 architecture, click Select and choose the LiteTouch image:

061

Review and click OK:

062

Now that we have everything setup, let’s test out our deployment process.  To save time a be a little more narrative, I’ve recorded a video of the Moonshot specific tasks that you can find below:

I would highly encourage you to use this as a starting point, but customize MDT even further to add applications, configure settings, and automate the build of your master Moonshot image. If you’re going to use Moonshot in a non-persistent manner, you’ll want to capture the image to provisioning services as described in HP’s guide. Otherwise, if you’re going to use Moonshot in a persistent manner, you may want to use this process, or System Center Configuration Manager (SCCM) with Windows Deployment Services (WDS) to manage your image deployment process.  Below is an example of what a task sequence can look like if you really go to town with MDT task sequence automation:

066

Remember, Microsoft Deployment Toolkit (MDT) is completely free as a Solutions Accelerator from Microsoft. So, if you’re still building your master images by hand, for virtual or Moonshot, you have no more excuses! Happy automating!

If you have any questions, comments, or feedback, feel free to comment below, message me on twitter or send me an e-mail.

Thanks!
–@youngtech

Share this post!