Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
18Activity
0 of .
Results for:
No results containing your search query
P. 1
Windows Deployment Using MDT

Windows Deployment Using MDT

Ratings: (0)|Views: 7,293|Likes:
Published by Jaime Bertozi
Deploymnet guide using mdt. This guide help you to make a deployment
Deploymnet guide using mdt. This guide help you to make a deployment

More info:

Published by: Jaime Bertozi on Nov 23, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

12/03/2012

pdf

text

original

 
Windows Deployment using MDT
1Introduction
Microsoft Deployment Toolkit (MDT) 2010 is a set of tools which allows you to Deploy Windows (including OSand applications) quickly and without user intervention. This ensures that all PCs are set up in the same wayand can be managed easily.Main features of MDT are:
Automates scripted and image based deployments of Windows XP, Windows 7, Windows Server 2003and Windows Server 2008 R2
Supports 32 and 64 bit platforms
GUI based driver management
Uses Windows PE as boot method
Contains the flexible task sequencer from Microsoft [System Center Configuration Manager 2007(formerly SMS)
Includes the scenarios: New computer, Refresh and Replace
Can re-use techniques of zero administration kit (previous scripted install method)MDT comes with two main flavors: LiteTouch and ZeroTouch. LiteTouch doesn't require any managementinfrastructure and is the method we will use. ZeroTouch is used together with Microsoft System Center Configuration Manager 2007 (formerly SMS).
The instructions below are for a productive environment and for a lab environment using VMware.
2Hardware and Software requirements
The minimum hardware requirements for MDT are listed below. We recommend using the same server for your WSUS server and the software repository.The best way is to set up MDT on a Windows 2008 R2 server although Windows 2003 is also supported. For the first time deployment of a Windows 2008 R2 you should use Sulzer's preconfigured Windows 2008 R2DVD available at\\pus04.pu.sulzer.com\transfer$\IT\CD\Win2008R2-SulzerDVD.Typically you would install the MDT server in a Hyper-V environment. Please see our separate documentationon setting up a Hyper-V server.
Productive environment
Software: Windows Server 2008 R2 (preferred) or Windows Server 2003 Standard Edition with SP2Hardware: 1.0 GHz CPU, 1 GB RAM, 50 GB free disk space (minimum)
Virtual Machine (VM) Lab
Software:VMware Player 2.5 (or Workstation 6.5) and aboveHardware: Intel Core Duo processor or equivalent, 2 GB RAM, 50 GB free disk space (minimum)
3Copy files
Please be aware that some of the files below are very large and should therefore be copied at a time of lownetwork traffic.Copy the following files from\\pus04.pu.sulzer.com\transfer$\it\MDT
MDT.zipcontains program and template files
WAIK.isocontains Microsoft Windows Automated Installation Kit
46436203.doc H.Büchler / 22-Jul-10Page 1/13
 
Copy XP operating system folder "Windows XP English x86 Image" and / or other operating system asrequired from\\pus04.pu.sulzer.com\DeploymentShare$\Operating Systems.If you want to run MDT in a virtual machine lab using VMware setup you need to download in addition of theabove:
MDT-Lab.zipcontains VMware setup (closed environment with DC, MDT Server and client)
VMware-player.zipVMware PlayeDownload WinRAR utility used for extracting ISO files fromwww.rarlabs.com 
4Prepare environment
Production environment (skip this section if you are setting up a VM lab)
4.1.Set up MDT server with Windows Server 2008 R2 or Windows Server 2003 SP24.2.Create partition D: with at least 50 GB of free disk space.4.3.Extract downloaded files MDT.zip to D:\MDT4.4.Copy folder "Windows XP English x86 Image" downloaded above to D:\MDT4.5.Extract downloaded file WAIK.iso to D:\MDT\WAIK
VM Lab environment (skip this section if you are setting up a production environment)
4.6.Set up a PC with Windows XP SP3 and fully patch it. Drive C: should have at least 50 GB free space.4.7.Extract MDT-Lab.zip into C:\4.8.Install VMware Player.4.9.Start VMware Player. Open and start the virtual machine for DC01 in C:\MDT-Lab\VMs\DC01. When theDC is operational start the virtual machine MDT in C:\MDT-Lab\VMs\MDT.User name: AdministratoPassword: passwordDC01 is the Domain Controller with AD, DNS, DHCP installed.MDT is the MDT deployment server.
Note:
To log on in the VM press Ctrl+Alt+Ins (if you connect via remote desktop you might useCtrl+Alt+End). If you want to power off (without shutting down a machine) go to menu "VMware Player",click "Troubleshoot" then either "Reset" or "Power Off and Exit".4.10.When logged on set the regional settings to suit the keyboard you are using.4.11.In the MDT VMware, click menu "VMware Player / Shared Folders…", select "Always enabled", check"Map as a network drive in Windows guests" and click OK.4.12.You should now see the drive Z:\ in the MDT guest. Extract the files MDT.zip, WAIK.iso to D:\MDT4.13.Copy folder "Windows XP English x86 Image" downloaded above to D:\MDT
5Create a domain user account for unattended setup
We will create a user account called "Setup" which will be used for connecting to the deployment share andadding computers to the domain. If you have used unattended setup before then you will already have thisaccount and you can skip this step.5.1.On the DC start "Active Directory Users and Computers"5.2.Click "View" then check "Advanced Features"5.3.Create a user called "Setup" (if not already existing). This account must not
 
be in the domainadministrators group. The account should have Universal Principal Name (UPN)setup@xxxx.yy.sulzer.com where xxxx.yy is your domain name in the Sulzer forest. (in the lab:Setup@sulzer.local)Uncheck "User must change password at next logon"5.4.Right-click the "Computers" container, then click "Properties".5.5.On the "Security" tab, click "Advanced"5.6.On the "Permissions" tab, click "Add…" then type “Setup” and click "OK".5.7.Make sure the "This object and all child objects" option is displayed in the "Apply onto" box.5.8.From the "Permissions" box, click to select the "Allow" check box next to "Create Computer Objects"and "Delete Computer Objects" then click "OK".
46436203.doc22-Jul-2010Page 2/13
 
5.9.Click "Add…" again then type “Setup” and click "OK". In the "Apply" onto box, click "Computer objects".5.10.In the "Permissions" pane, click to select the "Allow" check box next to "Write All Properties" and "ResetPassword". Select the check box "Apply these permissions to objects and/or containers within thiscontainer only". Click "OK" until the change is made. See alsohttp://support.microsoft.com/default.aspx?kbid=330095
6Setup Windows Deployment Services (WDS)
In our environment we use WDS as a replacement for the TFTP service used before. As soon as you startWDS the TFTP server will not work any more. If you want to revert back to your existing TFTP server at anytime just stop the WDS service.The WDS Server should be located on the same server that you use for MDT.6.1.For Windows Server 2008 R2:In the left pane of "Server Manager" right-click "Roles" and select"Roles". Select "Windows Deployment Services" and accept the defaults of the following screens.Reboot the server.For Windows Server 2003: On the MDT Server, go to "Control Panel" and select "Add or RemovePrograms". Click "Add/Remove Windows Components". Select "Windows Deployment Services" andclick "Next".Under Windows 2003 you will be asked for setup files. Point to "C:\WINDOWS\source\i386". If you don'thave that directory make absolutely sure you point to a directory with Windows 2003 SP2 otherwiseWDS will not work.Complete the installation and reboot the server.Go to Start / Programs / Administrative Tools and select "Windows Deployment Services".6.2.From "Administrative Tools" start "Windows Deployment Services", expand "Servers", right-click your server and select "Configure Server". Click "Next" on the first screen6.3.When prompted for the "Remote Installation Folder Location" use "D:\RemoteInstall" and click "Next".6.4.On screen "PXE Server Initial Settings" select "Respond to all (known and unknown) client computers".Do not check the "For unknown clients, notify administrator and respond after approval". Press "Finish"6.5.Do not add images when prompted to do so. Click "Finish". If you get the message "Invalid pointer" justignore it and click "OK" (It’s a bug in the MMC snap-in, fixed in Windows Server 2008)6.6.If your MDT server is on Windows 2003: start a command prompt and type the following command toenable detection of x64 clients):WDSUTIL /set-server /architecturediscovery:yes
7DHCP configuration
7.1.On the DC start DHCP management and right-click "Server Options" and select "Configure Options…"7.2.Select Option 67, Bootfile Name and set it to "boot\x86\wdsnbp.com" (without quotes)7.3.Select Option 66, Boot Server Host Name and set it to the WDS server name (FQDN). If you haveseveral geographical locations with multiple MDT servers you would add a scope option for eachlocation.
46436203.doc22-Jul-2010Page 3/13

Activity (18)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Manoj Kumar added this note
nice document on microsoft deployment toolkit
ausnetit liked this
Tom Jones liked this
Alex Moretti liked this
ausnetit liked this
Miquel Domenech liked this
Ronnie Ekvall liked this
Jim Bongiovanni liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->