Windows Deployment, Part 1: Configuring the Deployment Environment

 

• Windows Deployment, Part 1: Configuring the Deployment Environment
• Windows Deployment, Part 2: Installing and Configuring WDS
• Windows Deployment, Part 3: Installing and Configuring WADK
• Windows Deployment, Part 4: Installing MDT 2013
• Windows Deployment, Part 5: Configuring MDT 2013
• Windows Deployment, Part 6: Creating a Deployment Image
• Windows Deployment, Part 7: Creating a Task Sequence
• Windows Deployment, Part 8: Automating our OS Deployment
• Windows Deployment, Part 9: Deploying a vanilla build of Windows 8.1
• Windows Deployment, Part 10: Create your gold master image & prep MDT & WDS for capture
• Windows Deployment, Part 11: Capture your gold master image
• Windows Deployment, Part 12: Further Reading

In this 12 part series,  I will give instructions on how to configure WDS and MDT 2013, and show you how to deploy Windows 8.1, and capture your Gold Master Image. The example is for demonstration purposes only, and is not a representation of Microsoft recommendations or best practices. This article also assumes you have a working knowledge of Windows server.   First of all, we are going to configure WDS and MDT 2013 on Windows Server 2012 R2 Datacentre (fully patched) in an Active Directory environment. Then we are going to deploy Windows 8.1 Enterprise x64 using Lite Touch.

Environment Configuration

WDS and MDT must be installed in an environment that has a functioning DHCP and DNS server, preferably in an Active Directory environment. WDS and MDT do not need to be installed on an AD server (though they can, and will be for this example).   You will need:

• Server 2008 R2 or greater
• NTFS partition of sufficient size to store deployment images
• WAIK – for Windows 7 deployments, or WADK – for Windows 8.1 deployments

Do not install WAIK and WADK on the same server!   This example will be using Windows Server 2012 R2, also acting as a domain controller, DNS server and DHCP server)

• Server name: DC
• Domain: demo.local
• IP: 192.168.5.10

Roles & Features that are installed:

• Active Directory Domain Services
• DHCP
• DNS
• Windows Deployment Services

You will also require a second HDD attached to the server VM. This will act as your NTFS partition that will store your deployment images.

Lets Begin

In active directory, create a user with the following details:

• User: os.deploy
• Password: Pa$$w0rd1
• Member of: Domain Admins

This is not best practice! This account will be used to simply add computers to the domain.  Adding the account to the Domain Admins group is a quick and easy fix for the purpose of this demo only.   Create a new OU for your deployed computers. Call it: Computers_Deployed You will also want to note the distinguished name. In this case its: OU=Computers_Deployed,DC=demo,DC=local Tip:  open AD, select view, Advanced.  Right click on the AD object and select properties. Then chose the attribute editor tab. Find distinguished name and select view.  Copy and paste into notepad, or note down for later. You’ll be needing this!

 

In Part 2, We’ll be installing and configuring WDS!