Windows 7 Embedded & MDT 2010 Update 1

Hi,
Is it possible to deploy Win 7 Embedded with MDT 2010 U1 ? Is it supported by MS ?
Thanks,
Regards.

Hi,
Yes you can. Please see this video
Deploying Windows Embedded Standard 7 with Style
regards,
Blog Microsoft |
Déployer Windows 7 |
Améliorer les performances de Windows 7

Similar Messages

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

Unexpected restarts when deploying Windows 7 and Office 2010 updates

Hi
I am deploying Windows 7 and Office 2010 updates via SCCM 2012 sp1 and have a couple of questions
Question 1)
The updates are made available to clients at 9am on a Tuesday morning. The users get notification that updates are available to install. If the user doesn't install the updates, the client will wait 24hrs and then install the updates automatically.
We have set the restart behaviour to 24hrs, so again, the user will get a pop up saying that their machine will restart in 24hours. In my testing I have seen no more pop ups appear until 15 minutes before a restart is due and then a window appears
with a count down of 15 minutes but I think this might be standard behaviour. I am not sure why there are options in the client settings to remind users frequently about the impending installation of update but not of impending restarts. The
reason we delay the restart by 24hrs is to give the users the chance to restart their machines over night. Is there a way of providing more notifications of computer restarts ? The User Experience in the deployment of the updates is set to
Display in software center and show all notifications. We have Group Policy set to Not Configured for Windows Updates apart from the user policy
Remove Access To All Windows Update Features which is set to 0 - Do not show any notifications.
Question 2)
Another issue we have is that we have client machines restarting without any warning at all. I have tested setting the user experience to suppress restarts but have the issue regardless. It appears that this happens if the client
is off when the deployment schedule reaches its deadline and the restart time is missed. I had one user who did restart her machine because she was prompted to restart. When the machine came back up it looked like it installed another update and
then just resarted without any warning. This hasn't happened often but a one user was on a Lync call when the restart occured and she was not happy.
Any help would be much appreciated.
Thanks

Hi Daniel
I have done an RSOP on a VM I am testing and only have the user policy :
Remove Access To All Windows Update Features which is set to
0 - Do not show any notifications.
And the machine policy :
Specify intranet Microsoft update service location which is set to
Enabled The GPO Name is Local Group Policy
The policies look OK.
As a test I have deployed some updates and set the user experience to
Display all notifications and set the Suppress restarts
for both Servers and Workstations. When I deploy the updates, I get notifications that the updates are installing (when the deadline is met) and then I get a prompt telling me that a restart is required. I also get a windo letting me restart now
or I can ask to be reminded in x number of hours. This seems like expected behaviour. It does not force a restart. However if I leave the VM on over night I come in the following day and can see it has restarted. looking at the WindowsUpdate.log I
can see that at 3:15am the line AUInvoking reboot system. It looks like Windows Updates and not SCCM is forcing the restart.
Thanks

Failed to install drivers in Windows Vista using MDT 2012 update 1

I am trying to deploy physical machine with Windows vista along with drivers. After completion of deployment i see deployment is successful with no error and warnings, but it still do not install driver in the machine. To test weather i have selected correct
driver i checked manual installation of drivers and this install the driver in the machine. But the drivers are not installing when i am tried to install driver using MDT. In windows 7 and Windows XP drivers are installed correctly but not in Windows Vista.
I have shared my log files in one drive. Please look this and tell what mistake i am doing.
https://onedrive.live.com/?cid=BD291DD4A63B1353&id=BD291DD4A63B1353!107
https://onedrive.live.com/?cid=BD291DD4A63B1353&id=BD291DD4A63B1353!109
https://onedrive.live.com/?cid=BD291DD4A63B1353&id=BD291DD4A63B1353!108
https://onedrive.live.com/?cid=BD291DD4A63B1353&id=BD291DD4A63B1353!110
https://onedrive.live.com/?cid=BD291DD4A63B1353&id=BD291DD4A63B1353!112
https://onedrive.live.com/?cid=BD291DD4A63B1353&id=BD291DD4A63B1353!111
https://onedrive.live.com/?cid=BD291DD4A63B1353&id=BD291DD4A63B1353!114
https://onedrive.live.com/?cid=BD291DD4A63B1353&id=BD291DD4A63B1353!113

Can you be specific as to what drivers are not installing? An issue that can be had when doing PNPEnum is that child devices of something that does not have a driver installed are not visible to the PNPEnum. A way to get around that is you can force the
injection of drivers that are not getting installed. Something like you can add a second Inject Driver step but, have it be a selection profile of drivers that always get missed because they are children.
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.

Synaptics Pointting device Driver installs on an Desktop machine while deploying Windows 7X64 using MDT 2013 Update 1

I am deploying Windows 7X64 on Dell OptiPlex 990 and other desktops. Deployment goes fine but the Synaptics pointing device driver gets installed after the deployment is complete. Also after applying operating system I get a prompt to Run the Synaptics Pointing
Driver setup twice. If I don't click yes to install the TS wont proceed. Its gets worse when I uninstall the Synaptics Device Driver from Appwiz.Cpl and reboot the machine the Keyboard fails with the error Code:29. Above is the screenshot of what I get after
Applying Operating System step. Thanks in Advance.

I have also encountered this in MDT 2013 Lite Touch deployments for Windows 8.1 and I am researching it.
I noted that the Synaptics driver was installed for "SmBus" in Device Manager for a motherboard with an Intel 7 Cxxx Series chipset (Dell Optiplex desktop). The HardwareID's are all PCI\VEN8086...
We use %Model% in our task sequence and have a folder for each model such as "Optiplex 7010" in Out-of-Box Drivers.

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>

Deploy windows8 with custom partition using MDT 2012 update 1

Hi,
I am deploying windows 8 using MDT 2012 update 1 on SCCM 2012. I want C drive (to be quick format using task sequence) and D drive (remains same) on new system. While using diskpart , my D drive always get format . Can anyone suggest the steps.
Regards
Manish

Hi,
You could try steps in the following blog.
http://arnavsharma.net/4/post/2014/02/mdtformatting-only-c-drive-during-upgrade.html
(Note: Microsoft provides third-party contact information to help you find technical support. This contact
information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.)
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Vista is not installing using MDT 2012 update 1

I have created a media using selection profile in MDT 2012 update 1, but it is not deploying my physical machine. I get error message that Windows Cannot copy files required for installation. Make Sure all files required for installations are available.
However i have successfully deployed Windows & and Windows XP with MDT 2012.
I also used different iso image of vista but still i get same error message.

Looks like you have a *NEW* issue that is unrelated to this thread. Generally I recommend that you open a new thread.
How to Debug missing Drivers in MDT Litetouch
I see that you say there are *Problems* but you don't list which devices or drivers are missing.
From your Bdd.log file I can see that the following drivers are getting copied locally:
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\Net\e1c60x64_12.6.45.0_63DFBEA09BC1202B9E644652FC90898475BD80F6" "C:\Drivers\Net\e1c60x64_12.6.45.0_63DFBEA09BC1202B9E644652FC90898475BD80F6"
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\Net\e1c62x64_12.6.45.0_81A271BF21927B572C82D21D23EF89BD7E0ED315" "C:\Drivers\Net\e1c62x64_12.6.45.0_81A271BF21927B572C82D21D23EF89BD7E0ED315"
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\Net\e1c63x64_12.6.45.0_5B2448F2D9E89D0D8A718B71175BC6A559C8DC6A" "C:\Drivers\Net\e1c63x64_12.6.45.0_5B2448F2D9E89D0D8A718B71175BC6A559C8DC6A"
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9" "C:\Drivers\System\2008s4el_9.1.9.1005_2CA3E45C2F9AFCC12681EC010E1D73FEA7613AA9"
xcopy /seihycd "D:\Deploy\Out-of-box Drivers\System\cdvcore_9.2.2.1039_5676255595E54B75DA4EBCF4BB54B7CBA83C68D4" "C:\Drivers\System\cdvcore_9.2.2.1039_5676255595E54B75DA4EBCF4BB54B7CBA83C68D4"
However I can't tell what the problem is.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Deploy UDI Windows 10 with SCCM 2012 R2 and MDT 2013 Update 1

Hi,
Trying use "User-Driven Installation" with
SCCM 2012
R2 CU4 and MDT
2013 Update 1 for deploy Windows
10.
Created MDT Task Sequences with
template "Client Task sequence"
and Deployment Method "User-Driven Installation".
When I try to deploy I have error like:
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Part smsts.log
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Expand a string: WinPEandFullOS TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 22.04.2015 11:36:57 1160 (0x0488)
[ smsswd.exe ] InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
PackageID = '' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
BaseVar = '', ContinueOnError='' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
SwdAction = '0001' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Set command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Working dir 'not set' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Executing command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft (R) Windows Script Host Version 5.12 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Copyright (C) Microsoft Corporation. All rights reserved. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft Deployment Toolkit version: 6.3.8216.1000 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the action: Error in the task sequence.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionRetCode=5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 22.04.2015 11:36:57 1160 (0x0488)
Clear local default environment TSManager 22.04.2015 11:36:57 1160 (0x0488)
Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 22.04.2015 11:36:57 1160 (0x0488)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
The command completed successfully. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
Successfully launched command shell. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)

MDT Updates for Windows 10 Technical Preview Build 10041
Если Вам помог чей-либо ответ, пожалуйста, не забывайте жать на кнопку "Предложить как ответ" или "Пометить как ответ".
http://zalozny.com.ua

Deploy Windows XP Embedded using MDT?

Is there a way to deploy Windows XP Embedded (XPe) using MDT? If so, I could use step-by-step guidance on how to do so.
Currently we created the XPe wim file from our XPe computer but when we import it to the Deployment Share it is not recognized.

Which version of MDT are you running, Windows XP embedded is not supported by mdt 2012 or 2013

Windows XP Embedded Secuirty Updates

I apologize if this is in the wrong place but I was unable to find a Windows XP Embedded category.
I believe support for Windows XP Professional regarding security updates will end this year April 2014. Support for Windows XP Embedded lasts beyond that time. My question is does this mean that Microsoft will continue to release security patches
for Windows XP Embedded? If so then how will one obtain these patches? If Microsoft will not release security fixes / patches for Windows XP Embedded after the Windows XP Professional support ends what does the extended "support" of Windows XP Embedded
mean exactly?
This must have been answered somewhere, but I have been unable to find a definitive answer anywhere.

Cor,
Thanks I'll try to find some answers there.
Barry Wang, can you also suggest an appropriate forum where I can post and receive an answer to my question?
Thanks.

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

MDT 2012 Update 1 - Attempting to capture Windows Thin PC but it keeps looping after reboot.

I have been trying to capture a master image of Windows Thin PC we have prepared using MDT 2012 Update 1 but to no avail. When attempting the capture process using LiteTouch.vbs it syspreps and then reboots as it normally would and then it simply keeps rebooting
over and over in a loop.
I am unsure of how to bypass this and correctly capture Windows Thin PC using MDT 2012 Update 1. If anyone has any advice or feedback they can offer I would greatly appreciate it. Thank you.

Logs suggest that the script is most likely crashing early on.
I suspect that the reason for this is that the deployment share was *updated* from a previous version of MDT, and some files are out of date.
Can you update the share (full update, regenerate from scratch?)
Otherwise we may need to run Litetouch.wsf manually from within WinPE:
When WinPE Boots and you have a mouse, press F8.
Run TaskMgr.exe and verify that wscript.exe is no longer running (wait 2 minutes).
Then run the following command:
"cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture"
That should run the litetouch.wsf script and it should display any errors if found.
Keith Garner - keithga.wordpress.com

Rebranded from POSReady 2009 to Windows XP Embedded after updates

We are currently building a Windows Embedded POSReady 2009 image for a number of touch based terminals.
I started off by installing the base OS POSReady 2009 (non-evaluation version) and ran the windows update. After about 142 updates later my OS is now rebranded to Windows XP Embedded(System Properties, Login screens, etc...). I was able to narrow down the
problematic update to
KB975713
http://technet.microsoft.com/en-us/security/bulletin/MS10-007
due to the severity of the update and our terminals having a network connection we can not exclude the update from the build. I also checked the underlying OS using the method advised here
http://social.technet.microsoft.com/Forums/en-US/cd3a07e5-87c0-429e-ac81-4223dbb5e91b/xpe-vs-wepos?forum=posready
both pre and post updates are the same (HKEY_LOCAL_MACHINE\SYSTEM\WPA\POSReady = 1). Would it
be safe to assume the rebranding was skin deep?
This caused issue with our users as they are questioning our choice of OS due to Windows XP Embedded having a shorter end of life support vs Embedded POSReady 2009.
http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=embedded&Filter=FilterNO
We have thought about changing the images inside the dlls but decided it will violate the EULA. Is this correct?
The question is how would we go about changing the brand of the OS back to POSReady 2009 without violating the EULA?

Yes, for example that there is already IE7 included out-of-the-box instead of IE6, etc. (newer software versions), that there is 'fbreseal -keepall' optionally available instead of SysPrep and unattended setup is completely different. Additionally POSReady2009
comes with some interesting EEFs: FBWF for instance.
Best regards, Roman Maier

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

Windows 7 Embedded & MDT 2010 Update 1

Similar Messages

Maybe you are looking for