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

Similar Messages

  • Dynamic computers collection based on User State Migration associations

    At our company, we have a group of computers with the follwoing situation:
    User works on machine with WindowsXP, there is already prepared new machine, with Windows 7 installed, and delivered to user. I have prepared 2 task sequences - "State Capture" and "State Restore", both deployed to separate device collections.
    Now, what I do is create old/new computer association in the User State Migration tab, add old computer to Capture collection, let the TS complete, add new computer to Restore collection, and let the TS complete. After all these steps user can begin to work
    on the new machine with his/her profile and data migrated.
    But I would like to speed things a little bit, and allow my
    colleagues to perform such "migration" by simply adding computers association. To achieve that, I need to create a query, that would assign computers to collections, based on the existing associations in the User State Migration tab. The problem is,
    I fail to find appropriate rule in query wizard. Is it possible at all?
    I need computer to be added to Capture collection upon detection of it being source computer in the USM tab, and removed from collection upon finished TS, with the target computer added to Restore collection at the same moment and removed from the collection
    upon finished restore TS.
    I would greatly appreciate any help or pointing into right direction.

    Hi,
    There is a blog about removing computer from collection after SCCM task sequence. But it is for SCCM 2007. You could have a look on this blog to see if the script can be edited to meet your requirements.
    Remove computer association from collection
    after SCCM task sequence
    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.

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

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

  • 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

  • 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

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

  • MDT 2012 - Failure 9701: Unable to find any version of USMT, unable to perform user state migration. Failed to run the action Restore User State. DNS Record does not exist. (Error: 000025E5; Source: Windows)

    I am having trouble trying to capture a new Windows 8 image with WDT 2012.
    My Setup - 
    Server 2012
    WDS
    MDT 2012
    Windows 8 ADK
    Hyper-V
    I have created a new task and I can get the image to successfully deploy the image to a VM but it seems to fail at the Restore User State task.
    Once the install Applications task has finished I added a Suspend task so I could customize the image a little. Upon resuming the task sequence is where the above failure message appears. I can see it gets to the next step (which is 'Restore User State')
    but that seems to be where is crashes.
    Does anyone have any advice on what I might be doing wrong or what I can do to resolve the above issue?

    WAIK being installed was probably your issue so I wouldn't bother disabling the restore task. It is used to migrate user data, docs, and settings on refreshes, not new builds. It doesn't affect CopyProfile, just note that data will be migrated on refreshes so
    some aspects may change, ie wallpaper, shortcuts, etc but what gets migrated with USMT can also be configured.
    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. ”

  • User State Migration using SMP with config manager 2012 R2

    Hi , 
    I have SMP at primary site and need to migrate XP and 7 machines using this SMP (using USMT), 
    what are the steps do i need to define in TS so that usmt can use State migration point for user setting\data backup?
    Another challenge i see it with XP since we are deciding to take 2 phase approach, that means we will backup data using 1 TS (3 step TS) and then restore data as part of another TS that will install windows 8.1 also with user state restore. 
    Any pointers if we need to define anything special in TS (migration store etc.) or since its SMP, TS should able to take care of finding it automatically and backup\restore user state? 
    We have MDT based TS, just wondering if we need to define anything inside CS.ini file related to SMP? 
    Any pointers will be appreciated. Thanks
    Regards,

    Hi,
    Please refer to the link below:
    How to migrate user data from Windows XP to Windows 8.1 with System Center 2012 R2 Configuration Manager
    http://blogs.technet.com/b/configmgrteam/archive/2013/09/12/how-to-migrate-user-data-from-win-xp-to-win-8-1-with-system-center-2012-r2-configmgr.aspx
    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.

  • User state migration "Windows XP to Windows 7"

    Hello , 
    I want to migrate the XP computers to Windows 7 without losing data.
    I tried using the migration user state of SCCM 2012 SP 1   but  the sequence task failed in the step of "applying operating system" with the error "0x80070002" !!!!!!!
    Thank you.
    prince

    Hi,
    Here is a video for your reference.
    Migrating from Windows XP to Windows 7
    http://technet.microsoft.com/en-us/windows/migrating-from-windows-xp-to-windows-7.aspx
    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.

  • Adding a domain user to Local Admin Groups using MDT 2012

    I don't know if this will help anyone, but it did me after weeks of searching.  If you are trying to add a domain user or domain groups to the local administrators group using MDT, simply go to the cs.ini and add "SkipAdminAccounts=No". 
    But the administrators accounts page will only appear if you choose to join a domain. 

    Correct, if you were to go into the %DeployRoot%\Scripts\DeployWiz_Definition_ENU.xml file you would see the entry for the DeployWiz_AdminAccounts.xml page as follows:
    <Pane id="AdministratorAccounts" reference="DeployWiz_AdminAccounts.xml">
    <Condition><![CDATA[ UCase(Property("SkipAdminAccounts")) = "NO" and UCase(Property("DeploymentType"))<>"REPLACE" and Property("DeploymentType")<>"CUSTOM" and Property("JoinDomain") <> "" ]]></Condition>
    </Pane>
    Most Wizard Pages are displayed by default, and you can turn them off by using the SkipXxxXxxxxx Page variable to hide them during wizard execution. This page is different, since it was added for MDT 2012, the MDT team decided to leave it *OFF* by default,
    instead you must explicitly turn off the SkipAdminAccounts variable by setting it to "NO".
    Additionally, you would not need to display this page if you were running a Refresh or a Custom Task Sequence.
    Finally, this page does not actually *create* accounts, instead it just adds pre-existing user accounts and adds them to the local Administrators group. This scenario is only valid when you are joining the machine to a domain, so you must Join to the Domain.
    If you are interested in adding other local users to the Administrators Group, you should write a script to create the account(s) and add them to the local group. Windows 8.1 has some *gotchas* that have to do with Microsoft Accounts, but that's a different
    Story :^).
    Keith Garner - keithga.wordpress.com

  • UDI Wizard hides No Data option on User State page in Capture Mode

    Hi,
    as described in the MDT 2013 release notes i configured my UDI wizard config file like this:
    <Setter Property="DataSourceText">Please select a location where user data will be captured.</Setter>
    <Setter Property="Format">enable</Setter>
    <Setter Property="FormatPrompt">enable</Setter>
    <Setter Property="MinimumDriveSize">10</Setter>
    <Setter Property="State">Capture</Setter>
    <Setter Property="NetworkDrive">n:</Setter>
    <Setter Property="DisplayNoDataInCaptureMode">true</Setter>
    I have an SCCM 2012 R2 Environment with MDT 2013 Integration!
    However i can't select a USB or Network drive for USMT capture??
    What else do i need to enable?
    Any suggestions?
    thanks,
    ckuever

    Hi,
    as described in the MDT 2013 release notes i configured my UDI wizard config file like this:
    <Setter Property="DataSourceText">Please select a location where user data will be captured.</Setter>
    <Setter Property="Format">enable</Setter>
    <Setter Property="FormatPrompt">enable</Setter>
    <Setter Property="MinimumDriveSize">10</Setter>
    <Setter Property="State">Capture</Setter>
    <Setter Property="NetworkDrive">n:</Setter>
    <Setter Property="DisplayNoDataInCaptureMode">true</Setter>
    I have an SCCM 2012 R2 Environment with MDT 2013 Integration!
    However i can't select a USB or Network drive for USMT capture??
    What else do i need to enable?
    Any suggestions?
    thanks,
    ckuever

Maybe you are looking for

  • Where do I find MPN on my MBP?

    I'm trying to find the MPN for my MBP (to register iDVD/iLife), but don't see anything under Utilities/System Profiler. Any advice? Also tried looking on my package but can't see any M#####... number. Thanks- MacBook Pro   Mac OS X (10.4.7)  

  • Hide repeating column in table

    I have a table wrapped in a subform which allows the user to add/delete multiple rows, I want to use a button to hide a column in the table once the use has finished adding/deleting rows. I have tried:- xfa.resolveNodes("Tables.Table1.Row[*].deleteBt

  • Automatically assign admin rights in OS X based on Active Directory

    Hi Hello all is write in my question, i want when one users log of Mac book laptop is automatically admin of laptop have you a solution ? Thanks

  • My Lightroom 5.0 serial number is not valid?

    It is listed on the Adobe web page but is not valid says Application Manager?

  • Displaying an opponents screen in a game

    Say I have a two player tetris game which displays both your screen and your opponent's screen. How would I display the opponent's screen? So far my classes are structured so that each player has their own area and their own game. Game1 contains Play