MDT 2010: Skipping Deployment Wizard Pages

For MDT 2012 version of this post read here.

When I first began deploying images using Microsoft Deployment Toolkit 2010, the most useful resource at my disposal was this table.

It lists the Deployment Wizard pages shown during a Lite-Touch deployment and the customsettings.ini and bootstrap.ini propertys needed to skip them.  It will help you achieve the semi or fully automated LTI Deployment Scenario. You’ll also learn pretty much everything else in between.

Skip this wizard page

Using this property

Configure these properties

Administrator Password

SkipAdminPassword

· AdminPassword

Welcome to the Windows Deployment Wizard

SkipBDDWelcome

 

Choose a migration type

SkipDeploymentType

· DeploymentType

Configure the computer name

SkipComputerName

· OSDComputerName

Configure the target partition

SkipDestinationDisk

· DestinationDisk

· DestinationPartition

Join the computer to a domain or workgroup

SkipDomainMembership

· JoinWorkgroup

      or

· JoinDomain

· DomainAdmin

· DomainAdminDomain

· DomainAdminPassword

Language and other preferences

SkipLocaleSelection

· KeyboardLocale

· UserLocale

· UILanguage

Operating system deployment completed successfully

SkipFinalSummary

 

Operating system deployment did not complete successfully

SkipFinalSummary

 

Packages

SkipPackageDisplay

· LanguagePacks

Ready to begin

SkipSummary

 

Select a task sequence to execute on this computer

SkipBuild, SkipTaskSequence

· TaskSequenceID

· BuildID

Select one or more applications to install

SkipApplications

· Applications

SkipAppsOnUpgrade

 

Set the Time Zone

SkipTimeZone

· TimeZone

      or

· TimeZoneName

Specify credentials for connecting to network shares

by providing properties in next column

· UserID

· UserDomain

· UserPassword

Specify the BitLocker configuration

SkipBitLocker

· BDEDriveLetter

· BDEDriveSize

· BDEInstall

· BDEInstallSuppress

· BDERecoveryKey

· TPMOwnerPassword

· OSDBitLockerStartupKeyDrive

· OSDBitLockerWaitForEncryption

Specify the product key needed to install this operating system

SkipProductKey

· ProductKey

      or

· OverrideProductKey

Specify where to save a complete computer backup

SkipComputerBackup

· BackupDir

· BackupShare

· ComputerBackupLocation

Specify where to save your data and settings

SkipUserData

· UDDir

· UDShare

· UserDataLocation

Specify whether to capture an image

SkipCapture

· ComputerBackupLocation

Specify whether to restore user data

SkipUserData

· UDDir

· UDShare

· UserDataLocation

 

About these ads

About Andrew Barnes

A Scipting and Deployment Specialist.
This entry was posted in Deployment, MDT 2010 and tagged , , , , . Bookmark the permalink.

10 Responses to MDT 2010: Skipping Deployment Wizard Pages

  1. You can also configure all settings such as TimeZone, Locale, etc and just specify SkipWizard=YES to skip the entire wizard instead of skipping each part. ;)

    Like

  2. Leigh Webber says:

    I am confused. My technician machine is W2008 R2. I have added the Windows Deployment Services role, and I have installed the WAIK and the Deployment Workbench (v 5.1.1642.01). I have tried a dozen walk-throughs found on the net, and I have hit a major mental block. I used the Deployment Workbench to create a task sequences for deploying a vanilla Windows 7 machine, then importing it as a reference image. Next, I created a task sequence to deploy that reference image to a target. I logged into the target machine and installed our standard suite of apps. I then created a task sequence to Sysprep and capture that image, which I call Win7WithApps. So now I have a bunch of task sequences. If I create a VM and PXE boot it with F12, the wizard starts up and lets me choose the task sequence. I select my Win7WithApps, and it installs perfectly.

    Now I am trying to perform a completely unattended deployment. I have read about the bootstrap.ini and customsettings.ini files, and I have edited them exactly as described on your (excellent) blog. I use the Deployment Workbench, right-click the deployment share (I have only one DS), choose Properties, then click the Rules tab. I make the edits, click Edit Bootstrap.ini and edit it as well. I close the dialog, then update the deployment share. If I go into the DeploymentShare$\control folder, the bootstrap.ini and customsettings.ini reflect the edits I made.

    But when I start up a fresh VM (I’m using Hyper-V) and press F12, the @#$(*&% Welcome Windows Deployment wizard opens and waits for me to click the huge “Run the Deployment Wizard to install a new Operating System” button. Then it prompts me for credentials to access network shares. But my bootsrap.ini looks like this:

    [Settings]
    Priority=Default

    [Default]
    SkipBDDWelcome=YES
    DeployRoot=\\SPRST001\DeploymentShare$
    UserID=Administrator
    UserDomain=corp.mydomain.com
    UserPassword=Pa$$W0rd
    KeyboardLocale=en-US

    So what am I doing wrong?

    What really confuses me is the Windows Deployment Services piece. How does WDS know anything about what I have been doing in Deployment Workbench? In WDS, the Remote Installation Folder is D:\RemoteInstall. But in DW, my deployment share is K:\DeploymentShare. So what good does it do me to edit bootstrap.ini over on the K: drive, when WDS has no knowledge of that folder at all? I vaguely recall doing an “Add Install Image” in WDS, because it does have a WIM file corresonding to my Win7WithApps image over on DW. Thinking I had to edit something in my d:\RemoteInstall folder, I drilled down to my only image folder, found the Unattend folder inside it, and an ImageUnatted.xml file.Should I be editing that puppy instead?

    And what about Windows System Image Manager? Do I have to use it to create an “answer file”? How does it relate to DW and WDS? All I want is a complete vanilla deployment — exactly like taking all the defaults when you install Windows 7 by hand.

    Help!!

    Like

    • It all looks great exept the UserDomain line. It should be the netbios version of your domain, not the fully qualified domain name.
      From a command prompt type SET U and this should show you what you need for your domain.

      Like

  3. Ben says:

    Andrew, your page was a life saver.

    A TON of people claim to be able to bypass the WDS Client welcome, locale, computer name etc. by using the System Image Manager and generating an unattend.xml from their particular image. It is crazy how people will even make Youtube videos claiming to automate the WDS client page without mentioning clientsettings.ini and bootstrap.ini. This just does not work.

    It is exactly as stated in this page: The clientsettings.ini and the bootstrap.ini are the key to bypassing various screens in the WDS Client (using the LiteTouchx86 image in our case), including the welcome page, time zone, etc. etc. etc.. We jumped for joy after days of banging our heads against a wall, and then modding those two files using this table. It worked beautifully.

    One quick note to others in the same predicament: We had to update our deployment share (full update, not just the changes), and then after the new boot image was generated, we replaced the existing boot image using the WDS snap-in.

    Keep up the good work, Andrew!

    Ben

    Like

  4. Julie B says:

    I have a working Image build with a long task sequence. All is good except that I only have 1 task sequence in the build but the wizard asks me to choose one. Should I just edit my cs.ini and my bootstrap.ini to set the value for TaskSequenceID and BuildID? Your site is full of really good info. thanks

    Like

  5. Klaus B Frederiksen says:

    I am trying to make a ZTI virtual windows 7. Bootstrap.ini and customsettings.ini have been edited, and bypass BDDwelcome. But wants credentials. When I type in the “missing” credentials, all is well. I have placed UserID/UserPassWord/UserDomain in bootstrap.ini, and tried with, and without them in CS.INI. No luck.
    I have searched the net for a solution, and found no new info.
    The total CS.INI I made bypasses what I want it to.

    Like

    • This post covers that topic – http://wp.me/p1v18I-5v

      Like

      • Klaus B Frederiksen says:

        I have made a new deployment share (erased the old), copyed win 7 files, made a new task sequence, edited bootstrap.ini to:
        [Settings]
        Priority=Default

        [Default]
        DeployRoot=\\WDS\DeploymentShare2$
        UserId=administrator
        userDomain=V12
        UserPassword=*****************
        KeyboardLokale=da-DK
        SkipBDDWelcome=YES

        Customsettings.ini is untouched.

        Installation still wants credentials.

        Regards
        Klaus

        Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s