MDT 2010: How to change WinPE drivers?

We have boot images that currently work for all of our systems and is used for PXE booting with a WDS server, but I think we have lots of extra drivers in the PE image because the boot image size is quite large and it seems to spend a long time injecting
drivers during the PE portion before the OS is installed.
Which drivers other than than NIC drivers are needed in the boot image?
How can we change the boot image so that it has only the minimum necessary drivers for each computer model?

Network and storage controller drivers are the essential ones and that is included by default in the boot image. However there are certain types of these drivers you do not want/need in the boot image and that is drivers for wireless network cards and for
instance all kinds of memory card reader drivers.
One of way of gaining full control over the drivers in the boot image is to create a WinPE structure in the driver part of Deployment Workbench and then use Selection profiles (see the settings on the deployment share) to make sure that only the drivers
from the selection profile is added to the WinPE/Boot image.
Blogging about Windows for IT pros at
www.theexperienceblog.com

Similar Messages

MDT 2010 - USB 3.0 issue after OS Install and Inject Drivers steps

Hello,
I'm using MDT 2010 and I'm booting and image PCs from a USB drive. On some newer systems (eg: Latitude El530) I have issues when I use the USB 3 ports (if media is connected to USB 2 port, everuthing is fine). The systes recognizes the USB stick and I can
start the Task Sequence just fine. I pass the Install OS step and Inject Drivers step, but after the first reboot, I get the prompt to insert the media to continue the deployment. This happens only if the stick is connected to the USB 3.0 ports. If I
check Device Manager, I see the USB device withouth driver. The drivers are already on the USB stick...I puled them from FileRepository from an updated system with all the drivers. Is anyone else having similar issues? I see other people have USB 3 issues,
but mostlly to start the deployment from it, or at partitioning...I don't have that issue. My issue starts after the OS is installed.
Any sugestion is appreciated...Thank you...
aburica

You should be able to do this. nVidia Optimus video drivers have the same issue. How we solved this
We create selection profiles for each make and model
We inject every single driver in profile for each make and model
The Optimus driver then gets installed because it is local to the machine already.
Why it didn't work before is the child device never gets detected during the PNP enum that happens when you have 'Install only matching drivers from the selection profile' so never ends up in the local driver store.
P.S. We ONLY have the drivers that install imported into each make model folder.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
How to ask a question that is fixable.

How to change the default left alignment setting in Word 2010 professional (personal use)

Hi, I use Word 2010 Professional for my personal use at home, and somehow the default setting for the left alignment in a new Word document has been changed to a hanging indent at .25. So every time I open a new Word document, the left margin
has an indent setting. I have to change it to 0.0 every time, which is annoying.
I've tried to go into the "Options" section, under "Custom Settings" to de-select an auto left margin indentation, but I can't seem to find an option to do that. Can anyone please tell me how to change this setting in the master Word 2010 template,
so that every time I open a new doc, the left side is aligned at the 1" margin with no hanging indent?
Thank you.

Page Layout-Page Setup-Margins-Custom Margins...-change your setting-Set As DefaultStay Hungry, Stay Foolish

How to change the look and feel for Heading of quick launch menu in project server 2010

Hi
can someone tell me how to change the look and feel of Header names in quick launch.
I want the header to be displayed in Bold with Underline to it.
could this be possible for just header in quick launch in project server 2010.

Hi Rohan
It does not work this way. You have to use a content editor webpart.
See references below that might help you starting with this customisation:
Http://go4answers.webhost4life.com/Example/sharepoint-2010-quick-launch-look-feel-78379.aspx
Http://m.sharepointpromag.com/sharepoint/four-ways-add-or-remove-quick-launch-menu-control
Hope this helps.
Guillaume Rouyre - MBA, MCP, MCTS

How can i using MDT 2010 to deploy multiple partitions Windows 7 image?

Hello,
I am planning using MDT as a deploy windows 7 solutions. My Windows 7 is setup on parition 1 "C:" and users profile on parition 2 "D". I am already capture WIM for each paritions. How can i using MDT 2010 to deploy multiple partitions for Windows 7
image? together
Thanks

Having the users folder on a separate partitions is a bad idea because the Windows Setup was not really designed for it, it's more of a afterfix. In addition to that the deployment solutions in general have problem dealing with multiple partions.
Put it this way - The big warning text in the WAIK documentation about redirecting the users folder to another drive is there for a reason. It will break future offline servicing.
It doesn't mean it can't be done, it just means it will take you three times (at least) longer to setup/troubleshoot your deployment solution, and you will be in a world of pain the next time you want to re-image the machine.
This quote from a good friend of mine (Andreas Hammarskjold) describes it very well:
Generally I would always recommend to only have ONE partition these days. Going down the route of making multiple partitions is like having multiple wives/girlfriends/lovers… it’s all fun and games for a while but ends with disaster
- Andreas H.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Mac Book Pro 2010- how do I change MPG files on desktop to use on I Movie

I have a MacBook Pro 2010 - how do I change MPG files on desktop to use in IMovie

Transfer the movie from your iPad to your MacBook then. =)
iOS: How to transfer or sync content to your computer
http://support.apple.com/kb/HT1296

How to change format of OOB columns in sharepoint 2010?

Hi,
I have an requirement of changing of date format from 12/05/2014 to 12 May 2014 in a list for 2 Out of Box columns: Created , Modified. Can some one please help me on this.
Please find the screenshot in which columns are highlighted:
Badri

Hi,
Please check below:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/ade1b4a2-7eac-479a-9dde-baa66eb18e36/how-to-change-date-format-of-sharepoint-list
http://www.sharepointusecases.com/2009/01/customizing-datetime-format-on-a-list-view-web-part/
Hope it helps!
Thanks,
Avni Bhatt

MDT 2010 hangs on uefi equipped machines

Hi all,
I'm new to MDT (Started playing with the betas earlier this year), but I've been using WDS for nearly a year or so. I have an MDT 2010 server running on a Windows 2003 box with all of the latest service packs, fix packs, etc. The MDT server has been configured to deploy our install images to our test lab (We run everything from 2003 R2 up to 2008 R2). So far the MDT server (I upgraded the betas to the RTM code) has been running great on almost all of our machines, with the exception of our uEFI based machines.
We are primarily an IBM lab (We have a smattering of Dell and HP boxes, but none yet that have a uEFI Bios). We have mostly xSeries and BladeCenter products.
Our scenario:
We're running MDT 2010 in an LTI setup. No database, we just want the end user to be able to PXE boot the box, boot the Lite Touch 32 or 64 bit wim and then get the MDT screen that allows them to pick what operating system they want installed. Let the install start in the WinPE mode and then the WinPE mode reboots and continues on its installation path (DOS boot mode for the 2003 R2 installs , 2008 GUI setup, etc)
That part works fine for all of our regular xSeries (ie non uEFI) blades and servers. The user picks their OS, the preinstall phase starts, finishes and reboots out of the WinPE shell and then continues on with its next phase of the install.
Our uEFI enabled boxes (Mostly IBM HS22, x3200 M3, x3250 M3) boot into the MDT selection screen just fine. We can choose our os and the install starts in the PE phase (Sorry if I'm messing up the phase names still learning MDT as I go). Once the WinPE phase finshes, instead of rebooting (like the non uEFI boxes do) these boxes automatically open a Command Prompt window and then sit there until you close the window or type exit. I have not opened the command prompt (I know you can hit F8, but this is being done by MDT on its own). Once you manually close this window, the install continues just like it should.
I've updated alll firmware levels on these boxes to see if it might be something going on there, but no luck. MDT 2010 continues to hang (opens the command prompt) after completing the WinPE portion of the installation.
Has anybody else out there seen this behaviour? Anyone have any ideas how to correct it?
Thanks,
Jim Kosek

Hi there,
This is the original poster.
I had meant to list out our steps to correct this issue earlier this week, but this is the first chance I got to update this. Hate being the only one in on a holiday week :(
Like Keith stated above this is caused by the NETIMM.INF driver. Thanks to Keith's guidance in parsing through the log files (Especially since I had no idea where most of them were hiding) we were able to see that the NETIMM.INF driver would try and load during the Windows PE Setup phase. This driver does not appear to load correctly in Windows PE (I've been trying to get it to load into a different PE image for the better part of a year for other reasons). When this driver gets loaded during the PE phase, the installer would see that the driver did not load correctly. The installer would pop open a command prompt window to allow you to debug what went wrong. Since this driver isn't really needed for the installation, you could exit the command prompt window and your install would continue along just like it should.
If you look at your wpeinint.log file you should see something like this:
Info      Installing device usb\vid_04b3&pid_4010 X:\WINDOWS\INF\netimm.inf failed with status 0xe0000219
Info      Spent 19095ms installing network drivers
Info      STATUS: FAILURE (0xe0000219)
Warning   Applying WinPE unattend settings failed with status 0xe0000219; ignoring shutdown settings
This is what hangs the box.
When Keith first pointed me to the driver being the problem, I just removed the driver from my Out-Of-Box-Drivers and still had the issue. The NETIMM.INF file is part of the base install media so it shows up anyway. I then did just what you did by disabling the Commands on the USB Interface. This basically stops that device from being available during the install, so no device, no driver and MDT is happy and reboots like it should.
The problem I have with that solution is that all of the OS Firmware update disks from IBM want to try and communicate through that USB device when you go to update anything on that machine (uEFI code, Diagnostics, ASU, etc). So if that device is not there, then you cannot use any of the on-line flash utilities to update your machine. Not sure how many machines you have (or how often you upgrade the Firmware on them), but that might come back to bite you later. Plus you also have to remember to disable that on all of your IMM equipped machines BIOS's. And then when a user resets the Bios back to defaults that USB device gets turned back on again and you start getting calls that the deployments are hanging. I'm in a test lab and we get new machines brought to us all of the time. I may not be the one to set it up and then I have to rely on somebody remembering to change a setting in Bios. I'd rather just change it globally from my end and then I know its fixed. But to each their own.
I did like Keith suggested and edited the WIM files. I simply renamed the NETIMM.INF to NETIMM.OLD and closed the WIMs back up. I too was worried about having to change the WIM files repeatedly. I'm the one that built out our MDT server. My co-workers know enough to rebuild the deployment share if need be, but they don't use MDT enough to know about mounting WIMs and changing files and such. What I did was I changed these on our base install media. In my case, MDT picked Windows 7 to build out the 32 Bit LiteTouch.wim and 2008R2 for the 64 bit LiteTouch.wim file. Once I changed these on the original disks, all of my LiteTouch rebuilds have kept this change intact. Now if I ever change these original disks and have to completely rebuild the WIM files, I'm sure I'll forget to make that change. However I'd rather deal with that then (My end users will let me know if the installs start hanging again) instead of having to remember to change each machine's bios settings.
Now since the NETIMM.INF driver is no longer on the install media, I need some way to add that driver during the installation and not during the PE phase. What I did was to add the NETIMM.INF file into my Out-of-Box Drivers section. I then created a new selection profile called LiteTouch. I added all of my necessary drivers, with the exception of the NETIMM.INF driver, into that new LiteTouch selection group and I changed my LiteTouch Components to only load from the LiteTouch Selection group during the PE phase. I then call my All Drivers group during the installation of the Operating Systems. That way I do not get the driver during PE, but I get the driver installed during setup and I can then talk to the IMM for updates and such.
My way might not be the best way for everyone else, but it does what I need it to do.
I would like to take a minute though and thank Keith again for all of his help in troubleshooting this problem. We have a lot of remote users and this was causing them some grief because they would start a deployment and expect it to be done when they came back later. On the IMM equipped machines, they would be staring at a command prompt screen and have no idea what went wrong. I would then get calls stating that the install failed. Without Keith's help I'd still be getting those calls from our users.
Jim Kosek

MDT 2013, D: Wim not applying after update from MDT 2010 to 2013

Updated MDT from MDT 2010 Update 1 to MDT 2012 Update 1, uninstalled WAIK, Installed MDT 2013, and then ADK, Upgraded all Deployment shares along the way, and now the extra drive (D:) Wim will not apply to Drive, i have tried two different ways to handle
the said action, the first was using the Unattend.xml, adding the DataImage Action, the other was using an Imagex command from the MDT task sequence. neither is applying the Wim, before the upgrade this worked. has any one else had this issue?
Thank you,
Dane Zittritsch
Thinix Support Manager

I moved from MDT 2010 to MDT 2013 and its just not working, i have tried a few different methods, the old way we used the
Unattend.xml and placed a install order and that always worked, but now i am trying to use Imagex and its not applying the wim, when i get in the image the D:\ (Second Drive) is missing files. Now here is the weird part, if i re-run the task sequence
the D WIM is applied, but that's counter productive. i will apply my TS.xml information.
Ts.xml
<?xml version="1.0"?>
-<sequence description="A complete task sequence for deploying a client operating system" name="Standard Client Task Sequence" version="3.00"> -<globalVarList> <variable name="OSGUID" property="OSGUID">{52bb4035-96e5-46f3-9d17-3d2a363895c3}</variable>
<variable name="DestinationDisk" property="DestinationDisk">0</variable>
<variable name="DestinationPartition" property="DestinationPartition">2</variable>
<variable name="DestinationOSVariable" property="DestinationOSVariable">OSDisk</variable>
<variable name="DestinationOSRefresh" property="DestinationOSRefresh"/>
<variable name="DestinationOSDriveLetter" property="DestinationOSDriveLetter"/>
<variable name="DestinationOSInstallType" property="DestinationOSInstallType">ByDiskPartition</variable>
</globalVarList>
-<group description="Initialize the TS environment" name="Initialization" expand="true" continueOnError="false" disable="false">
- <step description="" name="Gather local only" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="BDD_Gather"> -<defaultVarList> <variable name="GatherLocalOnly"
property="GatherLocalOnly">true</variable> <variable name="RulesFile" property="RulesFile"/> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIGather.wsf"</action> </step> </group> -<group description="Test"
name="Validation" expand="true" continueOnError="false" disable="false"> -<condition> -<operator type="or"> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">PHASE</variable> <variable
name="Operator">equals</variable> <variable name="Value">VALIDATION</variable> </expression> </operator> </condition> -<step description="" name="Validate" continueOnError="false" disable="false" startIn="" successCodeList="0
3010" type="BDD_Validate"> -<defaultVarList> <variable name="ImageSize" property="ImageSize">0</variable> <variable name="ImageProcessorSpeed" property="ImageProcessorSpeed">800</variable> <variable name="ImageMemory" property="ImageMemory">768</variable>
<variable name="VerifyOS" property="VerifyOS">CLIENT</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIValidate.wsf"</action> </step> -<step description="" name="Check BIOS" continueOnError="false" disable="false"
startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIBIOSCheck.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step>
-<step description="" name="Next Phase" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
<variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
</defaultVarList> </step> </group> -<group description="" name="State Capture" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable
name="Variable">PHASE</variable> <variable name="Operator">equals</variable> <variable name="Value">STATECAPTURE</variable> </expression> </condition> -<step description="" name="Next Phase" continueOnError="false"
disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step>
</group> -<group description="" name="Preinstall" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">PHASE</variable>
<variable name="Operator">equals</variable> <variable name="Value">PREINSTALL</variable> </expression> </condition> -<step description="" name="Gather local only" continueOnError="false" disable="false" startIn="" successCodeList="0
3010" type="BDD_Gather"> -<defaultVarList> <variable name="GatherLocalOnly" property="GatherLocalOnly">true</variable> <variable name="RulesFile" property="RulesFile"/> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIGather.wsf"</action>
</step> -<group description="" name="New Computer only" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">DeploymentType</variable>
<variable name="Operator">equals</variable> <variable name="Value">NEWCOMPUTER</variable> </expression> </condition> -<step description="" name="Validate" continueOnError="false" disable="false" startIn="" successCodeList="0
3010" type="BDD_Validate"> -<defaultVarList> <variable name="ImageSize" property="ImageSize">0</variable> <variable name="ImageProcessorSpeed" property="ImageProcessorSpeed">800</variable> <variable name="ImageMemory" property="ImageMemory">768</variable>
<variable name="VerifyOS" property="VerifyOS">CLIENT</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIValidate.wsf"</action> </step> -<step description="" name="Format and Partition Disk" continueOnError="false"
disable="true" successCodeList="0 3010" type="SMS_TaskSequence_PartitionDiskAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="OSDDiskIndex" property="DiskIndex">0</variable> <variable name="DONotCreateExtraPartition"
property="DONotCreateExtraPartition"/> <variable name="OSDPartitions0Type" property="Partitions0Type">Primary</variable> <variable name="OSDPartitions0FileSystem" property="Partitions0FileSystem">NTFS</variable> <variable name="OSDPartitions0Bootable"
property="Partitions0Bootable">True</variable> <variable name="OSDPartitions0QuickFormat" property="Partitions0QuickFormat">True</variable> <variable name="OSDPartitions0VolumeName" property="Partitions0VolumeName">OSDisk</variable>
<variable name="OSDPartitions0Size" property="Partitions0Size">100</variable> <variable name="OSDPartitions0SizeUnits" property="Partitions0SizeUnits">%</variable> <variable name="OSDPartitions0VolumeLetterVariable" property="Partitions0VolumeLetterVariable">OSDisk</variable>
<variable name="OSDPartitions" property="Partitions">1</variable> <variable name="OSDPartitionStyle" property="PartitionStyle">MBR</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIDiskpart.wsf"</action>
</step> -<step description="You can change the size of the partition(s) in the \Scripts\WinRE\DiskConfig.txt file. Make sure your partition is large enough to hold the recovery image if you install alot of software. Current configuration is 160GB
for recovery, 60 for OS, 10 for scratch" name="Format and Partition Disk [Custom]" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable
name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010 BETA\Configure-HDD.cmd"</action> </step> -<step
description="" name="Copy scripts" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\LTICopyScripts.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
<variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
</defaultVarList> </step> </group> -<step description="" name="Configure" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIConfigure.wsf"</action> -<defaultVarList>
<variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
<variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Inject Drivers" continueOnError="false" disable="false" successCodeList="0 3010" type="BDD_InjectDrivers"
runIn="WinPEandFullOS"> -<defaultVarList> <variable name="DriverSelectionProfile" property="DriverSelectionProfile">Dell OptiPlex 790</variable> <variable name="DriverInjectionMode" property="DriverInjectionMode">ALL</variable>
</defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIDrivers.wsf"</action> </step> -<step description="" name="Apply Patches" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="BDD_InstallUpdatesOffline">
<action>cscript.exe "%SCRIPTROOT%\ZTIPatches.wsf"</action> -<defaultVarList> <variable name="PackageSelectionProfile" property="PackageSelectionProfile">All Packages</variable> </defaultVarList> </step> -<step description=""
name="Next Phase" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
<variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
</defaultVarList> </step> </group> -<group description="" name="Install" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable
name="Variable">PHASE</variable> <variable name="Operator">equals</variable> <variable name="Value">INSTALL</variable> </expression> </condition> -<step description="" name="[Custom] Apply D Wim " continueOnError="false"
disable="true" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable>
<variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
</defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\DWim.exe"</action> </step> -<step description="" name="Install Operating System" continueOnError="false" disable="false" successCodeList="0 3010" type="BDD_InstallOS" runIn="WinPEandFullOS">
-<defaultVarList> <variable name="OSGUID" property="OSGUID">{52bb4035-96e5-46f3-9d17-3d2a363895c3}</variable> <variable name="DestinationDisk" property="DestinationDisk">0</variable> <variable name="DestinationPartition" property="DestinationPartition">2</variable>
<variable name="DestinationOSDriveLetter" property="DestinationOSDriveLetter"/> <variable name="DestinationOSVariable" property="DestinationOSVariable">OSDisk</variable> <variable name="DestinationOSRefresh" property="DestinationOSRefresh"/>
<variable name="DestinationOSInstallType" property="DestinationOSInstallType">ByDiskPartition</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\LTIApply.wsf"</action> </step> -<step description="" name="Restart
computer" continueOnError="false" disable="false" successCodeList="0 3010" type="SMS_TaskSequence_RebootAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="SMSRebootMessage" property="Message"/> <variable name="SMSRebootTimeout"
property="MessageTimeout">60</variable> <variable name="SMSRebootTarget" property="Target"/> </defaultVarList> <action>smsboot.exe /target:WinPE</action> </step> -<step description="" name="Next Phase" continueOnError="false"
disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step>
</group> -<group description="" name="Postinstall" expand="true" continueOnError="false" disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">PHASE</variable>
<variable name="Operator">equals</variable> <variable name="Value">POSTINSTALL</variable> </expression> </condition> -<step description="" name="Copy Scripts" continueOnError="false" disable="true" startIn="" successCodeList="0
3010"> <action>cscript.exe "%SCRIPTROOT%\LTICopyScripts.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/>
<variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Configure"
continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIConfigure.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable
name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
</defaultVarList> </step> -<step description="Applies the D: wim to System " name="Apply Scratch Drive" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS">
-<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable
name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"\\thinix-dev1\navyImage$\Tools\x86\imagex.exe" /apply
"\\thinix-dev1\navyImage$\Operating Systems\navycnic-gen_20131226100000\navycnic-gen_20131226100000_ddrive.wim" 1 D:\</action> </step> -<step description="" name="Inject Drivers" continueOnError="false" disable="false" startIn="" successCodeList="0
3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIdrivers.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/>
<variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<group description="" name="Custom
Tasks" expand="true" continueOnError="false" disable="false"> -<step description="Makes sure there is no Boot Config files on C drive and changes them to R drive:" name="Recovery Partition" continueOnError="false" disable="false" startIn="" successCodeList="0
3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\Re-assign
DriveLetter.cmd"</action> </step> -<step description="" name="[Custom] Apply D Wim " continueOnError="false" disable="true" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList>
<variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\DWim.exe"</action> </step> -<step description=""
name="[Custom] TDRBCD" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable
name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
<variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\TDRBCD.exe"</action> </step> -<step description="" name="[Custom] Apply D Wim " continueOnError="false"
disable="true" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_RunCommandLineAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="PackageID" property="PackageID"/> <variable name="RunAsUser" property="RunAsUser">false</variable>
<variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
</defaultVarList> <action>"%SCRIPTROOT%\Dell_Optiplex_7010\DWim.exe"</action> </step> </group> -<step description="" name="Next Phase" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe
"%SCRIPTROOT%\ZTINextPhase.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Set Phase" continueOnError="false" disable="false" successCodeList="0
3010" type="SMS_TaskSequence_SetVariableAction"> -<defaultVarList> <variable name="VariableName" property="VariableName">PHASE</variable> <variable name="VariableValue" property="VariableValue">STATERESTORE</variable> </defaultVarList>
<action>cscript.exe "%SCRIPTROOT%\ZTISetVariable.wsf"</action> </step> </group> -<group description="" name="State Restore" expand="false" continueOnError="false" disable="true"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression">
<variable name="Variable">PHASE</variable> <variable name="Operator">equals</variable> <variable name="Value">STATERESTORE</variable> </expression> </condition> -<step description="" name="Gather local only"
continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="BDD_Gather"> -<defaultVarList> <variable name="GatherLocalOnly" property="GatherLocalOnly">true</variable> <variable name="RulesFile" property="RulesFile"/>
</defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIGather.wsf"</action> </step> -<step description="" name="Post-Apply Cleanup" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe
"%SCRIPTROOT%\LTIApply.wsf" /post</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Recover From Domain " continueOnError="false" disable="false"
successCodeList="0 3010" type="BDD_RecoverDomainJoin" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="DomainErrorRecovery" property="DomainErrorRecovery">Auto</variable> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIDomainJoin.wsf"
</action> </step> -<step description="" name="Tattoo" continueOnError="true" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTITatoo.wsf"</action> -<defaultVarList> <variable name="RunAsUser"
property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile"
property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Opt In to CEIP and WER" continueOnError="true" disable="true" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIOptIn.wsf"
/CEIP:YES /WER:YES</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Windows Update (Pre-Application Installation)" continueOnError="true"
disable="true" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIWindowsUpdate.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName"
property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step>
-<step description="" name="Install Applications" continueOnError="false" disable="false" startIn="" successCodeList="0 3010" type="BDD_InstallApplication"> <action>cscript.exe "%SCRIPTROOT%\ZTIApplications.wsf"</action> -<defaultVarList>
<variable name="ApplicationGUID" property="ApplicationGUID"/> <variable name="ApplicationSuccessCodes" property="ApplicationSuccessCodes">0 3010</variable> </defaultVarList> </step> -<step description="" name="Windows Update
(Post-Application Installation)" continueOnError="true" disable="true" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIWindowsUpdate.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
<variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
</defaultVarList> </step> <group description="" name="Custom Tasks" expand="true" continueOnError="false" disable="false"/> -<step description="" name="Enable BitLocker" continueOnError="true" startIn="" successCodeList="0 3010" type="SMS_TaskSequence_EnableBitLockerAction">
<action>cscript.exe "%SCRIPTROOT%\ZTIBde.wsf"</action> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">BdeInstallSuppress</variable> <variable name="Operator">notEquals</variable>
<variable name="Value">YES</variable> </expression> </condition> -<defaultVarList> <variable name="OSDBitLockerTargetDrive" property="BdeTargetDriveLetter"/> <variable name="OSDBitLockerMode" property="BdeInstall">TPM</variable>
<variable name="OSDBitLockerStartupKeyDrive" property="BdeKeyLocation"/> <variable name="OSDBitLockerCreateRecoveryPassword" property="BdeRecoveryPassword">AD</variable> <variable name="OSDBitLockerWaitForEncryption" property="WaitForEncryption">false</variable>
</defaultVarList> </step> -<step description="" name="Restore User State" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIUserState.wsf" /restore</action> -<defaultVarList>
<variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
<variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Restore Groups" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe
"%SCRIPTROOT%\ZTIGroups.wsf" /restore</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable
name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Apply Local GPO Package"
continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIApplyGPOPack.wsf"</action> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable
name="Variable">ApplyGPOPack</variable> <variable name="Operator">notEquals</variable> <variable name="Value">NO</variable> </expression> </condition> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
<variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
</defaultVarList> </step> -<group description="" name="Imaging" expand="false" continueOnError="false" disable="false"> <action/> -<group description="" name="Prepare Only" expand="false" continueOnError="false" disable="false">
-<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">DoCapture</variable> <variable name="Operator">equals</variable> <variable name="Value">PREPARE</variable>
</expression> </condition> -<step description="" name="Copy Sysprep files" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\LTISysprep.wsf"</action> -<defaultVarList>
<variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
<variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> </group> -<group description="" name="Sysprep Only" expand="false" continueOnError="false" disable="false"> -<condition>
-<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">DoCapture</variable> <variable name="Operator">equals</variable> <variable name="Value">SYSPREP</variable> </expression>
</condition> -<step description="" name="Add mass storage drivers to sysprep.inf for XP and 2003" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIDrivers.wsf"</action>
-<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
<variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Execute Sysprep" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe
"%SCRIPTROOT%\LTISysprep.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> </group> -<group description="" name="Capture Image" expand="false" continueOnError="false"
disable="false"> -<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">DoCapture</variable> <variable name="Operator">equals</variable> <variable name="Value">YES</variable>
</expression> </condition> -<step description="" name="Apply Windows PE" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE /STAGE</action> -<defaultVarList>
<variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/>
<variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Add mass storage drivers to sysprep.inf for XP and 2003" continueOnError="false" disable="false" startIn=""
successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIDrivers.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/>
<variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Execute
Sysprep" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\LTISysprep.wsf"</action> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable>
<variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable>
</defaultVarList> </step> -<step description="" name="Apply Windows PE (BCD)" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%_SMSTSMDataPath%\Scripts\LTIApply.wsf" /PE /BCD</action>
-<condition> -<expression type="SMS_TaskSequence_VariableConditionExpression"> <variable name="Variable">ImageBuild</variable> <variable name="Operator">greaterEqual</variable> <variable name="Value">6</variable>
</expression> </condition> -<defaultVarList> <variable name="RunAsUser" property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword"
property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile" property="LoadProfile">false</variable> </defaultVarList> </step> -<step description="" name="Restart computer" continueOnError="false" disable="false"
successCodeList="0 3010" type="SMS_TaskSequence_RebootAction" runIn="WinPEandFullOS"> -<defaultVarList> <variable name="Message" property="Message"/> <variable name="MessageTimeout" property="MessageTimeout">60</variable> <variable
name="Target" property="Target"/> </defaultVarList> <action>smsboot.exe /target:WinPE</action> </step> -<step description="" name="Gather local only" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"
type="BDD_Gather"> -<defaultVarList> <variable name="GatherLocalOnly" property="GatherLocalOnly">true</variable> <variable name="RulesFile" property="RulesFile"/> </defaultVarList> <action>cscript.exe "%SCRIPTROOT%\ZTIGather.wsf"</action>
</step> -<step description="" name="Create WIM" continueOnError="false" disable="false" startIn="" successCodeList="0 3010"> <action>cscript.exe "%SCRIPTROOT%\ZTIBackup.wsf"</action> -<defaultVarList> <variable name="RunAsUser"
property="RunAsUser">false</variable> <variable name="SMSTSRunCommandLineUserName" property="SMSTSRunCommandLineUserName"/> <variable name="SMSTSRunCommandLineUserPassword" property="SMSTSRunCommandLineUserPassword"/> <variable name="LoadProfile"
property="LoadProfile">false</variable> </defaultVarList> </step> </group> </group> </group> </sequence>

How to change the path of sysprep files that were copied to reference computer when i capture the image from reference.

Dears ,,
how to change the path that sysprep were copied to reference computer when i capture the image from reference.
Should i modify some codes in LTIAPPLY.wsf? how to modify it?
Thanks.

Sysprep and capture has *Three* steps.
1. Run sysprep on the local machine (easy).
2. Copy WinPE down to the local machine so we can reboot into winpe for capture.
3. Capture the drive in an *offline* state from within WinPE.
What is most likely happening is that you are having problems with step #2. 100MB is *WAY* too small to copy down WinPE. By default MDT will make this System partition much bigger, 499MB. IF you install Windows 7 from the default media. IT will only create
a 100MB partition.
By default MDT 2012 Update 1 and greater *should* recover to a fallback drive with the OS on it, however if you are running older versions that might not happen correctly.
If you are still having problems, copy your BDD.log file to a public share like OneDrive and copy the link here.
Keith Garner - keithga.wordpress.com

MDT and Macs running Bootcamp – worked in MDT 2010, now does not in MDT 2012

I haven’t been able to find much info on this so I thought I would try here and see if anyone can help.
We’ve been using MDT 2010 for the last couple of years to install Windows 7 on Macintosh’s running Bootcamp and it’s been working fine.
We recently upgraded to MDT 2012 and the same process we used to use for this does not work anymore and I would like to find out how to make it work on 2012.
Here’s how the process works:
First, setup Bootcamp on the Mac. This creates another partition on the Mac for the Windows OS (partition 3 for MAC OS 10.6 and lower, partition 4 for OS 10.7 Lion because of the recovery partition).
Unfortunately Bootcamp cannot create NTFS partitions so it formats it as FAT32.
We then create a standard client task sequence using MDT and the Windows 7 source files (not a custom image) and give it a name to make it obvious it’s for Mac’s – “Windows 7 for Macintosh running Bootcamp”.
We edit that task sequence and disable the built in “Format and Partition Disk” step since we don’t need to create the partition, only format it as NTFS.
We then create a custom diskpart.txt file called BootCamp_Lion.txt with the following contents:
SELECT DISK 0
SELECT PARTITION 4
FORMAT FS=NTFS QUICK OVERRIDE
We place this file in the “Extra directory to add” location we’ve specified in the Win PE Customization section so it is located on the root of X:\ when it boots into Win PE.
We then add a command line to the task sequence: diskpart.exe /s x:\BootCamp_Lion.txt
to format the existing bootcamp partition as NTFS. Then in the “Install Operating System” step we set it to apply to a specific disk and partition – Disk 0, Partition 4.
This installs Windows 7 on the Bootcamp partition and leaves the Mac OS intact and has been working fine in MDT 2010.
Now with MDT 2012, the task sequence starts fine, formats the partition, installs Win 7, but when it comes up in the full OS for the first time I get the error “Unable to find the SMS Task Sequencer.
The deployment will not proceed.” And the task sequence stops.
I know the partitioning part has changed in 2012 and have read that you can get this error if you deploy to something other than disk 0, partition 1 but I’m wondering if I can accomplish the same thing that I used to have working in 2012.
Is there a different way I can do this? Any help would be appreciated.
Thanks,
Robb

Hi Guys
I have been having the same problem.
What I have done to get around it is
add a custom command as we all did in MDT 2010 to format partition 3 or 4 depending on the version of OSX
don’t disable the Format and Partition Disk task but tick in create active partition then remove the partition properties and then click on options and check
continue on error
then under install operating system change the partition that you want to have windows installed on
Once the deployment has completed you will receive the message that deployment has completed but with one error
Hope this helps
Regards
Matthew

WDS Multicasting MDT 2010 created SOE

I'm just wondering if the following scenario is possible with the setup we currently have. The architecture we've implemented is:
MDT 2010 on Win2008 R2. No clients build from this server.
Windows 2008 R2 servers with the WDS Transport Server role only. We have no AD in the environment, so this is what I'm limited to. Clients connect via PXE to these servers to image, using a WinPE LTI.
Multicast has been setup and configured, and it working successfully for the base OS .wim file only. Once the client moves further into the task sequence and begins installing additional applications, their traffic falls back to Unicast.
Is it possible to maintain multicast throughout the entire imaging process given this environment and its limitations?

Interesting setup. I think the answer is no. My thought process is:
- Boot LiteTouch wim via PXE - unicast for multiple machines
- multiple machines establish a session from which the deployment server starts sending out the blocks for the install.wim via multicast to clients at the same time.
- task sequence starts up at different times for the clients for first boot\OOBE and complete final tasks via unicast.
Once the install.wim is deployed, that piece is complete from multicast perspective. This would happen if you had a domain, so I don't think you environment piece is a factor. By the way, you may want to evaluate Windows Server 2012 as it supports
WDS with non domain joined configuration called "stand alone".
Configure Windows Deployment Services (WDS) In Standalone Mode in Windows Server 2012
http://technet.microsoft.com/en-us/video/configure-windows-deployment-services-wds-in-standalone-mode-in-windows-server-2012.aspx
If I recall multicast is actually slower than unicast unless the number of deployments you have going concurrently are quite high. This is the best link that I know of that shows the speeds based on deployment type:
Optimizing Performance and Scalability
http://technet.microsoft.com/en-us/library/cc732088(v=WS.10).aspx
Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
I concur with Dave's post.
It's not a limitation of your environment, however multicast is only supported for data images. Once the OS is actually deployed, and the task sequence continues within Windows, all network traffic will be unicast as it will only access the deployment share
through smb.
The 'general' cutoff as to where multicast will become more effective vs unicast in terms of computers starts at about 50, more then 50 unicast connections at the same time will generally cause the wds server not being able to keep up to serve the data.
This still depends on the server's hardware, unless it's a really high end machine with fast storage you might be able to serve more then 50 unicast at a reasonable speed.
Kind regards,
Stephan Schwarz
If one of these posts answered your question or issue, please click on "Mark as answer".
My Blog | Twitter:
@Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
How to configure Windows RE/OEM Recovery Partition with MDT
How to configure Windows RE/OEM Recovery Partition with MDT 2012 Update 1

Microsoft Updates after Windows 7 Deployment using MDT 2010 Update 1

Hello,
After I deploy Windows 7 using MDT 2010 Update 1, i'm prompted to download and install updates. Updates which were installed prior to the capture process. During the capture process, does something reset Windows Update and makes it think the updates were
not installed?
My process of building a custom image is as follows:
1. PXE boot and kick-off a build task sequence (install OS + drivers + soe applications). (protectmypc = 3 in unattend.xml)
2. Download and install all Microsoft Updates, configure the OS, configure third-party applications.
3. Map a network drive to my deployment share, run litetouch.vbs and kick-off a capture task sequence.
4. PXE boot and kick-off a deployment task sequence. (copy profile = true, protectmypc = 1 in unattend.xml)

I'm getting updates but they are new updates. We have updates turned off through Group Policy and after an image is deployed it is attempting to install updates which should not be installed through Windows. I also have the protectmypc setting set to 3
and have updates turned off before capture. Something is searching for updates and during the deployment process and I need to find out how to stop this from happening. Someone has to know where these updates are coming from.
Joseph N. Sunderman | IT Professional

How to change default alerts in iCal?

Hello.
Every time you add a new event in iCal, the Info panel of the event contains a series of default alerts that you may want to add to it. However, all of them are useless to me (e.g.: "Send email to <my address> 4 days after), so I need to manually edit them event by event. Anybody knows how to change them? I have already inspected all the plist files related to ical, and looked inside the ical package content, but I found no indication of where to change these values. Using iCal version 5.0.2
Thanks,
l

John: Thank you, this is exactly what I wanted. I was indeed inspecting the plist with bbedit, but what I did not realize is that the file has some parts which are binary, so I could not see the PersistentMenu-lastUsedAlarms part by using a text editor. I opened it with Xcode and I did find what you were saying, and erased all the junk that was in there. In fact, the issue I had was also described here:
http://newsgroups.derkeiler.com/Archive/Uk/uk.comp.sys.mac/2010-06/msg02349.html
For some reason, it looks like after some upgrade the program adds were some positive values in the plist and I was stuck with default alarms that were set *after* the events I wanted to set an alarm for.
I did what you suggested, then added by hand new values to the PersistentMenu part of the plist, and I am now happy.
For everybody's information, to know what I did, it is enough to know to add Dictionary items to the PersistentMenu-lastUsedAlarms, with 3 fields:
-- AlarmTypeKey (this determines if you want a sound, or else an email, or else the other default alarm type keys. For example, sending an email is a Number, value 4; having a message with sound is a Number, value 3)
-- AlarmDurationKey: This is a Number, in seconds, that determines when you want your alarm to trigger. E.g: -172800 will be two days before. Must be negative for "before", of course)
-- AlarmParameterKey: This is a String, where you store the value that you want the alarm to have. For example, if you want an email to be sent, the AlarmTypeKey will be 4, as explained above, and this field will contain your email address. Instead, if you want the alarm to be a sound, the AlarmTypeKey will be 3 and this field will have the name of the sound you want (e.g., Basso).
That's it. Thanks a lot for the solution!
l.

Hi Support team, somehow my mozilla settings have been changed and it baceme transprenet, now how to change back to normal ?

Hi Support team, somehow my mozilla settings have been changed and it became transparent, now how to change back to normal because everything is transparent, menus, pages etc.

This could be the same problem other users are reporting as a white screen or black screen, caused by an incompatibility between Firefox 33 and some older graphics card/chipset drivers.
Please disable hardware acceleration as a temporary workaround. Step-by-step directions in this thread: https://support.mozilla.org/questions/1025438
Does that work?

MDT 2010: How to change WinPE drivers?

Similar Messages

Maybe you are looking for