Driver Injection
All Dell Drivers can be found here (at least at time of writing this doc)
http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.aspx
Driver Injection is a very simple task.
Expand the deployment share (\deployment$\mdt) from within the “Deployment Workbench”
Select “Out-of-Box-Drivers”
Right click “Out-of-Box-Drivers”
Select “Import Drivers”
You will then be presented with the “Import Driver Wizard” and asked to specify the “Driver source directory”, this is the location of the drivers that you want to import into MDT. There is also a checkbox here to import duplicate drivers. I advise against this UNLESS the existing driver needs replacing.
Click “Next” and you are presented with a summary, Click “Next” again to started the import
CustomSettings.ini settings
Note: The YES' and NO's have to be UPERCASE.
[Settings][Default]OSInstall=YESUserDataLocation=NONE
SkipAppsOnUpgrade=YES
SkipCapture=YES
The 3 above are used for upgrades
SkipAdminPassword=YES
Ask the 'user' to input an admin password when they are building the machine.
SkipProductKey=YES
Has the machine talk to the KMS server.
SkipBDDWelcome=YES
Don't make me click next to get to a useful prompt.AdminPassword=THEPASSWORD
Put what you want here for the local admin password.
SkipDeploymentType=YES
DeploymentType=NEWCOMPUTER
SkipUserData=YES
This formats the HDD and does not save user data.
SkipDomainMembership=NO
JoinDomain=DOMAIN
DomainAdminDomain=DOMAIN
You can pre-populate this to save some typing when telling the setup what domain to join.
SkipBuild=NO
BuildiD=Test1
In MDT you can have several different builds -- this lets you choose which one to prompt for or automatically start building with.
SkipComputerName=NO
ComputerName=TEST-COMPUTER
Prompt for the computer name.
SkipPackageDisplay=NO
SkipApplications=NO
Show what packages get installed and allow the person running the build to check off what gets installed.
SkipLocaleSelection=YES
UILanguage=en-AU
UserLocale=en-AU
KeyboardLocale=0c09:00000409
Lookup these values if you need them to be different.
SkipTimeZone=YES
TimeZoneName=Australia Standard Time
Look it up if you need something different here.
SkipBitLocker=YES
We are not going to use BitLocker
SkipSummary=NO
Shows the values you have either put into this CS.ini file or typed into the dialogs to check they are correct.
CaptureGroups=NO
Store the members of the current groups on the machine so they can be readded after the machine is built.
SLShare=\\COMPUTER\logs$
Where some logs will be saved at on a network machine if you want them to be. I had a very difficult time getting this to work, but it is very nice when you run into problems with your deployment (and you will).
Home_page= http://www.mycompany.com/
Sets the defaultIEhomepage.
StagingOU=OU=VistaTest,DC=DOMAIN,DC=ad,DC=COMPANY,DC=com
DomainDC=DOMAIN.ad.COMPANY.com
These are added in so that msi’s can be applied. The DomainDC value has to be something that the WinPE 'install' can resolve. The StagingOU is where you want your machine to be housed on a temp basis so that you can get around any policies that may cause you problems while doing installs.
Bootstrap.ini settings
Boot:
[Settings]
Priority=Default
[Default]SkipBDDWelcome=YES
DeployRoot=\\ SERVER\deployment$\mdt
UserDomain=DOMAIN
UserID=admin
SkipBDDWelcome=YES
Gets rid of the 'hi welcome to the deployment click next to do anything useful' screen.
DeployRoot=\\SERVER\deployment$\
The server share where you have your deployment point at.
UserDomain=DOMAIN
The domain that the below UserID is a part of that let's you have access to the above DeployRoot folder.
UserID=admin
The user name you use to connect to the DeployRoot share.
Image Gather
Important I USE TWO “CustomSettings.ini” one is used for Deployment and one for Gathering of images when not being used I give the file a prefix of what it actually does. i.e. Capture_CustomSettings.ini. A FYI the Gather is the basic customsetting.ini before any mods.
Log on to local machine (NOT DOMAIN) as administrator
Map the deployment share
“net use *\\SERVER\deployment$ /user:SERVER\username”
You should be prompted the domain password
Browse to the “MDT\Scripts” folder and double click on “Litetouch.wsf”
Creating a new Task Sequence for Upload
A NOTE BEFORE BEGINNING: FAMILIARIZE yourself with MDT, and its functionality, especially the area concerning task sequences. MDT has a built-in reference library which is broken down into index format, additionally; the library has built into it step by step instructions for most MDT related tasks. The library is also interconnected with different MDT tools for technical functionality and easy reference.
1. When starting the task sequence, you will be launching the MDT 2010 workbench on the MDT VM. When launched, you will click the task sequence option, once selected look to the right side of the screen and click ‘New Task Sequence’ a variety of other options exist, but ignore those for now.
2. Once clicked, MDT will initiate a wizard. Simply select a name, ID, and add any required notes for your Task, then click the drop down for pre-existing templates, select the Sysprep and Capture Template. Make sure to select the correct Operating System, that is, the one which matches the Operating System you intend to capture.
3. The actual task sequence is run from the computer you are intending to capture.
4. **A common mistake at this point is to boot the reference computer from your LiteTouch image and start this task sequence. Don’t do it.
5. To run the task sequence, you connect to the deployment share and launch the LITETOUCH.WSF through manual interaction with the command prompt.
6. RUN CMD – enter:
net use \\mdt\DeploymentShare$ /user:domain\username
7. Once the connection is established, execute LiteTouch.WSF
cscript \\mdtserver\DeploymentShare$\Scripts\LiteTouch.WSF
8. Once executed, MDT Wizard screens will initialize and appear, asking for prompts related to completing the task sequence.
9. Select the task sequence you created earlier in step 3.
10. Use your Sysprep and Capture option, and supply the location for storage and name of the image you are capturing.
11. Supply your login credentials. – Follow the Wizard Steps.
12. MDT will assume control, and the task sequence will run through its course here, assuming it can run uninterrupted. MDT will copy the reference computer, launch the sysprep and apply the LiteTouch Image. The computer will reboot during this phase.
13. The computer will reboot, and in this portion the size of the image, and speed of the computer govern the time required for the installation. Expect this step to take a substantial amount of time.
14. After the capture is completed, you can go back to MDT – and import the image, as a customized image file in MDT itself, for use in future task sequences.
15. To do this, click Operating Systems, in the index on the left side. Look to the right, and click ‘Import Operating System,’ this will initialize another wizard.
16. Select Custom image file and hit next – find your file. Most likely under
D:\DeploymentShare\Captures
17. Include the setup files for the OS which you are importing and complete the wizards. This is important, if you select the wrong OS – the system will not install on subsequent attempts.
18. Should be done! The file will be available for use with any new task sequence you need.
Image Deploy
Important I USE TWO “CustomSettings.ini” one is used for Deployment and one for Gathering of images when not being used I give the file a prefix of what it actually does. i.e. Capture_CustomSettings.ini. A FYI the Gather is the basic customsetting.ini before any mods.Boot PC or Laptop
Press the F12 or Delete key (or whatever key required) to select boot from device
Select the NIC and press enter
At this point the machine will send a request to the DHCP Server for an IP address
Once the machine has received an IP address Press F12 as directed on the screen
You will then be presented with the “Windows Boot Manger” options Lite Touch Windows PE (x86) 32 Bit or Lite Touch Windows PE (x64) 64 Bit. Select the option for the operating system you wish to install.
The next window you will be presented with is the “Welcome Windows Deployment” for deployment purposes click on the “Run the Deployment Wizard to install the new Operating System”
You will then be presented with a request for you User Credentials. The account used must be your admin account.
Once you have entered your credentials, you will be presented with a screen where you will have a selection of image builds to choose from.
Select the radio button next to image you require and click next
The next screen that you are presented with refers to user data.
If all goes well and there are no errors (see below for more information on possible errors) you will presented with a "Operating system deployment completed sucessfully.
unless the “CustomSettings.ini” has the line SkipFinalSummary=Yes which ours does but check to be sure. Remember the CustomSettings.ini can be found in “deployment$\MDT\Control”
Errors encountered
Error
The task sequence has been suspended. LiteTouch has encountered and Environment Error (Boot into WinPE!)
OK to Reboot
Solution
There are two primary scenarios where this can happen (although not limited to these). When booting into a LiteTouch WinPE image, we can encounter this error.
With ”The task sequence has been suspended” dialog up
don’t click OK,
press F8,
run diskpart right out of the PE instance.
So boot from standard Windows PE
open diskpart,
select disk 0
type “clean”
Following this, you will be able to boot the LiteTouch.wim install and start over again.
Error
If during a LiteTouch installation the process is interrupted, files from the task sequence will be left on the hard drive. This will cause any attempt to restart the LiteTouch process to fail
Solution
In that case remove the c:\minint\ and/or c:\_SMSTaskSequence directory and reboot back into WinPE.
Error
While performing Lite Touch deployments it seemed that randomly deployments would fail at the Format and Partition Disk step in the task sequence.
Examining the BDD.LOG showed this error:
FAILURE ( 7705 ): command: FORMAT.COM C: /FS:NTFS /V:OSDisk /Y /Q FAILED with error = 4
The first step I had him do was reboot the computer and run through the steps that the script ztidiskpart runs manually.
Those steps are:
1. Boot in Windows PE
2. Press F8
3. Run diskpart
4. select disk 0
5. clean
6. create partition primary
7. assign letter=c:
8. active
9. exit
10. format c: /fs:ntfs /v:OSDisk /Y /Q
Again the format command failed. I then immediately tried the format again and it worked. So this was truly an intermittent problem. My suspicions went up that this was driver related and I checked what kind of storage controller is in the laptop and it was the Intel Matrix Storage Driver. I checked Intel’s web site and downloaded the new driver from here:
http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=17882&lang=eng
After removing the old Intel Matrix Driver from Deployment Workbench, adding this one back in, and regenerating his boot images it worked!
If you ever run into any intermittent format or partitioning problems start investigating the storage driver!
