MDT 2013 capture error

Litetouch.wsf runs but after the sysprep reboot get error that can't connect to deploymentshare$ - but I have ip address and can map to share. Hope someone has seen this error before.

Could you post the exact error, please?
In the meantime;2 common things, check your credentials. Check your DNS.
Blog: http://scriptimus.wordpress.com

Similar Messages

SCCM 2012 R2 UDI Tasksequence (MDT 2013): Capture and Refresh UserState in one Tasksequence

Hi,
is it possible to first capture the user state in an UDI Tasksequence to USB or Network drive and afterwards, after re-installation restore the user state via restore user state step?
Customer wants this steps in refresh Scenario:
UDI Tasksequence starts within Windows
User configures Network drive to capture User State
Windows is reinstalled during Tasksequence
User State is restored in restore user state step (same TS)
Possible?
I can't find reliable Information?
Thanks for answers!
Regards,
ckuever

Hi,
Here is video for your reference.
Configuring MDT 2012 UDI Replace Computer Scenario
http://technet.microsoft.com/en-us/video/configuring-mdt-2012-udi-replace-computer-scenario
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.

MDT 2013: ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate: ActiveX component can't create object (429)

Hi,
I try to capture a custom image but at the end of the process, I get the following error (see attached image):
ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate: ActiveX component can't create object (429)
Could someone help me to solve this please?

Hi everybody,
I'm getting this message time to time and I don't know why. I have the ZTIWindowsUpdate.log who says:
<![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.6.7601.18804]LOG]!><time="15:35:07.000+000" date="04-14-2015" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
<![LOG[ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate: ActiveX component can't create object (429)]LOG]!><time="15:35:37.000+000" date="04-14-2015" component="ZTIWindowsUpdate" context="" type="3"
thread="" file="ZTIWindowsUpdate">
<![LOG[Event 41002 sent: ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate: ActiveX component can't create object (429)]LOG]!><time="15:35:38.000+000" date="04-14-2015" component="ZTIWindowsUpdate" context=""
type="1" thread="" file="ZTIWindowsUpdate">
Do we have an explanation for this issue? Or, do you know how to fix that?

MDT 2013 - Capture WIM vs. Domain Join in rules.ini

Hi,
Pre MDT2013 it was possible to have domain join settings in the rules.ini and run capture tasks.
rules.ini ->
JoinDomain=<my domain>
DomainAdmin=<domain join account>
DomainAdminDomain=<domain>
DomainAdminPassword=<password>
MachineObjectOU=OU=Computers Germany,OU=_Computers,OU=EU Offices,DC=bar,DC=foo,DC=com
On MDT2013, whenever I enable my domain join settings capture task will cancel shortly upon start.
Is this a desired behaviour?
How are you working aroun that?
Regards,
Albert

Albert,
My recommendation would be to create a second Deployment Share and use that only for Build & Capture Task Sequences.
I blogged about this a while ago, and I think it would work well for you (Build and Capture Task Sequence)
I recommend re-building your image you want to capture each time. This way you have a clean build with less patches on it (as the superseded patches will not be applied).
If you don't (or can't) do this, then you should try the following:
Assumptions
* Task sequence is named SYSPREPCAP
* I think from reading your previous posts that you don't want to join this to the domain, but you want all other TS's to join.
You'll want to try this in your CustomSettings.ini file.
[Settings]
Priority=TaskSequenceID, Default
[SYSPREPCAP]
JoinWorkgroup=WORKGROUP
[DEFAULT]
JoinDomain=<my domain>
DomainAdmin=<domain join account>
DomainAdminDomain=<domain>
DomainAdminPassword=<password>
MachineObjectOU=OU=Computers Germany,OU=_Computers,OU=EU Offices,DC=bar,DC=foo,DC=com

Unable to capture images since upgrade to MDT 2013

I recently updated MDT 2012 to MDT 2013 to enable support for Windows 8.1. Under MDT 2012 I was able to both capture and deploy images without an issue. Since upgrading to MDT 2013 I've had nothing but grief. When I launch my Sysprep and Capture task I am
returned with the following error:
Error creating an image of drive D:, rc=2ZTI ERROR -Non-zero return code by ZTIBackup, rc=2Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Create WIM.
The system cannot find the file specified. (Error: 00000002; Source: Windows)
The execution of the group (Capture Image) has failed and the execution has been aborted.
An action failed.
Operation aborted (Error: 80004004; Source Windows)
Failed to run the last action Create WIM. Execution of task sequence failed.
The system cannot find the file specified. (Error 00000002; Source: Windows)
Task Sequence Engine Failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error TAsk Sequence Manager failed to execute task sequence. Code 0x80004005
Once the machine boots up again I check the BDD log located in C:\Windows\Temp\DeploymentLogs and notice the following error:
<![LOG[ Console > Error opening file [\\rmh-vm-mdt2012\DeploymentShare$\Captures\WINDOWS.8.1.REF.wim].]LOG]!><time="10:23:55.000+000" date="02-06-2014" component="ZTIBackup" context="" type="1"
thread="" file="ZTIBackup">
<![LOG[ Console > Access is denied. ]LOG]!><time="10:23:55.000+000" date="02-06-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
My issue appears to be a permissions problem. For troubleshooting purposes I've given Everyone full access to \DeploymentShare$ however the problem continues to persist.
I'm not sure where to go from here. Hoping someone can help.
Thanks.

Additionally, ensure that the share itself is marked R/W access.
As a test, boot to WinPE and try to create a file, any file on the share.
However, Lordy86 may have the correct solution :^).
Keith Garner - keithga.wordpress.com

MDT 2013 won't capture 8.1 image, does not boot to PE to capture

I am doing this with Server 2012 R2 and MDT 2013, and the reference machines are VMs
I initially created a deployment share for creating windows 7 and windows 8.1 reference images and capturing and deployment worked ok. After getting into some more details i customized the deployment share customsettings to make things easier and created
a separate capture share for capturing new reference images. I updated permissions on the share so my service account has access to it.
In this share i imported the windows 8.1 os files and copied the sysprep and capture task sequence i used to capture my first reference image [from the original deployment share], but when running the task sequence it reboots and just goes back into windows,
instead of windows PE to capture the image.
I copied a windows 7 capture sequence to the capture share, imported the windows 7 files and updated the task, and it rebooted into PE without a problem and copied an image. so I don't believe I have any permissions/customsettings problems with the new share.
Im not seeing any errors jump out at me in the bdd.log but I'm new-ish to going over the logs and using MDT to start with so I may be missing the obvious. I am using SMS trace and dont see any red/yellow highlites either.
In windows 7 i did have the vm in audit mode when i mapped the share as an admin and started the task sequence. In windows 8.1 i am not in audit mode [after doing some research and learning more about using MDT it did not seem necessary]
After comparing a run of the windows 7 task to windows 8 i see the boot.wim copied to the win 7 vm, but i dont see it on the win 8 vm. There is a partition created, i cant see data in it when i show hidden files.
rules for the capture share
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
Heres the last part of bdd.log. New here so I can't post a link yet, didnt know if i should post the whole thing here or not to start with.
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property PHASE is now = CUSTOM]LOG]!><time="08:29:38.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[--------- Script Start ---------]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[LTICopyScripts processing completed successfully.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
<![LOG[Creating startup folder item to run LiteTouch.wsf once the shell is loaded.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Shortcut "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\LiteTouch.lnk" created.]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property BootPE is now = ]LOG]!><time="08:29:43.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="08:32:24.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="E:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\WIN81-REF\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\WIN81-REF\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\WIN81-REF\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = E: C:]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[No task sequence is in progress.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE.]LOG]!><time="08:32:25.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Phase = CUSTOM]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = Z:]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:26.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentType = CUSTOM]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceRoot = \\2012R2_TEST\CaptureShare$]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property ResourceDrive is now = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceDrive = Z:]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[SMS Task Sequencer already found on C:\MININT\Tools\X64]LOG]!><time="08:32:27.000+000" date="03-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Thanks for your reply.
The pc is not in the domain when i run litetouch. It was joined after install, then i run some local gpos/scripts against it, install all of the shared printers from servers, then i put it back in a workgroup, login as the local administrator, delete the
domain profiles and guids in the registry, briefly connected back to a domain server [not with a mapped drive] to copy a couple of files, rebooted into the local admin account an ran litetouch.
After running litetouch.wsf the first time in the windows 8.1 pro vm [no changes, but manual connection] it rebooted without sysprepping or taking an image
I deleted the task sequence and created another one with "sysprep and capture" as the sequence. i made no changes to the task sequence. did all of the above, ran litetouch, and it just reboots. sysprep does not run and windows pe does not load.
if i run sysprep and boot into audit mode [as a test, since my windows 7 vm snapshot was in audit mode when it runs litetouch.wsf], then run litetouch, sysprep works, then it DID capture an image, but after that image was capture and the VM rebooted, i got
this error when loading windows 8
"windows could not complete the installation. To install windows on this computer, restart the installation" and if i hit ok it will reboot and error out again.
Haven't had any issues with that VM until now.
I reverted to my snapshot and just ran sysprep oobe w/ generalize to see how it would react
it failed, setuperr.log shows SYSPRP failed to remove apps for the current user. some searching gives me information on that and makes me think its related to adding/deleting user profiles? i dont actually use or update the apps at all, i have a deploy task
that removed most of them and customizes the start screen and those seem to work without issue.
found this as my reference: http://support.microsoft.com/kb/2769827/en-nz
Sysprep has an additional provider that is added in Windows 8 to clean appx packages and generalize the image. The provider will only work if the Appx package is a per-user package or an all-user provisioned package.
and
Resolution
The correct way of removing the package is to remove the package for the user running sysprep and also remove the provisioning. This can be done using the following Powershell cmdlets:
Import-Module Appx
Import-Module Dism
Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation
if i run that i get a lot of
[unknown user]: installed
Do I just need to revise my process and start from scratch? or at least just never actually join the domain and user other profiles? thats a convenience thing so its not a big deal, really.
I have an image made in a similar way that works, but doesnt have quite all the updates/changes i wanted. It captured [at the time] fine and installs without issue
Heres an overview of what I do [i am open to some revisions on this]
-deploy windows 8 base install from MDT
-join domain, login with service account [just makes getting to some things easier]
-install office 2010 pro plus w/ sp2 [i do understand that these can be set as an MDT app but the install takes a while and i dont like waiting on it if i dont have to]
-install windows updates [no WSUs server currently, on my future to-do list, not my decision right now and i do understand the benefits of having one]
-connect to servers and install all network printers [we have so many that i dont want to wait on the drivers when we do a big roll out soon]
-install oracle software [i can get it to automate in windows 7, not 8, so i dont want to manually deal with it post-install]
-install adobe reader/java [i do understand that these can be set as an MDT app]
-leave domain, reboot, login as local admin
-clean domain profiles/registry guids
-make some local gpoedits [we dont have 8.1 enterprise and just want the start screen locked down]
-install our AV network agent
-lite touch.
any advice is appreciated

Error While Using MDT 2013 to Refresh Windows XP to Windows 8.1 during Computer backup to network

Hi,
I am getting below error in Deployment Summary while Computer backup to network during Refresh from XP to 8.1 through MDT 2013.
1. I followed URL-
http://blogs.technet.com/b/mniehaus/archive/2014/01/09/migrating-from-windows-xp-to-windows-8-1-using-mdt-2013.aspx to use USMT for the UserProfile through MDT 2013.
2. For User profile I am using Hardlink USMT through MDT Wizard, that is working fine.
3. My Deployment Share rule is below..
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
DoCapture=YES
ComputerBackupLocation=NETWORK
BackupShare=\\MDT2013\share$
BackupDir=%OSDComputerName%
BackupFile=%OSDComputerName%.wim
BackupDrive=ALL
4. ZTIBAckup Logs below..
2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context=""
type="1" thread="" file="ZTIBackup">
<![LOG[OriginalPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '26213933056' and VolumeName = '' and VolumeSerialNumber = '7413DBF4']LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup"
context="" type="1" thread="" file="ZTIBackup">
<![LOG[Search for Drive: OriginalPartitionIdentifier SELECT * FROM Win32_LogicalDisk WHERE Size = '26213933056' and VolumeName = '' and VolumeSerialNumber = '7413DBF4']LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup"
context="" type="1" thread="" file="ZTIBackup">
<![LOG[Found Drive: C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDisk is now = C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Checking to see if we can store the backup locally]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive C: 3231300]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive D: 272600]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive X: 2489]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Local store path = C:\StateStore]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Total used space: 3506389]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Available space at C:\StateStore: 22368244]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Backup can use local path]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property USMTLocal is now = True]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Network store path set to:
\\MDT2013\DeploymentShare$\Tools\X64\imagex.exe" /capture /compress maximum C: "\\MDT2013\share$\TEST8\TEST8.wim" "001CDrive" /flags EnterpriseN]LOG]!><time="13:16:21.000+000"
date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Command has been started (process ID 1248)]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1248)]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > ImageX Tool for Windows]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Version: 6.3.9600.16411]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Files/folders excluded from image capture by default:]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~bt]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~ls]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \winpepge.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Windows\CSC]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycled]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycler]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$Recycle.Bin\*]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \System Volume Information]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \swapfile.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \pagefile.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \hiberfil.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Turning on VERIFY option for network share]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Scanning files and directories...]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [   0% ] Capturing progress ]LOG]!><time="13:16:33.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [   1% ] Capturing progress ]LOG]!><time="13:16:33.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [   2% ] Capturing progress: 11:04 mins remaining ]LOG]!><time="13:16:47.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   3% ] Capturing progress: 9:12 mins remaining ]LOG]!><time="13:16:47.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   4% ] Capturing progress: 7:58 mins remaining ]LOG]!><time="13:16:50.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   5% ] Capturing progress: 7:20 mins remaining ]LOG]!><time="13:16:55.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   6% ] Capturing progress: 7:59 mins remaining ]LOG]!><time="13:17:07.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   7% ] Capturing progress: 8:23 mins remaining ]LOG]!><time="13:17:13.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   8% ] Capturing progress: 8:20 mins remaining ]LOG]!><time="13:17:17.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   9% ] Capturing progress: 8:33 mins remaining ]LOG]!><time="13:17:26.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 11% ] Capturing progress: 8:21 mins remaining ]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 13% ] Capturing progress: 7:37 mins remaining ]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ RETRY ] Restoring C:\WIMA8B0.tmp again (Error = 1392)]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ ERROR ] C:\StateStore\USMT\File\C$\MININT\SMSOSD\OSDLOGS\BDD.log (Error = 80)]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1"
thread="" file="ZTIBackup">
<![LOG[ Console > [ ERROR ] C:\StateStore\USMT\File\C$\MININT\SMSOSD\OSDLOGS\BDD.log (Error = 80)]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1"
thread="" file="ZTIBackup">
<![LOG[ Console > Error imaging drive [C:\]]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > The file exists. ]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Return code from command = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Error creating an image of drive C:, rc = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">
<![LOG[ZTIBackup COMPLETED. Return Value = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI ERROR - Non-zero return code by ZTIBackup, rc = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">
5. Computer Backup Dir is accessbaile and permission is ok.
Any idea to resolve this issue
Shailendra Dev

After changing the BackupDrive=D: , I am able to take backup of D drive only , but I want to take all the local drives backup before installing windows 8.1
please suggest .
Shailendra Dev

Since upgrade to MDT 2013, can't capture Windows 7 image.

Hi fellas,
I use Virtual Box to create a 32- and 64-bit reference Windows 7 VM, which I then capture using an MDT Sysprep & Capture TS. This worked without a hitch using MDT 2012.
I recently upgraded to MDT 2013. Since then, after the VM syspreps and reboots, I get a boot manager error saying Windows failed to start. Status: 0xc0000260.
Not sure where to look for any logs. What I've done so far:
- Upgraded to latest version of Virtual Box (4.3.18)
- Rebuilt both VMs from scratch.
- Deleted and recreated the deployment share and Sysprep & Capture task sequences.
Stumped for the time being, although I could always just boot to my Win PE disc and manually capture with imagex. But c'mon.

Thanks for your input, but this is indeed a configuration issue, and it makes sense.
Vbox VMs are configured according to the guest OS installed on them. For my Windows 7 x64 VM, it's configured of course to run as Windows 7 x64. In the MDT 2012 environment, the Windows PE version
was 3.0, which is based on Windows 7, and hence the VM could boot to it since it was configured for it.
But MDT 2013 uses PE 5.0, based on 8.1. The VM crashes or throws an error when trying to boot the PE 5.0 boot image. I went into the VM's settings and changed the Guest OS to 8.1 x64, and it booted successfully to Windows PE and captured the
image according to the Sysprep & Capture sequence.
Sorry for the wild goose chase fellas. This should've been the first thing I checked.

Server 2012 R2 + MDT 2013 + WINLOAD.EXE error

Hi All,
After watching some videos on MDT 2013 integration with SCCM 2012 I have been testing some builds of Windows Server 2012 R2. The MDT 2013 integration is working well with Database look-ups providing the required rules for customsettings.ini. To coincide
with the tests I am using the MDT 2013 Server Task Sequence Template.
Unfortunately I am hitting an error whereby, when using the MDT Task Sequence the full Operating System fails to start with a:
\Windows\System32\Winload.exe, 0xC000000F, File is Missing or Corrupt
Note: This is happening when the full OS is starting up. This is not a WinPE startup issue.
When I use a non-MDT Task Sequence, i.e. a typical task sequence we use for OSD the build process works OK. We still have MDT database integration working in that Task Sequence however.
Some background info:
As per our normal process we are using a Windows Server 2012 R2 Capture image. The reference machine was build and capture using a partition scheme of (Partition 1 - 500MB + No Drive Letter + Hidden, Partition 2 - 100% of disk - Drive C:\)
This is a new SCCM 2012 R2 implementation and as such we installed CU3 as part of our build process. CU4 is yet to be applied.
Our WinPE Boot Images are WinPE 5 with a build number of 6.3.9600.16384
As we have an existing SCCM 2007 environment I am currently using USB Boot media to kick off the Task Sequence
We are only considering a "New Computer" build scenario. The MDT 2013 Task Sequence already detects that because the "_SMSTSinWinPE" = True.
In both Task sequences the Format and Partition step is as follows:
Disk 0
Standard(MBR)
BDEDrive (Primary) - 499MB, Marked Active with variable BDEDrive assigned
OSDisk (Primary) - 90GB variable OSDisk assigned
In both Task sequences the Apply Operating System step is as follows:
Using Captured Image
Apply operating system from a captured image (Image 2-2)
Apply image to Logical Drive (OSDisk)
In both Task sequences the Apply Data Image step is as follows:
Using Captured Image
Image 1-1 (from the same captured image as shown above)
Apply image to Logical Drive (BDEDrive)
What has been done so far:
Already eliminated driver packs as the problem occurs with and without them
Have monitored the build process (during WinPE that is) to determine what disks and partitions are in play at that stage. The 500MB BDE and 90GB OS Partitions are created as expected. The Apply OS and Apply Data Image steps are applying to the correct partitions.
I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /fixmbr + bootrec /fixboot
I have used the Windows Server 2012 R2 Installation CD and tried to run a bootrec /rebuildbcd
I have tried toggling the "OSDPreserveDriveLetter" variable from True to False and back again. Based on my interpretation of the SCCM 2012 R2 + Windows Server 2012 drive letter issue this should be set to True so the capture image drive letters
are preserved.
I have disabled an UEFI Partitioning steps just as a precaution.
There is no Bitlocker steps involved yet.
I have trawled through the SMSTS.LOG. So far it looks OK to me:
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: WinPEandFullOS TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Executing command line: tsenv.exe "OSDPreserveDriveLetter=True" TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Finished with error code 0 TSEnv 18/02/15 8:09:49 AM 728 (0x02D8)
Process completed with exit code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Successfully completed the action (Set Variable for Drive Letter) with the exit win32 code 0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
MP server https://SOMETHING24.SOMETHING. Ports 80,443. CRL=false. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting authenticator TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set authenticator in transport TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Sending StatusMessage TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting message signatures. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Setting the authenticator. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 CCM_POST /ccm_system_AltAuth/request TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
In SSL, but with no client cert TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Request was successful. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Clear local default environment TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Updated security on object D:\_SMSTaskSequence. TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a TS execution environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a TS execution environment variable _SMSTSInstructionStackString=0 33 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Save the current environment block TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Successfully save execution state and environment to local hard disk TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Start executing an instruction. Instruction name: Apply Operating System Image. Instruction pointer: 43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSCurrentActionName=Apply Operating System Image TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSNextInstructionPointer=43 TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a local default variable OSDImageIndex TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Command line for extension .exe is "%1" %* TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Set command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Start executing the command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
!--------------------------------------------------------------------------------------------! TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Expand a string: WinPE TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Executing command line: OSDApplyOS.exe /image:S0200034,%OSDImageIndex% /target:%OSDisk% /runfromnet:False TSManager 18/02/15 8:09:49 AM 1048 (0x0418)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Set command line: "OSDApplyOS.exe" /image:S0200034,2 /target:D: /runfromnet:False ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Found run from net option: 0 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Not a data image ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
ApplyOSRetry: ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
TSLaunchMode: UFD ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
'C:\' not a removable drive ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The volume D:\ exists and is a local hard drive. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The volume D:\ is using a valid file system. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Windows target partition is 0-2, driver letter is D:\ ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Verifying boot volume is NTFS. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
The machine does not have a local client cache. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
ResolveSource flags: 0x00000001 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
SMSTSPersistContent: . The content for package S0200034 will be persisted ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
DownloadOnDemand flag is true. Attempting to download content locally for Package S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Locations: Multicast = 0, HTTP = 2, SMB = 0. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Package Flags: 0x01000000 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Multicast is not enabled for the package. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Trying https://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
GetDirectoryListing() entered ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Initializing HTTP transport. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Setting Authenticator. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Set authenticator in transport ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Setting Media Certificate. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
WinHttp credentials set ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
CLibSMSMessageWinHttpTransport::Send: URL: SOMETHING24.SOMETHING:443 PROPFIND /NOCERT_SMS_DP_SMSPKG$/S0200034 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
In SSL, but with no client cert ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Using thread token for request ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Request was successful. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
DAV response string is:
<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/sccm?/S0200034/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://SOMETHING24.SOMETHING/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim</D:displayname><D:getlastmodified>Tue, 10 Feb 2015 04:56:27 GMT</D:getlastmodified><D:getcontentlength>6814100762</D:getcontentlength></D:prop></D:propstat></D:response></D:multistatus> ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
List of files to be downloaded ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
File: http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
GetDirectoryListing() successfully completed ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with anonymous access. Retrying with context credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
401 - Unsuccessful with context credentials. Retrying with supplied credentials. ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 0-2147483646 ApplyOperatingSystem 18/02/15 8:09:49 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 2147483647-4294967293 ApplyOperatingSystem 18/02/15 8:10:40 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 4294967294-6442450940 ApplyOperatingSystem 18/02/15 8:11:23 AM 724 (0x02D4)
Downloading file /NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim range 6442450941-6814100761 ApplyOperatingSystem 18/02/15 8:12:14 AM 724 (0x02D4)
Downloaded file from http://SOMETHING24.SOMETHING:443/NOCERT_SMS_DP_SMSPKG$/S0200034/sccm?/dos-20150210.wim to D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
VerifyContentHash: Hash algorithm is 32780 ApplyOperatingSystem 18/02/15 8:12:21 AM 724 (0x02D4)
Content successfully downloaded at D:\_SMSTaskSequence\Packages\S0200034. ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Opening image file D:\_SMSTaskSequence\Packages\S0200034\dos-20150210.wim ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Image file S0200034 version "2015-02-10" will be applied ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Starting to apply image 2 from dos-20150210.wim to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Wiping D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "D:\_SMSTaskSequence" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%OSDStateStorePath%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%_SMSTSClientCache%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Skipping D:\System Volume Information for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Skipping D:\_SMSTaskSequence for wipe ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Calculating expected free space. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
Reporting deletion progress. ApplyOperatingSystem 18/02/15 8:14:12 AM 1764 (0x06E4)
Successfully wiped D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Applying image to D:\ ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Applying image 2 to volume D: ApplyOperatingSystem 18/02/15 8:14:12 AM 724 (0x02D4)
Executing command line: X:\windows\system32\cmd.exe /k TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
The command completed successfully. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
Successfully launched command shell. TSBootShell 18/02/15 8:14:22 AM 780 (0x030C)
Successfully applied image to D:\ ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:07 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
System root for target OS is D:\Windows, System drive is D: ApplyOperatingSystem 18/02/15 8:21:08 AM 724 (0x02D4)
OS Version is 6.3 ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
Successfully loaded a source BCD boot system ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
SetupNewOS: Loaded source boot system from target volume "D:\" ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
BootLoader::restore: D:\, C:\ ApplyOperatingSystem 18/02/15 8:21:09 AM 724 (0x02D4)
Saving bcd store to D:\_SMSTaskSequence\ApplyBootSystem\boot\BCD ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Set command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Executing command line: "bcdboot.exe" D:\Windows /s C:\ /l en-US ApplyOperatingSystem 18/02/15 8:21:10 AM 724 (0x02D4)
Process completed with exit code 0 ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:11 AM 724 (0x02D4)
Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:12 AM 724 (0x02D4)
Updating MountedDevices key in target system registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
OfflineRegistry::Init("D:\Windows") ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
CurrentControlSet is mapped to ControlSet001 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
OS volume after boot is: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Reading '\DosDevices\D:' value under MountedDevices in WinPE registry ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 0 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272081-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 1 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272089-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 2 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208a-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 3 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 4 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27208c-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 5 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\X:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 6 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272095-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 7 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272098-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 8 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\G:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 9 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\H:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 10 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\I:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 11 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb27209b-b6e8-11e4-9b22-806e6f6e6963}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 12 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\DosDevices\J:' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 13 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720cf-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 14 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720d2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 15 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720d5-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 16 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb2720e2-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 17 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb2720f3-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 18 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '#{cb272126-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerating index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Enumerated index: 19 ApplyOperatingSystem 18/02/15 8:21:13 AM 724 (0x02D4)
Found value: '\??\Volume{cb272139-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerating index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerated index: 20 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Found value: '\DosDevices\C:' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerating index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Enumerated index: 21 ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Found value: '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Data for value '\DosDevices\D:' matches data for value '\??\Volume{cb27213d-b6e8-11e4-9b22-a4badb3da627}' ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Done enumerating. Closing mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Closed mounted devices key. ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Deleting MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Creating new MountedDevices key on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Writing new values to MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Successfully updated MountedDevices on target system ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Unloading offline SOFTWARE registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Unloading offline SYSTEM registry hive ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Finished updating MountedDevices in target system registry (0x00000000) ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing up known name surrogate reparse points... ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\Documents and Settings] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\History] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Microsoft\Windows\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\AppData\Local\Temporary Internet Files] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\Application Data] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\users\Administrator\Cookies] ApplyOperatingSystem 18/02/15 8:21:14 AM 724 (0x02D4)
Fixing junction point path [D:\use
The fact that our normal Task Sequence works OK eliminates the Capture image and the WinPE boot images. It must be something I have not configured or configured incorrectly in the MDT task sequence.
Any suggestions would be great.
NSutton

Hi,
If I were you, I would Streamline the MDT Task Sequence to find the root cause.
Moreover, please refer to the link below:
How to fix Windows System32 Winload.exe Missing Or Corrupt 0xc000000f Error?
http://winwiki.org/windows-system32-winload-exe-missing-or-corrupt-0xc000000f/
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.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Creating Windows 8.1 master image with MDT 2013,cannot capture .WIM

I am having an issue with creating a master image with Windows 8.1 and MDT 2013.
I have followed extensive tutorials on how to create a master image using Microsoft Deployment Toolkit. my goal is to have a fully configured windows 8.1 image which I can deploy through Windows Deployment Services. I have been relatively successful thus far,
except for one issue I have run into, which is successfully capturing this image as a .WIM.
I have successfully created a task sequence and the task sequence is able to run all the way through until the final step. Essentially the task sequence is supposed to install Windows and Office, then suspend the task sequence to allow me to make customisations
to the start screen and desktop background, and I simply click resume task sequence, and the task sequence should sysprep reboot and capture the machine image as a .WIM file.
the task sequence is able to sysprep the machine, but upon rebooting it boots into out of box experience, and does not create a wim file. I receive an error saying: "cannot find script file C:\ltibootstrap.Vbs" after the machine completes OOBE
I am using Windows Server 2012 r2, creating my Master machine image using hyper-v, and my master image is running Windows 8.1.
Any help would be greatly appreciated.

I'm not sure about the sequence of steps here. Try taking your captured.wim file and deploying it using MDT again, or at least to another machine. MDT sometimes leaves extra files around on the captured machine, so simply rebooting it may not get a accurate
test results.
IF you are getting the ltibootstrap.vbs it is most likely because there is a stray unattend.xml file somewhere in your image that is looking for this file. Crack open your Wim file and search for any unattend.xml files.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Issue with Capture Task Option showing correctly in MDT 2013

I am aware that having the variable of DomainJoin will prevent the capture dialog from appearing when running the task. The problem is, even when the options are greyed out due to the domain settings not being applied from a different setting in the workflow
it still breaks the task.
E.G.
I am using the database, and have my workflow as such:
[Settings]
Priority=Model, TaskSequenceID, LSettings, CRoles, RApps, LApps, MMApps, MMSettings, Default
Properties=MyCustomProperty
DataBase:
Location Settings: Overall settings for Domain join, wizard skips, etc info per gateway
Role Apps: Apps per role
Make/Model Apps: Apps specific to a piece of hardware
CustomSettings INI:
Model/Task Sequence/Default: I have tried to null out the DomainJoin settings with these variables by adding workgroup join by task ID, Model, etc and nothing seems to work. I've verified in other tasks
that these settings take place of what's in the DB, but the DB settings are still there, greyed out and causing an issue.
[X86SYSANDCAP]
JoinDomain=
JoinWorkgroup=WORKGROUP
[VMware Virtual Platform]
JoinDomain=
JoinWorkgroup=WORKGROUP
As shown below the model/TS specify the workgroup (1st pic is normal deploy, 2nd is cap) but the greyed out settings are still having an effect. Skip Capture is set to NO at each level, and when I remove the Domain from the DB it shows up correctly.
Not sure what to do besides removing the domain everytime I want to do a capture, which seems a bit unreasonable and I don;t want my T1s in the DB.

I highly recommend to always use the standard Client task sequence for a build and capture. Much more reliable.
Check out these Resources, the info is also valid for Windows 7:
TechNet Docs - Create a Windows 8.1 Reference Image
http://technet.microsoft.com/en-us/library/dn744290.aspx
Virtual Hands-On-Labs - Creating a Windows 8.1 reference image
http://go.microsoft.com/?linkid=9845755
How to deploy Windows 8.1 (and Windows 7) with MDT 2013 - The Resources
http://www.deploymentresearch.com/Research/tabid/62/EntryId/186/How-to-deploy-Windows-8-1-and-Windows-7-with-MDT-2013-The-Resources.aspx
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Error when deploying LiteTouch image using MDT 2013 Media Flashdrive

Please help! I have created a media flash drive (drive capacity: 64Gb) to deploy LiteTouch x86 and x64 images (Win7 and Win8, 8.1) to PCs but getting error for the 3rd time. I am using the following tools in my environment: i am using MDT 2013 on a Windows
2k8 WDS server. PXE boot works fine deploying images but i keep getting this error after creating the Media flash drive). I first got the same failure with 14 errors but recreated the media on the WorkBench using a different selection profile but now i am
getting this error: (by the way where is the BDD.LOG?)
"Deployment Summary
During the deployment process, 8 errors and 0 warnings were reported.
Details...
Failure ( 5456): Unable to determine destination disk, partition, and/or drive. See BDD.LOG for more information.
Litetouch deployment failed, return code = -2147467259 0x80004005
Failed to run the action: inject drivers.
Unknown error (error: 00001550; source: unknown)
The execution of the group (preinstall) has failed and the execution has been aborted. An acton failed.
Operation aborted (error: 80004004; xource: windows)
Task sequence engine failed! code:enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. code 0x80004005

I am planning to build a WDS with Win2k12 and MDT2013 and perhaps will be lucky to create a successful media. I created one with my WDS Win2k8 it works on a HP laptop but failed on other machines like Dell...
Did you get driver injection in configuration WDS and MDT?
Considering if the incompatible drivers cause your issue.
If you can post back the MDT log during the deployment on DELL computers, it would be helpful for us to determine your issue.
Kate Li
TechNet Community Support

MDT 2013 - Errors on Install Operating System

Hi,
I have previously been using batch files to deploy our WIM files using ImageX.
I'm trying to make them work with MDT 2013 now and thought I had it all working.
I can happily deploy the image to a HP Pro 6200 desktop PC and told my colleagues to start using it.
The first PC they tried to do was a HP ProDesk 600 G1 EFF - and disaster, the process fails! I made sure I had the latest drivers and it made no difference. There are several errors shown in the output: 0x80004005, 0x80004004 and 000015F8.
The MDT server is running as a guest inside VMware. I did a little testing and if I try to run the task sequence in a VM on the same host its fine, but if I move that VM to the other (identical) host it doesn't work.
I started pinging the MDT server from the ProDesk 600 and the response times are usually <1ms, but they randomly jump up, to 28ms in one case, although didn't watch for long.
Has anyone else encountered anything like this? Going to try manoeuvring everything to be within the one switch next.

Hi,
I have previously been using batch files to deploy our WIM files using ImageX.
I'm trying to make them work with MDT 2013 now and thought I had it all working.
I can happily deploy the image to a HP Pro 6200 desktop PC and told my colleagues to start using it.
The first PC they tried to do was a HP ProDesk 600 G1 EFF - and disaster, the process fails! I made sure I had the latest drivers and it made no difference. There are several errors shown in the output: 0x80004005, 0x80004004 and 000015F8.
The MDT server is running as a guest inside VMware. I did a little testing and if I try to run the task sequence in a VM on the same host its fine, but if I move that VM to the other (identical) host it doesn't work.
I started pinging the MDT server from the ProDesk 600 and the response times are usually <1ms, but they randomly jump up, to 28ms in one case, although didn't watch for long.
Has anyone else encountered anything like this? Going to try manoeuvring everything to be within the one switch next.
The first PC they tried to do was a HP ProDesk 600 G1 EFF - and disaster, the process fails!
Do you have log files? Please define the process fails. Where is it failing.
There are several errors shown in the output: 0x80004005, 0x80004004 and 000015F8-
are generic error codes, hence not enough info
If this post is helpful please click "Mark for answer", thanks! Kind regards

MDT 2013 supports build and capture win 7 SP1

Hi,
Just want to have a check if MDT 2013 supports Build and capture windows 7 as image (wim)?
I know it is supporting windows 7 as supported OS for deployment.
Regards,

Yes it does:
http://technet.microsoft.com/en-US/windows/dn475741.aspx
Good luck!

Upgraded to MDT 2013 - old deployments not working - parse error - copyprofile error

I upgraded from MDT 2012 U1 and Waik to MDT 2013 and ADK 8.1. My windows 7 deployments quit working after the upgrade. I installed ADK 8.1 and upgraded 2012 to 2013 then upgraded the deployment share. Since the upgrade I am getting copyprofile errors
when MDT is trying to sysprep the machine then I am in a reboot loop. Not sure what changed. The error is "windows could not
parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file
cannot be applied." In the setup log files it says the copyprofile could not be done. The deployments all worked before the upgrade. Any ideas? Thanks.

Thanks for your reply. My DISM file doesnt tell me anything. It is not at the location after the system reboots. The exact message I get is
Windows could not parse or process the unattend answer file for pass(specialize) The settings specified in the answer file cannot be applied. The error was detected while processing settings for component Microsoft windows Shell Setup.
I get this message from all of my windows 7 images when trying to apply them. These were okay until I updated the deployment share for MDT 2013. Under the shell setup in the unattend.xml I have
BluetoothTaskbarIconEnabled (blank)
ComputerName (blank)
CopyProfile True
DisableAutoDaylightTime false
DoNotCleanTaskBar True
ProductKey (blank)
RegisteredOrganization CompanyName
RegisterOwner CompanyUser
ShowWindowsLive false
StartPanelOff (blank)
TimeZone Central Standard Time
Something in the unattend.xml that 2013 doesnt like perhaps?
Thanks..

MDT 2013 capture error

Similar Messages

Maybe you are looking for