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

Similar Messages

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

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:

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.

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

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.

Trying to update my iPad 2 to iOS 5 but it keeps failing.

I have been trying to update my iPad 2 to iOS 5 but it keeps coming up with "The iPad could not be restored. An unknow error occurred (-1)". I've been trying since Thursday but still no joy. I've tried doing it through two different PCs as well. My iPad just tells me that it needs to connect to iTunes. I updated my iPhone software with out any issues.
I went into my local iStore but they wanted £12.00 just to restore it. I was advised that they would do it for free in an Apple Store so I'm guessing that I'll have to pop into one in London during the week.
Is anyone else having these problems / been able to resolve it?

Are you trying to update via wifi or connected to your computer?
 Cheers, Tom

I am trying to update the itunes software on my Mac but I keep getting an instalation alert saying please close itunes. It is already closed, the only option then left is to quit instalation. I want the update though. . .

I am trying to update the itunes software on my Mac but I keep getting an instalation alert saying please close itunes. It is already closed, the only option then left is to quit instalation. I want the update though. Can anyone help?

Click on iTunes and do comand Q. Be sure you are quitting iTunes to finish update and not just closing the screen.

I'm trying to update my apps on my iphone 4s, but it keeps telling me to tap continue and view billing information, what do I do?

I'm trying to update my apps on my iphone 4s, but it keeps telling me to tap continue and view billing information, what do I do?

Sounds like the credit card you have on file is probably invalid/expired. You'd need to correct that or set the payment method to None.

SCCM 2012 R2: Build and Capture - Windows 8.1 prompting for network

I have upgraded my SCCM 2012 SP1 (CU2) to SCCM 2012 R2 and I am attempting to Build and Capture Windows 8.1 Enterprise. Everything is perfect except for the OS prompting for a network selection during the process, if I click "next" on that screen
the Capture finishes without incident. The same is true of the Deploy as well...
Is this a bug from my upgrade?
Portland Public Schools / Systems Administrator II

Hi LillonelC
Can you point out how and where to do this?
When capturing with MDT 2013 on VMware I do not see this, naturaly, since the "machine" only has one network adapter.
But when deploying to a Laptop I get the wireless Setup screen...
On beforehand Thank You!
With kind regards
We aren't using MDT but what we did was create a package called Windows 8.1 - Compnents. In it placed a file named "32Bit-Unattend.xml" and 1 named "64Bit-Unattend.xml".
During the capture in the "Apply Operating System Image" I put a check in the box "Use an unattended or Sysprep answer file for a custom installation". The package was Windows 8.1 - Compnents the File name was "32Bit-Unattend.xml".
I did the same for 64-bit and used the 64-bit version.
Here is content of the 32-bit file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
</OOBE>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x86/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Here is the content of the 64-bit file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
</OOBE>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://SERVERNAME/e$/osimages/win_8.1_x64/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
If that doesn't help I can try to clarify it a bit further.
PS You won't need to do this for the deploy, only the capture.
Portland Public Schools / Systems Administrator II

Windows 7PC no longer detects iPad 3 after latest itunes update. Why?, Windows 7PC no longer detects iPad 3 after latest itunes update. Why?

Windows 7PC no longer detects iPad 3 after latest itunes update. Why?,

iPad not appearing in iTunes
http://www.apple.com/support/ipad/assistant/itunes/
iOS: Device not recognized in iTunes for Mac OS X
http://support.apple.com/kb/TS1591
iOS: Device not recognized in iTunes for Windows
http://support.apple.com/kb/TS1538
iTunes for Windows: Device Sync Tests
http://support.apple.com/kb/HT4235
IOS: Syncing with iTunes
http://support.apple.com/kb/HT1386
Apple - Support - iPad - Syncing
http://www.apple.com/support/ipad/syncing/
 Cheers, Tom

Update an email address in Address Book but Mail Keeps seeing old addresses

Hi,
Trying to figure out why I update an email address in Address Book but when I go to email this person 2 of their old email addresses still show up in the list. I thought Mail accessed Address Book only? I can't find a update sync or anything...any help?
Txs

I went to the window menu-previous recipients and deleted obsolete addresses. When I address an email to one of the people where I deleted an old address, it still comes up. I quit Mail and reopened it thinking that it needed to do that before it worked, but that didn't do it. When I open the previous recipients list, the email addresses that I deleted are gone so there's no way to delete them again. Is there another way to do this? The addresses have also been deleted from my address book, so it's not getting them from there.
null

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

Similar Messages

Maybe you are looking for