USMT 4 Wrong version error - MDT 2012 update 1

Hi,
we are in process of Migrating XP to windows 7, i have prepared a media using MDT 2012 update 1 and WAIK,
When i started deployment using the DVD i am getting the following error message
" The USMT Files in e:\..\..\x86\USMT4 are the wrong version. failure 9701.
When i checked in the above mentioned path i can see the USMT 4 folder with all required files inside it and i even compared the folder with USMT4 folder of c:\program files\WAIK instllation folder and i did not find any difference between them.
When i tested the deployment from the share folder by accessing (\\itd-mig\deploymentshare$) i was able to migrate without any error.
Can any one help me to find out what is the error about.
Thanks in advance.
D. Sendil Kumar

Ugh...
ValidateCaptureLocation is a function in the Deployment Wizard, the wscript object is *not* available from within the MSHTA environment, so be careful.
Instead of:
wscript.sleep 5000
use this instead:
outility.SafeSleep 5000
Is your DHCP server slow?
Keith Garner - keithga.wordpress.com

Similar Messages

  • MDT 2012 Update 1 Boot Image Creation Fails in SP1

    I have my site server (SCCM 2012 SP1) installed on Server 2012 with the Windows 8 ADK installed (I've also tried installing the Win7 WAIK with no change to the below problem). It is hosting the site server, FSP, AIS, and Endpoint protection roles. I
    installed MDT 2012 Update 1 (build 6.1.2373.0) and installed ConfigMgr integration. I have a share
    \\siteserver\bootimages that I'm creating the boot image to and the system account has full control on both the NTFS and Share permissions. When I create the boot image I get an error almost immediately and
    a popup that the Microsoft.BDD.ElevatedProxy has stopped working. Details from the pop-up:
    Description:
      Stopped working
    Problem signature:
      Problem Event Name: CLR20r3
      Problem Signature 01: microsoft.bdd.elevatedproxy.exe
      Problem Signature 02: 3.0.0.0
      Problem Signature 03: 50400c36
      Problem Signature 04: System.ServiceModel
      Problem Signature 05: 3.0.0.0
      Problem Signature 06: 4fee6b19
      Problem Signature 07: fb9
      Problem Signature 08: a7
      Problem Signature 09: G3DT0URDW53KGT4VJDEEQCRAUIFCNTLL
      OS Version: 6.2.9200.2.0.0.272.7
      Locale ID: 1033
    The error in the boot image creation wizard is:
    Started processing.
    Creating boot image.
    Error while importing Microsoft Deployment Toolkit Task Sequence.
    System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
    configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
    Server stack trace:
       at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at INewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
       at NewBootImageClient.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
       at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
    I haven't found anything online on this particular error, I've seen all the ones about MDT 2012 and ConfigMgr 2012 CU 1. Any ideas? Any logs that may be revealing to the cause of this error? I've tried removing integration components, uninstalling MDT, reboot,
    re-installing, etc, but same problem occurs each time.

    I just tried to create a new boot image again, the DISM.log file does not show any evidence of the attempt to create the boot wim, in fact nothing since 0800 this morning. The most recent logs are as follows:
    2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=4312 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Shutdown SessionTable - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized GlobalConfig - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized SessionTable - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=3672 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 m_pInternalThread started - CCommandThread::Start
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Created g_internalDismSession - DismInitializeInternal
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Shutdown SessionTable - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized GlobalConfig - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized SessionTable - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=1620 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 m_pInternalThread started - CCommandThread::Start
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Created g_internalDismSession - DismInitializeInternal
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Shutdown SessionTable - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-05 08:44:10, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Initialized GlobalConfig - DismInitializeInternal
    2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Initialized SessionTable - DismInitializeInternal
    2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=3140 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 m_pInternalThread started - CCommandThread::Start
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Created g_internalDismSession - DismInitializeInternal
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Shutdown SessionTable - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:                       

  • 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

  • User State Migration Data Capture Failure MDT 2012 Update 1

    Hello All
    Trying to capture data on a Win7 x64 machine so that I can keep the data and restore once the computer is done re-imaging.  This is an offline MDT deployment on the same computer.  See the error below:
    CNAME loop detected. (Error: 000025EB; Source: Windows) 
    Using MDT 2012 Update 1

    Lots of good information out there.  Even stuff that says it's for MDT 2010 also applies to MDT 2012 Update 1 for the most part.  Here's a few to get you started:
    http://deployment.xtremeconsulting.com/2009/11/20/understanding-usmt-with-mdt-2010/
    http://technet.microsoft.com/en-us/magazine/jj127984.aspx
    http://blogs.technet.com/b/mniehaus/archive/2009/07/01/mdt-2010-new-feature-12-usmt-4-0-hardlink-support.aspx
    http://www.windows-noob.com/forums/index.php?/topic/3758-usmt-mdt/
    http://channel9.msdn.com/Events/MMS/2013/DC-B301 (great video with Johan presenting, focused on USMT 5.0)
    You should create a default Standard Client Task Sequence and look at the State Capture and State Restore groups to see what MDT sets up for you by default that you may have removed from your current Task Sequence.  But the direct answer to your question,
    is that ScanState (part of USMT) is the part that creates a backup.  LoadState is the piece that restores it to a machine.
    David Coulter | http://DCtheGeek.blogspot.com |
    @DCtheGeek

  • 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

  • Deployment Failure - thick image - (5627) dism.exe (MDT 2012 Update 1)

    I installed MDT 2012 Update 1 on a new server and was testing it out with our Windows 8 deployment. I captured a thick image which works fine when I boot to Win PE and apply it using dism.
    I imported the image into the the deployment share (custom, no setup/sysprep) and created a Custom Task Sequence with just 3 tasks to do a custom format (command line using dism), apply the image (choose specific disk and partition), and restart the computer.
    However, when I go through the task sequence, it comes up with some errors and appears that it gets sysprepped again because it prompts me to answer questions that weren't a part of my original sysprep (EULA, adding a new user, etc).
    Any idea where I need to look to get this fixed? I've shared the BDD.log and LTIApply.log on my SkyDrive.
    https://skydrive.live.com/?cid=0FB4C394CC7A79E1&id=FB4C394CC7A79E1%21105
    Here's a snip of the results 
    <![CDATA[FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found
    FAILURE ( 5627 ): 2: Run DISM.exe
    Litetouch deployment failed, Return Code = -2147467259  0x80004005
    Failed to run the action: Install Operating System. 
    Unknown error (Error: 000015FB; Source: Unknown)
    Failed to run the action: Install Operating System. Execution has been aborted
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015FB; Source: Unknown)
    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]]>
    Please advise.
    Thanks in advance.

    I installed MDT 2012 Update 1 on a new server and was testing it out with our Windows 8 deployment. I captured a thick image which works fine when I boot to Win PE and apply it using dism.
    I imported the image into the the deployment share (custom, no setup/sysprep) and created a Custom Task Sequence with just 3 tasks to do a custom format (command line using dism), apply the image (choose specific disk and partition), and restart the computer.
    However, when I go through the task sequence, it comes up with some errors and appears that it gets sysprepped again because it prompts me to answer questions that weren't a part of my original sysprep (EULA, adding a new user, etc).
    Any idea where I need to look to get this fixed? I've shared the BDD.log and LTIApply.log on my SkyDrive.
    https://skydrive.live.com/?cid=0FB4C394CC7A79E1&id=FB4C394CC7A79E1%21105
    Here's a snip of the results 
    <![CDATA[FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found
    FAILURE ( 5627 ): 2: Run DISM.exe
    Litetouch deployment failed, Return Code = -2147467259  0x80004005
    Failed to run the action: Install Operating System. 
    Unknown error (Error: 000015FB; Source: Unknown)
    Failed to run the action: Install Operating System. Execution has been aborted
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015FB; Source: Unknown)
    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]]>
    Please advise.
    Thanks in advance.
    Hi Mathew,
    I have the similar error deploying a image (no sysprep) using the standard client task sequence. There are 2 partitions, one 500MB for boot and the other remaining partition is for OS. Do you have solutions to resolve the errors? Greatly appreciate
    any advice given. Thanks.
    Regards,
    Eng Chai
    Eng Chai

  • MDT 2012 Update 1 - Deployment - Auto Login won't Disable

    Hello,
    I am using MDT 2012 Update 1 with an almost vanilla Windows 8.1 and Windows 7 test box. I can deploy both images fine and get a success on my summary but both machines continue to auto login to the Administrator account. To my understanding, the Auto Login
    should be shutoff via the LTIcleanup script. When I double check the script for the reg keys that are added/deleted I can confirm that this is happening but the images still continue to auto login to the admin account.
    Anyone have any ideas?

    Thought I would let those who are interested know. After speaking with Microsoft Premier Support they determined that you must have a password on the Administrator account. If you don't then something goofs up and causes the auto logon issues that I was
    having.

  • Slow Imaging on Lenovo T430 with MDT 2012 Update 1

    I am having an issue where laying down the operating system (Custom WIM, Windows 7 x64 about 3GB in size) to a Lenovo T430 machines using MDT 2012 Update 1 is slow.  The install operating system/applying image, seems to hang around 20%, this process takes anywhere from 10-20 minutes to complete before DISM applies the unattend file.  While the process is “hung” the hard drive light on the laptop is solid, so I assume something is going on but I still do not understand why the process seems to hang.  When I image an older Lenovo T410 laptop the WIM is layed down in about in about 5 minutes.  So it seems strange to me that a new laptop model would be slower.  I added new network card drivers and storage device drivers to out of box drivers and updated my deployment share.  I am currently using a lite touch deployment, so I extracted the ISO to a bootable USB stick.
    I thought this was a driver issue but I am not sure now. Anyone else see anything like this? Below is a screenshot of the process I am talking about, although like I said above, it seems to hang around 20% or so.
    Link to picture
    Moderator note; picture(s) totalling >50K converted to link(s) Forum Rules

    I'm experiencing the same issue with our latest batch of T430s laptops, using SCCM 2007 to deploy a custom WIN7SP1 x64 image:
    With the 1st shipment of T430s' we received (Type: 2355-CE8), our image deploys to a system in 31 minutes total. The WIM download + apply stage with this model takes 7 minutes during the deployment.
    With the 2nd shipment of T430s' we received (Type: 2355-2G8), our image deploys to a system in 97 minutes total. The WIM download + apply stage with this model takes 72 minutes during the deployment.
    Aside from an additional stick of memory and a backlit keyboard, these two shipments should've been identical. A quick device manager comparison of the two types shows only one major difference: the Type 2355-CE8 systems use a Micron SSD (C400-MTFDDAK128MAM) where as the Type 2355-2G8 use a Toshiba SSD (THNSNF128GCSS).
    If I swap the Micron SSD (from a Type 2355-CE8 system) into one of the Type 2355-2G8 systems and re-image it, deployment now takes 33 minutes total, and the WIM + download stage takes 8 minutes during the deployment.
    A 2-3 minute difference (total deployment time) is acceptable, but a 60+ minute difference is not.

  • 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.

  • Process version 2010 to 2012 update differences...why?

    I am a retired computer professional and I have used LR since V3 first came out and have recently updated my photos from process version 2010 to PV2012.  I used the batch process as I have ~200 GB of photos. My batch process is as follows:
    In the Library module, I clicked on > Library> select Show Photos in Subfolders. I then selected the Develop module, opened a folder and selected the first photo and manually clicked on the ! icon to Update to Current Process (2012).  I then added all the photos in the filmstrip to my selection.  I then clicked on Sync button to open the Synchronize Settings dialog and clicked on Check None and then check marked only Process Version and clicked on Synchronize.
    I noticed that the batch process zeroed out all my settings in the Develop module Basic dialog.  I no longer have my previous 2010 settings listed for the photo and in some cases it looks like some of the images have defaulted to an unprocessed state (under or overexposed, lack of color saturation).  If  I select a photo in the Develop module and go History and select the setting just prior to the "Synchronize Settings"  to render it back to PV2010 and click on the image ! icon to update just that one photo, I get a totally different result.  I retain the previous settings in the Basic tab and only the new LR4 tool settings are changed.and the History then states "Update to Current Process (2012)".
    1.  Why the different labeled result in History for the two processes? 
    2.  Why are completely different results achieved in Develop module between the batch vs the manual update processes?
    3.  Have the photos really been updated from process version 2010 to PV2012 using the batch process listed above?  As far as I know, I did the batch process correctly, as I even double checked online prior to processing in batch.
    4.  Can the images be "batched" back to PV2010?   Would they change the photos that have been added since acquiring LR4 that are in PV2012?  I can load last weeks backup PV2010 LR4 catalog, but I have added new photos since then and it would be a hassle to process them over again.
    I am NOT happy with the results of my process update due to the loss of  Develop Module Basic settings and in the completely different results achieved between the batch vs the manual update processes.  I would like to keep my old settings that are not impacted by the PV2012 change and now they are gone in my current catalog. 
    Adobe, is this a BUG or a FEATURE?

    In my opinion: not a good idea to convert old photos en-batch.
    Recommend: convert (hand-selected photos) one at a time, or just use PV2012 on new photos.
    There are more than one reason:
    * As you know, process conversion yields very different results (if photo has been substantially edited).
    * It takes some time to polish your PV2012 editing skills.
    * Often when you are comparing PV2012 results to previous PV2010 results (which you've become familiar with, and like...), you may interpret differences in a more negative light, than if you were using PV2012 without comparing to a previous PV2010 version.
    This last one can not be over-stated. Numerous times I have converted and been disappointed, at least initially. Recovered highlights can seem like loss of contrast. Detail in shadows can be distracting after initial conversion, until you step back for a while, then re-look at it...
    Also, the process version itself (results I mean) takes some getting used to (even when not comparing to a previous legacy-pv edit). e.g. if you've become attached to the over-saturated shadows in previous process version, the shadows seem under-saturated in PV2012, etc...
    Rob

  • 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.

  • SCCM 2007 with MDT 2012 Update 1 - LTI Build Process - "UserLocale" setting is all lowercase.

    Greetings all.  I'm trying to resolve a situation where the "UserLocale" property is being set to "en-us" opposed to "en-US".  Quick environment stats:  SCCM 2007, MDT2010, using LTI build process with a 
    custom UDI.  2 Build Sites (customer build sites), both sites have branch distribution points.
    Both sites are performing the exact same LTI builds.  Same task sequence. 
    Both sites have MDT location records that have the "UserLocale" property defined as "en-US".
    Both sites successfully build the same LTI build, but post build; Site A has correct UserLocale entry of "en-US", while Site B does not have correct UserLocale entry - it is set to "en-us".   This wouldn't normally be a big
    deal, however we have an enterprise application that is hard coded to look for case specific property of "en-US", so this application does not function as desired as Site B.
    Both builds use the same task sequence, same OS.WIM (Windows 7 x86), and same unattend.xml.  The unattend.xml does have UserLocale specified as "en-US" (and also the MDT location records for Site A and Site B both have "UserLocale"
    property defined as "en-US", so I do not understand where the lowercase "en-us" is being populated from during the client build for Site B, when it works correctly for Site A?
    Bdd.log for client build at Site A shows:
    Obtained USERLOCALE value from SQL:  USERLOCALE = en-USUpdated
    C:\WINDOWS\panther\unattend\unattend.xml with UserLocale=en-US (value was en-US)
    Property USERLOCALE is now = en-US
    Bdd.log for client build at Site B shows:
    Obtained USERLOCALE value from SQL:  USERLOCALE = en-US
    Property UserLocale_Edit is now = en-us;0409
    Property UserLocale is now = en-us
    Value for USERLOCALE is already set to en-us so database value of en-US will be ignored.
    Updated C:\WINDOWS\panther\unattend\unattend.xml with UserLocale=en-us (value was en-US)
    Value for USERLOCALE is already set to en-us so database value of en-US will be ignored.
    Can anyone offer insight as to my next troubleshooting steps? I'm not sure why Site B, bdd.log - unattend.xml shows updating UserLocale to en-us instead of en-US?
    (Please note I have verified that the OS.WIM, unattend.xml, and all MDT scripts that run during task sequence execution are exact matches on the BDP's for each site. Same size, date, and content)

    Well, there must be something that is different... If you zip up the logs (all of them) from each setup, and mail them to me, I can take a quick look.
    / Johan
    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

  • MDT 2012 - Update Deploymentshare: Unable to open the specified WIM file

    Hi @ all
    wie have updated our Litetouch boot image using DISM and know we try to update the deploymentshare but we get the following error.  
    === Making sure the deployment share has the latest x86 tools ===
    === Processing LiteTouchPE (x86) boot image ===
    Building requested boot image profile.
    System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
       --- End of inner exception stack trace ---
       at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
       at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
       at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()
       --- End of inner exception stack trace ---
       at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
       at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
       at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
    Unable to open the specified WIM file? The image ist is stil in the boot folder.
    Anybody an idea or an solution for that problem?
    Thank's
    Adrian

    I had installed ADK to utilize the latest and greatest DISM tool. That broke WAIK and the boot.wim could not be found when updating the deployment shares. Thanks for the pointer...
    Paul Prindle MCP, A+
    That is because WAIK and ADK are unsupported as side-by-side installations.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    How to ask a question that is fixable.

  • Mdt 2012 update

    if I have aik and adk installed on same computer does mdt use winpe.wim from adk or aik . I am trying to create a lite touch to install windows 8.1 both winpe.wim from adk and install. wim from windows 8.1 are the same version any ideas I have a feeling
    that mdt is using aik winpe.wim which I don't want

    Hi,
    We can check whether the current version of PE is from ADK or AIK.
    Once boot into Lite touch, and Exit to command prompt, type Regedit to open registry editor, locate to
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinPE.
    If the version is 5.0 / 5.1, we can be sure that it's using PE from ADK.
    If the PE is from AIK, the version should be 4.0.
    Kate Li
    TechNet Community Support

  • Best Practice: Working with Win7 32Bit & 64Bit Versions in MDT 2012

    Whats the recommended way for producing bootable media using MDT2012 that would support 32 and 64 bit versions of Windows 7?
    Should I have 2 deployment shares or do I import the 2 operating systems source dvd's into the same deployment share?
    is it possible to create 32 & 64Bit bootable media from 1 deployment share and if so what settings would I need to modify in the task sequence & advanced configs to allow me to do so?

    No problemt to run both x86 and x64 in the same deploymentshare.
    Yes you can create both 32 and 64 bits boot media (winpe) in one deployment share.
    In the properties of you deploymentshare, general tab you choose if you want to support both x86 & x64.

Maybe you are looking for