Monthly Archives: May 2011

MDT 2010–From Zero to Deploy–The complete series

Please note, this is not perfect.  I’ll take comments on how we can get this polished up and improved Smile

But my hope here is that there are enough “nuggets” that almost any tech could at least pick up MDT and get themselves running for at minimal an LTI installation or a NEAR ZTI install

It’s in my own words, I’m not a writer, I’m just an Energized Tech who loves to help out.  If this is any way helpful to you?  Pass it along.  “Share and enjoy”

Just don’t go near any “Nutrimatic Dispensers” when you “Share and Enjoy”

 

Part 1 – Installing MDT 2010 on your computer

Part 2 – Creating A Deployment Share

Part 3 – Importing an Operating System

Part 4 – Importing Applications

Part 5 – Silent Install of Applications – tips and tricks

Part 6 – Creating a Silent Office Installation

Part 7 – Importing Updates and Packages

Part 8 – Importing Drivers and staying organized

Part 9 – Creating Dependencies in Applications and Updates

Part 10 – Creating a Task Sequence

Part 11 – Creating Selection Profiles

Part 12 – Creating Deployment Media

Part 13 – Beginning to Skip Screens and Auto answer questions

Part 14 – A quick look at the Task Sequence and Unattend.xml

Part 15 – Using WDS with MDT to create a network based PXE install

FacebookTwitterGoogle+Share

MDT 2010–From Zero to Deploy–The complete series

Please note, this is not perfect.  I’ll take comments on how we can get this polished up and improved Smile

But my hope here is that there are enough “nuggets” that almost any tech could at least pick up MDT and get themselves running for at minimal an LTI installation or a NEAR ZTI install

It’s in my own words, I’m not a writer, I’m just an Energized Tech who loves to help out.  If this is any way helpful to you?  Pass it along.  “Share and enjoy”

Just don’t go near any “Nutrimatic Dispensers” when you “Share and Enjoy”

 

Part 1 – Installing MDT 2010 on your computer

Part 2 – Creating A Deployment Share

Part 3 – Importing an Operating System

Part 4 – Importing Applications

Part 5 – Silent Install of Applications – tips and tricks

Part 6 – Creating a Silent Office Installation

Part 7 – Importing Updates and Packages

Part 8 – Importing Drivers and staying organized

Part 9 – Creating Dependencies in Applications and Updates

Part 10 – Creating a Task Sequence

Part 11 – Creating Selection Profiles

Part 12 – Creating Deployment Media

Part 13 – Beginning to Skip Screens and Auto answer questions

Part 14 – A quick look at the Task Sequence and Unattend.xml

Part 15 – Using WDS with MDT to create a network based PXE install

FacebookTwitterGoogle+Share

MDT 2010–From Zero to Deploy–Part 15

So all the fun stuff is over and we’re done…

No wait.  We’re not.  I was mumbling something out using “WDS” or “Windows Deployment Services”

This is simply a Role you add in Server 2008 or Server 2008R2.  This is free to use so flip it on Smile

Just go into the Server Manager, right click on “Roles”, choose “Add Roles”, click next and choose “Windows Deployment Services”

image

We’re not going to go TOO deep into it’s setup.  Yes you can have multiple servers across many environments, blah blah blah.  Today we’re going to stick with the basics.  So just take all the default settings and move along (“These are not the Droids you’re looking for ….”)

You’ll find “Windows Deployment Services” as a new entry in your Administrative Tools.  Clicking on it you’ll see the name of your server under “Servers” with a Yellow Exclamation mark

image

So Right click on your server name in the WDS console and choose Configure Server.  This will present a nice simple step by step Wizard to get you going.  It’s going to ask to create a new folder structure for just WDS.  If this is the same server as MDT, LET IT DO THIS.  Remember to treat MDT and WDS as two separate entities.  One CREATES the images, the other is a tool to enable DEPLOYMENT of images.  Just like with another Role or Application.  Give them their own Sandbox.  Perhaps some Chocolate Chip cookies (Or are they no longer on the HCL for Server 2008R2?)

It will create a folder called C:\RemoteInstall for it’s stuff and then ask you how you want to respond to PXE requests.  If you need 100% control use “Respond only to known client computers” otherwise just choose “Respond to All” (Don’t worry, you can always turn this on or off as you need it)

When it asks you if you want to add images to Windows Deployment  Server now, clear the box and don’t for the moment.

To make this all work we need three things, a Boot Image, DHCP and a DeploymentShare created by MDT.

Right click on “Boot Images” in the Left hand console in Windows Deployment Services and browse to one of the LiteTouch.wim files that were created earlier in your C:\MyMedia folder. They will typically be under \Content\Deploy\Boot . In our case you may find two (One is a 64bit bootable WIM file and one is a 32bit bootable WIM file) You can add in each one, it won’t hurt.

Just browse to each one of these files, follow the step by step simply wizard and you’ll have two new bootable images within WDS

If nothing else is done, your environment should now (as long PXE boot is enabled on a network card) be able to now choose to boot from the WDS server from one of these two WIM files.

Now we haven’t configured them so to make it install from the DeploymentShare you’ll actually have to provide credentials and the UNC pathname of the share.  From this point it will at least be an LTI install if you haven’t configured it otherwise for the DeploymentShare itself.

But like everything in MDT, this can be tweaked even further.

So if you would like to have that bootable file have the USERID and PASSWORD and UNC pathname already known (so this becomes even simpler) just go to the Properties of the C:\MyMedia folder, Click on the “Rules” and add in the following lines to your configuration

DeployRoot=\\MYMDTSERVERNAME\DeploymentShare$
UserDomain=CONTOSO
UserID=USERIDIWITHACCESSTOTHATSHARE
UserPassword=AnotherPasswordIShouldNotHaveSharedWithTheWorld

You’ll have to right click on the MyMedia in MDT and choose “Update” to rebuild the WIM files.   Once this is done just right click on each entry in WDS for the Boot files and choose “Replace Image” and just follow the same procedure as last time to browse to those files in the C:\MyMedia folder.

Well it’s now officially the Long Weekend.  My fingers are numb.  My brain is empty and I want to go play with some more Powershell Smile

I’ll post a single posting tomorrow with the entire series and links so you could just access that if you like.   If you have any comments, add them in as this is something I’d like to see the community join in with.  MDT is fantastically amazing and Powerful tool.  If there is any way I can help YOU get off the ground with it, ping me.   Because we all need shorter days and more time to relax

MDT 2010 gives us just that Smile

Thanks Michael Niehaus for creating such a Kick Ass tool! YOU ROCK!

FacebookTwitterGoogle+Share

MDT 2010–From Zero to Deploy–Part 15

So all the fun stuff is over and we’re done…

No wait.  We’re not.  I was mumbling something out using “WDS” or “Windows Deployment Services”

This is simply a Role you add in Server 2008 or Server 2008R2.  This is free to use so flip it on Smile

Just go into the Server Manager, right click on “Roles”, choose “Add Roles”, click next and choose “Windows Deployment Services”

image

We’re not going to go TOO deep into it’s setup.  Yes you can have multiple servers across many environments, blah blah blah.  Today we’re going to stick with the basics.  So just take all the default settings and move along (“These are not the Droids you’re looking for ….”)

You’ll find “Windows Deployment Services” as a new entry in your Administrative Tools.  Clicking on it you’ll see the name of your server under “Servers” with a Yellow Exclamation mark

image

So Right click on your server name in the WDS console and choose Configure Server.  This will present a nice simple step by step Wizard to get you going.  It’s going to ask to create a new folder structure for just WDS.  If this is the same server as MDT, LET IT DO THIS.  Remember to treat MDT and WDS as two separate entities.  One CREATES the images, the other is a tool to enable DEPLOYMENT of images.  Just like with another Role or Application.  Give them their own Sandbox.  Perhaps some Chocolate Chip cookies (Or are they no longer on the HCL for Server 2008R2?)

It will create a folder called C:\RemoteInstall for it’s stuff and then ask you how you want to respond to PXE requests.  If you need 100% control use “Respond only to known client computers” otherwise just choose “Respond to All” (Don’t worry, you can always turn this on or off as you need it)

When it asks you if you want to add images to Windows Deployment  Server now, clear the box and don’t for the moment.

To make this all work we need three things, a Boot Image, DHCP and a DeploymentShare created by MDT.

Right click on “Boot Images” in the Left hand console in Windows Deployment Services and browse to one of the LiteTouch.wim files that were created earlier in your C:\MyMedia folder. They will typically be under \Content\Deploy\Boot . In our case you may find two (One is a 64bit bootable WIM file and one is a 32bit bootable WIM file) You can add in each one, it won’t hurt.

Just browse to each one of these files, follow the step by step simply wizard and you’ll have two new bootable images within WDS

If nothing else is done, your environment should now (as long PXE boot is enabled on a network card) be able to now choose to boot from the WDS server from one of these two WIM files.

Now we haven’t configured them so to make it install from the DeploymentShare you’ll actually have to provide credentials and the UNC pathname of the share.  From this point it will at least be an LTI install if you haven’t configured it otherwise for the DeploymentShare itself.

But like everything in MDT, this can be tweaked even further.

So if you would like to have that bootable file have the USERID and PASSWORD and UNC pathname already known (so this becomes even simpler) just go to the Properties of the C:\MyMedia folder, Click on the “Rules” and add in the following lines to your configuration

DeployRoot=\\MYMDTSERVERNAME\DeploymentShare$
UserDomain=CONTOSO
UserID=USERIDIWITHACCESSTOTHATSHARE
UserPassword=AnotherPasswordIShouldNotHaveSharedWithTheWorld

You’ll have to right click on the MyMedia in MDT and choose “Update” to rebuild the WIM files.   Once this is done just right click on each entry in WDS for the Boot files and choose “Replace Image” and just follow the same procedure as last time to browse to those files in the C:\MyMedia folder.

Well it’s now officially the Long Weekend.  My fingers are numb.  My brain is empty and I want to go play with some more Powershell Smile

I’ll post a single posting tomorrow with the entire series and links so you could just access that if you like.   If you have any comments, add them in as this is something I’d like to see the community join in with.  MDT is fantastically amazing and Powerful tool.  If there is any way I can help YOU get off the ground with it, ping me.   Because we all need shorter days and more time to relax

MDT 2010 gives us just that Smile

Thanks Michael Niehaus for creating such a Kick Ass tool! YOU ROCK!

FacebookTwitterGoogle+Share

MDT 2010–From Zero to Deploy–Part 14

So now we’ve MDT 2010 to a level where we could actually make a seamless install.

No we haven’t.  I lied again.

What we’ve done is bring a lot of automation but there are things that can and should happen even further.

What about Windows Updates?   What about things that can happen WITHIN that installation as it’s installing?  Perhaps you’d like to NOT join to the Domain and leave the password in clear text?

That’s the power contained within your Task Sequence.  Remember when I said it was a “Predefined Template” but you COULD go into it deeper?  We’re about to open the hood.  Let’s pull up the properties of the Task Sequence created before.

image

We’re going to click on “Task Sequence” which is (Are you ready folks?) the “SEQUENCE” your task is going to run in.

Taking a quick look at our Task Sequence it’s really almost a workflow more than code.   Stating what we’re planning on doing.  If you look near the bottom you’ll see two sections marked “Windows Update (Pre-Application Installation)” and “Windows Update (Post-Application Installation)”

image

Presently they are greyed out.  You can see this if you click on one of them and choose the “options” tab on the right hand side.   If you were to enable this feature you will now have enabled Windows Updates to occur BEFORE applications install.   Have done more than a few I recommend looking into getting as many patches into the system upon install.  But if you have WSUS server local to your install this is not a bad option to enable.  This is off be default to leave HOW you want Windows Updates to apply up to you.

With Windows 7 you may want to enable this to avoid disturbing the application Install.  Once it’s live on the Network, Windows 7 will IMMEDIATELY want to download updates.    However now we’re going to look into editing UNATTEND.XML in order to control this and other features on a finer level.

Click the “OS Info” tab next.  This will give you a very simplistic screen.  We’re concerned with one option “Edit Unattend.XML”

image

Fortunately for the ITPro this will NOT bring up a souped up version of NOTEPAD and force you to learn XML.  Microsoft has provided us with a proper editor to navigate and work with the content it contains in a very sensible fashion including encryption of passwords.   We get THIS to work with Smile

image

Looking here under “Unattend” on the right hand side are the various stages of your Deployment.  From WindowsPE all the way down to oobesystem (Out Of Box Experience, what happens JUST BEFORE  YOU GIVE IT TO THE USER TO BREAK!)

I’ll be honest and I haven’t mastered even half of this but I’ll show you some things I learned and maybe that will help you along. 

The part I’ve with the most is under “Specialize” and “oobeSystem”.   Specialize (from what I can tell you) is various changes you’re making to the O/S from it’s stock configuration.  Like the local Administrator password you’re assigning and the scripts that are running automatically upon each successive reboot of the O/S until of course that part is complete.

The neat part I found out, is that the commands are just DOS commands.  so if you need to disable a service JUST for the install (IE, say Windows Update is stepping on your toes) you simply find out the command in Console to alter the state of a service and add it to the list of “FirstLogonCommands” When you see “Synchronous” that means nothing else can happen until it’s predecessor is complete and the command order is exactly that.   This process works the same way under “Specialize” and “oobeSystem” – Just remember everthing done under “oobeSystem” is your “Out Of Box Experience”, what get’s left behind for the user

image

To add a new Command to the list simply right Click on “FirstLogonCommands” and choose “Insert New Synchronous Command”.  In the provided line you will need to specify the Script or Console command you are running, Give a vague description and specify the order it happens in.  (1,2,3,4,5) – Keep in mind if you want to make this happen before OTHERS you will have to go and edit the “Order number” on the FOLLOWING synchronous commands first.

image

You can, if you so choose edit the default password being assigned to the Local Administrator account in your Deployment.

 

image

Here’s the coolest part.  If you don’t want to show your ID and password for Joining a machine to the Domain under Rules you can edit the UNATTEND.XML and put it right here under “Specialize” under the “x86-Microsoft-Windows-UnattendedJoin-neutral” category.  Under the “Identification” you can specify “JoinDomain” as true then under “Credentials” key in the required credentials

image

You could sit down on an entire weekend and not learn the massive power available to you in UNATTEND.XML but I’m hoping here you can see what it can do and hopefully you become comfortable to really pop open the hood.

Our next and final bit?  We’re going to drop our Images into a WDS (Windows Deployment Services) and get our environment so that we can even use a PXE network boot to install the software.

FacebookTwitterGoogle+Share

MDT 2010–From Zero to Deploy–Part 14

So now we’ve MDT 2010 to a level where we could actually make a seamless install.

No we haven’t.  I lied again.

What we’ve done is bring a lot of automation but there are things that can and should happen even further.

What about Windows Updates?   What about things that can happen WITHIN that installation as it’s installing?  Perhaps you’d like to NOT join to the Domain and leave the password in clear text?

That’s the power contained within your Task Sequence.  Remember when I said it was a “Predefined Template” but you COULD go into it deeper?  We’re about to open the hood.  Let’s pull up the properties of the Task Sequence created before.

image

We’re going to click on “Task Sequence” which is (Are you ready folks?) the “SEQUENCE” your task is going to run in.

Taking a quick look at our Task Sequence it’s really almost a workflow more than code.   Stating what we’re planning on doing.  If you look near the bottom you’ll see two sections marked “Windows Update (Pre-Application Installation)” and “Windows Update (Post-Application Installation)”

image

Presently they are greyed out.  You can see this if you click on one of them and choose the “options” tab on the right hand side.   If you were to enable this feature you will now have enabled Windows Updates to occur BEFORE applications install.   Have done more than a few I recommend looking into getting as many patches into the system upon install.  But if you have WSUS server local to your install this is not a bad option to enable.  This is off be default to leave HOW you want Windows Updates to apply up to you.

With Windows 7 you may want to enable this to avoid disturbing the application Install.  Once it’s live on the Network, Windows 7 will IMMEDIATELY want to download updates.    However now we’re going to look into editing UNATTEND.XML in order to control this and other features on a finer level.

Click the “OS Info” tab next.  This will give you a very simplistic screen.  We’re concerned with one option “Edit Unattend.XML”

image

Fortunately for the ITPro this will NOT bring up a souped up version of NOTEPAD and force you to learn XML.  Microsoft has provided us with a proper editor to navigate and work with the content it contains in a very sensible fashion including encryption of passwords.   We get THIS to work with Smile

image

Looking here under “Unattend” on the right hand side are the various stages of your Deployment.  From WindowsPE all the way down to oobesystem (Out Of Box Experience, what happens JUST BEFORE  YOU GIVE IT TO THE USER TO BREAK!)

I’ll be honest and I haven’t mastered even half of this but I’ll show you some things I learned and maybe that will help you along. 

The part I’ve with the most is under “Specialize” and “oobeSystem”.   Specialize (from what I can tell you) is various changes you’re making to the O/S from it’s stock configuration.  Like the local Administrator password you’re assigning and the scripts that are running automatically upon each successive reboot of the O/S until of course that part is complete.

The neat part I found out, is that the commands are just DOS commands.  so if you need to disable a service JUST for the install (IE, say Windows Update is stepping on your toes) you simply find out the command in Console to alter the state of a service and add it to the list of “FirstLogonCommands” When you see “Synchronous” that means nothing else can happen until it’s predecessor is complete and the command order is exactly that.   This process works the same way under “Specialize” and “oobeSystem” – Just remember everthing done under “oobeSystem” is your “Out Of Box Experience”, what get’s left behind for the user

image

To add a new Command to the list simply right Click on “FirstLogonCommands” and choose “Insert New Synchronous Command”.  In the provided line you will need to specify the Script or Console command you are running, Give a vague description and specify the order it happens in.  (1,2,3,4,5) – Keep in mind if you want to make this happen before OTHERS you will have to go and edit the “Order number” on the FOLLOWING synchronous commands first.

image

You can, if you so choose edit the default password being assigned to the Local Administrator account in your Deployment.

 

image

Here’s the coolest part.  If you don’t want to show your ID and password for Joining a machine to the Domain under Rules you can edit the UNATTEND.XML and put it right here under “Specialize” under the “x86-Microsoft-Windows-UnattendedJoin-neutral” category.  Under the “Identification” you can specify “JoinDomain” as true then under “Credentials” key in the required credentials

image

You could sit down on an entire weekend and not learn the massive power available to you in UNATTEND.XML but I’m hoping here you can see what it can do and hopefully you become comfortable to really pop open the hood.

Our next and final bit?  We’re going to drop our Images into a WDS (Windows Deployment Services) and get our environment so that we can even use a PXE network boot to install the software.

FacebookTwitterGoogle+Share

MDT 2010–From Zero to Deploy–Part 13

At this point we have bootable media, the ability to have an LTI install controlling our workstation deployment.   We’re down to maybe a little typing and a mouse clicks and everything will deploy.

This is a problem.  (*klunk* WHAT?!)

Really it is.   Now that you’ve eliminated MOST of the clicks and you’re constantly choosing your Time Zone and reselecting the same 5 apps each time as WELL as answering the same questions (albeit simple) you will begin to question “Well can’t I automate this more?”

In a word Yes without the caveat of “It Depends”

What MDT 2010 actually does is just lay down a TEMPLATE of vbScript, INI and XML files to automate things as much as possible.   Truth be told, this is fine for most of us.  But if you deploy on even a somewhat regular basis and hate typing as much of the rest of the IT community does, you’ll want to eliminate those few extra clicks left.

So where do you start?  You start in your Task Sequence.  Remember that word…. “SEQUENCE”.  It controls the order in which things are installed but also in what questions are or are not asked, when certain features in Windows are enabled during the install, whether can join a Domain…

The amount of things you can control with a Task Sequence is mind numbing.   Here’s the really cool part.  Just about EVERYTHING that you can do with Systems Center Configuration Manager for deployment (just about!) you can do with MDT and a little programming.

“But Why?!  Why would Microsoft let us do that?  SCCM is the King of Deployment!”

Wrong.   But not for the reason you think.   SCCM is Excellent on Deployment but look at it’s name.  “Configuration Manager” and think of how this product is meant to interact with the Enterprise.  It is MEANT to manage the CONFIGURATION of your Enterprise.   Deployment is about 5% of that.   Configuration is about controlling patches, individualized application deployment, inventory and more.

So letting you have the ability to make a Near ZTI deployment with MDT 2010 does not hurt SCCM.  It’s purpose to be is much larger.  MDT 2010 is a tool to BUILD IMAGES.   SCCM is a tool to BUILD and MANAGE Everything (INCLUDING images) from an Enterprise standpoint.

So let’s take a look at our first challenge.  Skipping some screens.  “SKIP” is the magic word.   

To get rid of our first pile of screens we much “SKIP” them.  Funny thing is if you search MDT 2010 (that big built in documentation search system) for “SKIP” you’ll find exactly what you’re looking for the first time.

image

Clicking on the very FIRST one for “SkipAdminPassword” is going to take you to the heart of it all.    You’ll see it refers to BootStrap.ini and CustomSettings.ini which is where this entry would go (One or the other) including a sample of how it would fit in.    Here’s the catch 22.   Just because you said “SKIP” doesn’t mean it answers the question, it just means “Don’t bother asking and I’ll go with a default answer”

If you need to know which answers to provide and to which questions you click on the link near top of the Help Window saying “Providing Properties for Skipped Windows Deployment Wizard Pages” which will provide you with what I found to be the heart to getting rid of most of my questions.

image

So looking here we can see that if we put in “SkipAdminPassword” if we need to provide the password we must fill in “AdminPassword”

Ok fine, then when does all this go in?

Well THAT is a case of “It Depends”.  It depends on whether you are editing a configuration for your Media (Like the C:\MyMedia folder we created before) when we built an image) or if you’re editing the master settings on the Deployment Share itself.   Editing this is the “Master field” and will also be the spot you need to edit when you are working with WDS (Windows Deployment Services) or doing a manual over the wire install.

Let’s just say, we’re going to work on just our Media share (C:\MyMedia)

For that we go back to the properties of the MyMedia configuration we created under “Media” and click on the “Rules” tab (Remember how I said we’d look at that later?  “Later” is Now.

image

These are the “Rules” that say what happens or Doesn’t happen in this Deployment.   Added your SKIP entry with the appropriate variable will now SKIP that screen in your LTI and have the answer prefilled.  For the “SkipAdminPassword” we would add in these two lines

SkipAdminPassword=YES

AdminPassword=SomePasswordIJustTypedInAndExposedToTheWorldOhCrapThereGoesMyNewSecurePassword

I would not recommend using that password of course, but that would set the Local Administrator password AUTOMATICALLY on all of your Deployments to everything after “AdminPassword=”

This is just one option.  The one I REALLY wanted was the ability to “Skip” the application screen since I would check the same 8 or nine applications each time.  Skipping this is easy but you need to know how to specify the Applications.

I found the line was “SkipApplications” which was sensible enough but how do you SPECIFY the applications? It turns out it was easier than I thought.

For each and every Application, Bundle and even package there is a GUID you can reference.   You may have overlooked it (I certainly did my first couple of times)

So looking up in Applications, let’s pull up the Properties for our “Adobe Flash Player 10”

 

image

In order to get this Application to install you simply need to key in to the CustomSettings.ini file (Your Rules)

SkipApplications=YES< /strong>

Applications001={c7fe0f41-0240-48df-912f-6646f710e286}

If I had a series of applications to have installed I would just mark down something like this

SkipApplications=YES

Applications001={c7fe0f41-0240-48df-912f-6646f710e286}
Applications002={d22c1a92-8cee-4a6a-9045-9778a46e613e}
Applications003={fc5c78ce-4966-48de-9d52-b54c586900f3}

As well, the order they will attempt to install will be the order you list them in.   But remember this (Good thing).  All those dependencies you programmed in are going to be called up here.

If you want to have the Media automatically choose which Task sequence to default to you can enter in a

SkipTaskSequence=YES

But how do you know how to choose the task sequence.   Do you remember how we entered a “Task Sequence ID” ?  This is where that ID get’s used

image

So within our CustomSettings.ini (Rules) we would enter a

SkipTaskSequence=YES

TaskSequenceID=WIN7ENT1

So if were to add in these entries to our Rules it would all look like this

image

Now would you like me to make your life REALLY easy?  Here is a sample set of Rules from a Deployment I created that would install the applications, Join the Domain and not ask ANYTHING except prompt me with the initial “Welcome Screen”.  Just read the various Skip statements and see if You can figure out what I’ve done here.  The nice thing is the variables are very sensible.  The ComputerName one is call since it takes the SerialNumber from the BIOS and gives the computer that as a default name.  For that I must personally express heartfelt thanks to Mitch Garvis for that one.  I was butting my head against a wall for 24 hours on that one!

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipApplications=YES
Applications001={b3d58913-7175-446b-92d8-359be635073f}
Applications002={d22c1a92-8cee-4a6a-9045-9778a46e613e}
Applications003={fc5c78ce-4966-48de-9d52-b54c586900f3}
Applications004={89532c30-72b0-4fb1-9c6a-8e605d098825}
SkipComputerName=YES
SkipDomainMembership=YES
JoinDomain=CONTOSO.LOCAL
DomainAdmin=CONTOSODOMAINADMIN
DomainAdminDomain=CONTOSO.LOCAL
DomainAdminPassword=ContosoPasswordOhNoIJustShowedTHATtoTheWorld
SkipLocaleSelection=YES
SkipFinalSummary=NO
SkipSummary=YES
SkipPackageDisplay=YES
SkipTaskSequence=YES
TaskSequenceID=WIN7ENT1
SkipTimeZone=YES
TimeZoneName=Eastern Standard Time
SkipBitlocker=YES
SkipProductKey=YES
SkipComputerBackup=YES
OSDComputerName=%SERIALNUMBER%
SkipUserData=YES
SkipCapture=YES

But you’re not satisfied?  You want MORE? You want to skip the Welcome screen too?

The welcome screen is a part of the Windows PE boot and you must edit the Bootstrap.ini file for that.  On the same Rules tab, click on “Edit Bootstrap.ini” and add this line on the end

SkipBDDWelcome=YES

With these settings you can now have a Boot that won’t bug you with any silly questions and do all the dirty work for you.

Next time around?  We’ll open up the hood a bit and take a quick look at editing the UNATTEND.XML with the built in Editor in MDT 2010

FacebookTwitterGoogle+Share