Hi I am currently part of a team deploying windows 7 to lenovo laptops. We are experiencing issues with deploying to a specific model the T410i laptop. A pink screen appears saying Operating system deployment did not complete successfully. 11 errors and 3 warnings were reported. We are using a desktop PC with windows 7 as a deployment server as it needs to be portable for use at satellite sites.

The odd thing is this doesn't effect all T410i laptops many build without an issue. At our most recent rollout we found 17 machines refused to take the image. So far we cannot image these machines. I believe one engineer said they had had sucess by removing the DVD drive and battery but haven't tested this yet I'm about to. We have tried the following.

1. Clean with diskpart and retry - no effect

2. Different SSD - no effect

3. Different deployment server - no effect.

4. Memory sticks instead of CD's - helps with some machines but not these 17

This is a sample of the BDD.log from the machine in question. Does anyone have any ideas? This is a little over my head if I'm honest.

<![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="04:42:03.000+000" date="03-10-2015" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">

<![LOG[Validating connection to \\DTV0022485\Events$]LOG]!><time="04:42:03.000+000" date="03-10-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

<![LOG[Already connected to server DTV0022485]LOG]!><time="04:42:04.000+000" date="03-10-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

<![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="04:42:04.000+000" date="03-10-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

<![LOG[Error executing web service http://DTV0022485:9800/MDTMonitorEvent/PostEvent?uniqueID=&computerName=MC7V0022153&messageID=41014&severity=3&stepName=&currentStep=0&totalSteps=0&id=016410A4-8C51-CB11-BE21-E3F6BC6D2E61,F0:DE:F1:63:7C:4C&message=Litetouch deployment failed, Return Code = -2147467259  0x80004005&dartIP=&dartPort=&dartTicket=&vmHost=&vmName=: The operation timed out

I can get more logs if needed!

Many thanks if anyone can offer any suggestions we are fresh out.

I cannot deploy a captured image using wdt deployment share using lti method.

error 5640 says The network path was not found.

The path is real and accessible ----------------  net use K: \'\wds-rpm\reminst\

I have a copy of the log file.

What could be the issue here?????????????????

#server 2012r2 #mdt 2012 #adk 8.0 #win 8.1   

###########################################################################

<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="08:08:34.213+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="instruction.cxx:2957"><![LOG[Expand a string: WinPEandFullOS]LOG]!><time="08:08:34.213+000" date="03-12-2015" component="TSManager" context="" type="0" thread="1588" file="executionenv.cxx:782"><![LOG[Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"]LOG]!><time="08:08:34.213+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="commandline.cpp:805"><![LOG[Process completed with exit code 5640]LOG]!><time="08:09:49.687+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="commandline.cpp:1102"><![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="08:09:49.687+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="instruction.cxx:3010"><![LOG[Failed to run the action: Install Operating System.
Unknown error (Error: 00001608; Source: Unknown)]LOG]!><time="08:09:49.701+000" date="03-12-2015" component="TSManager" context="" type="3" thread="1588" file="instruction.cxx:3101"><![LOG[Sending status message . . .]LOG]!><time="08:09:49.701+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="utility.cxx:292"><![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="08:09:49.701+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="utility.cxx:302"><![LOG[Set a global environment variable _SMSTSLastActionRetCode=5640]LOG]!><time="08:09:49.701+000" date="03-12-2015" component="TSManager" context="" type="0" thread="1588" file="executionenv.cxx:668">

###########################################################################

I am using mdt 2013 to deploy images. I have a separate share for windows 7 images and windows 8 images. Everything works perfectly. I decided that I want to combine my images on one share so that we do not have to use separate usb boot keys. I added our one windows 8.1 image onto the windows 7 share and it fails. Giving me a 5627 error message. Everything is identical between the two shares and the task sequences. I have log files if anyone can understand them

When attempting to inject new network driver; DISM keep error out with the 0xc0000135 error. The log file content is below.

Please help or point me to the right direction. Thank you very much.

2015-03-10 10:47:07, Info                  DISM   PID=10296 Scratch directory set to 'C:\Users\name\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2015-03-10 10:47:07, Info                  DISM   PID=10296 Successfully loaded the ImageSession at "C:\Program Files\Windows AIK\Tools\AMD64\Servicing" - CDISMManager::LoadImageSession
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Manager: PID=10296 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: 
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: 
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=2
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: Executing command line: DISM  /Unmount-wim /MountDir:D:\imaging\mount /commit
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2015-03-10 10:47:07, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Getting Provider WimManager - CDISMProviderStore::GetProvider
2015-03-10 10:47:07, Info                  DISM   DISM Provider Store: PID=10296 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:47:30, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2015-03-10 10:47:30, Info                  DISM   DISM.EXE: 
2015-03-10 10:47:30, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2015-03-10 10:47:30, Info                  DISM   DISM.EXE: 
2015-03-10 10:47:30, Info                  DISM   DISM Image Session: PID=10296 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2015-03-10 10:47:30, Info                  DISM   DISM Provider Store: PID=10296 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:47:30, Info                  DISM   DISM Provider Store: PID=10296 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:47:30, Info                  DISM   DISM Provider Store: PID=10296 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-03-10 10:47:30, Info                  DISM   DISM Provider Store: PID=10296 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:47:30, Info                  DISM   DISM Provider Store: PID=10296 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:52:36, Info                  DISM   PID=9888 Scratch directory set to 'C:\Users\name\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2015-03-10 10:52:36, Info                  DISM   PID=9888 Successfully loaded the ImageSession at "C:\Program Files\Windows AIK\Tools\AMD64\Servicing" - CDISMManager::LoadImageSession
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Manager: PID=9888 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: 
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: 
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=2
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: Executing command line: DISM  /Mount-WIM /WimFile:D:\Imaging\boot.wim /index:1 /MountDir:D:\Imaging\Mount
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2015-03-10 10:52:36, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Getting Provider WimManager - CDISMProviderStore::GetProvider
2015-03-10 10:52:36, Info                  DISM   DISM Provider Store: PID=9888 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:52:59, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2015-03-10 10:52:59, Info                  DISM   DISM.EXE: 
2015-03-10 10:52:59, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2015-03-10 10:52:59, Info                  DISM   DISM.EXE: 
2015-03-10 10:52:59, Info                  DISM   DISM Image Session: PID=9888 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2015-03-10 10:52:59, Info                  DISM   DISM Provider Store: PID=9888 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:52:59, Info                  DISM   DISM Provider Store: PID=9888 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:52:59, Info                  DISM   DISM Provider Store: PID=9888 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-03-10 10:52:59, Info                  DISM   DISM Provider Store: PID=9888 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:52:59, Info                  DISM   DISM Provider Store: PID=9888 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:53:08, Info                  DISM   PID=8968 Scratch directory set to 'C:\Users\name\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
2015-03-10 10:53:08, Info                  DISM   PID=8968 Successfully loaded the ImageSession at "C:\Program Files\Windows AIK\Tools\AMD64\Servicing" - CDISMManager::LoadImageSession
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Manager: PID=8968 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: 
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: 
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.1.7601, Running architecture=amd64, Number of processors=2
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: Executing command line: DISM  /image:d:\imaging\mount /Add-Driver /driver:d:\imaging\driver\ /recurse
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2015-03-10 10:53:08, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2015-03-10 10:53:08, Info                  DISM   DISM Provider Store: PID=8968 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2015-03-10 10:54:10, Error                 DISM   DismHostLib: Failed to create DismHostManager remote object. Checking for dismhost.exe exit code.
2015-03-10 10:54:10, Info                  DISM   DismHostLib: Found dismhost.exe exit code.
2015-03-10 10:54:10, Error                 DISM   DISM Manager: PID=8968 Failed to create Dism Image Session in host. - CDISMManager::LoadImageSession(hr:0xc0000135)
2015-03-10 10:54:10, Warning               DISM   DISM Manager: PID=8968 A problem ocurred loading the image session. Retrying...  - CDISMManager::CreateImageSession(hr:0xc0000135)
2015-03-10 10:55:10, Error                 DISM   DismHostLib: Failed to create DismHostManager remote object. Checking for dismhost.exe exit code.
2015-03-10 10:55:10, Info                  DISM   DismHostLib: Found dismhost.exe exit code.
2015-03-10 10:55:10, Error                 DISM   DISM Manager: PID=8968 Failed to create Dism Image Session in host. - CDISMManager::LoadImageSession(hr:0xc0000135)
2015-03-10 10:55:10, Error                 DISM   DISM Manager: PID=8968 Failed to load the image session from the temporary location: C:\Users\name\AppData\Local\Temp\F22DD0AC-FE11-445F-BD1D-5E5D9173F94A - CDISMManager::CreateImageSession(hr:0xc0000135)
2015-03-10 10:55:10, Error                 DISM   DISM.EXE: Could not load the image session. HRESULT=C0000135
2015-03-10 10:55:10, Error                 DISM   DISM.EXE: Unable to start the servicing process for the image at 'd:\imaging\mount'. HRESULT=C0000135
2015-03-10 10:55:10, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2015-03-10 10:55:10, Info                  DISM   DISM.EXE: 
2015-03-10 10:55:10, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2015-03-10 10:55:10, Info                  DISM   DISM.EXE: 
2015-03-10 10:55:10, Info                  DISM   DISM Image Session: PID=8968 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2015-03-10 10:55:10, Info                  DISM   DISM Provider Store: PID=8968 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:55:10, Info                  DISM   DISM Provider Store: PID=8968 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:55:10, Info                  DISM   DISM Provider Store: PID=8968 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-03-10 10:55:10, Info                  DISM   DISM Provider Store: PID=8968 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-03-10 10:55:10, Info                  DISM   DISM Provider Store: PID=8968 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

Hi guys,

I'm trying to deploy to a UEFI enabled server but am running into a problem.

The deployment kicks off fine, the disk is formatted and the correct UEFI partitions appear, the operating system image gets applied, then I get into the post install phase, everything goes through up until the restart computer step.

The sequence hangs for a little while then flags up an error stating that it was unable to check the reboot status, and I get an access denied 80004005 message.

if I then restart that computer, and re-run through the deployment it all goes through fine.

When I first boot the computer from out of the box, there are no disks detected as they are attached to an array, I run a utility to configure the array and the disk appears and is found and formatted by the format disk step.

Does any have any ideas?

I am relatively new to MDT, but I can't figure this out. I have followed the instructions by Mitch Tulloch (http://www.windowsnetworking.com/articles_tutorials/Deploying-Windows-7-Part7.html) and when I boot off my CD, I still get prompted to start the process and then prompted for my credentials...

Here is my CustomSettings.ini file:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipAdminPassword=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipCapture=YES
SkipComputerName=YES
SkipComputerBackup=YES
SkipDeploymentType=YES
DeploymentType=NEWCOMPUTER
SkipDomainMembership=YES
JoinDomain=MYDOMAIN
DomainAdmin=MYID
DomainAdminDomain=MYDOMAIN
DomainAdminPassword=MYPW
SkipFinalSummary=YES
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
SkipPackageDisplay=YES
SkipProductKey=YES
SkipSummary=YES
SkipTaskSequence=YES
TaskSequenceID=OPTIPLEX780-W7
SkipTimeZone=YES
TimeZoneName=Central Standard Time
SkipUserData=YES

Here is my Bootstrap.ini file:

[Settings]
Priority=Default

[Default]
DeployRoot=\\MYPC\OptiPlex780-Win7-64bit$

UserID=MYID
USerDomain=MYDOMAIN
UserPassword=MYPW

KeyboardLocale=en-US

SkipBDDWelcome=YES

I am having trouble getting my UNC deployment to run the State Restore phase. I am operating on a network without DHCP and have successfully connected to the network share and ran the Task Sequence. After the reboot, however, the static ip doesn't get set and the deployment can't continue.

Upon inspection of the BDD.log I ran across the entry in the State Restore section that pertains to setting the static ip.

WMI Function: Adapter.EnableStatic(IPAddress,SubnetMask) FAILURE: -2147217405 Unknown Error: -2147217405

If I log in and run the LiteTouch.wsf file as an administrator, the task sequence starts running again and the static ip gets applied.

Why is this not happening automatically?

I have created and captured a custom image of Windows 8 using MDT2012 update 1 and Windows ADK (without SCCM). In the image, I have set an account called DeployUser, with password XXX, adding it to the Administrators group, and I have disabled the User Account Control.
I did this because the Administrator account is renamed from GPO and the password is changed every 30 days (for security reasons, the password is not disclosed to any IT support).
Next, I created a TS to deploy this image, adding the installation of some software.
In the Unattend.xml, I also added DeployUser to perform the autologon.
After the first logon with DeployUser, the TS stops and does not return any error message.
If I manually run C: \ ProgramData \ Microsoft \ Windows \ Start Menu \ Programs \ Start-up \ LiteTouch.lnk nothing happens, however, if I run it with "Run as Administrator", the TS continues normally.

Somebody who knows a solution for this?

I have a 64-Bit Win7 wim file that I captured from a hyper v vm using MDT2013. When I apply the wim to a machine using a different deployment share I am getting the error "Litetouch deployment failed, Return Code = -2147467259  0x80004005". In the BDD log the error shows up right after my applications have finished installing. The logs say that the applications installed successfully and do not indicate any errors.

However, if I deploy just the wim with no applications, I dont get the lite touch deployment failed error. So my problem seems to be that one of my applications is causing the error but the logs dont show which one. I wanted to see if there is an easier way to find the cause, rather than going through the deployment 15 times for each of my applications?

Thank you.

Hello everyone,

So I'm currently using MDT 2013 to successfully push my images to all of my machines. However I have a big desktop upgrade coming up and need to prepare 100 machines (all same model, same configuration). I would like to image one machine and sysprep it so that I can duplicate the hdd on our duplicator machine.

I'm having a problem with the unattend file for this master hdd. I created a new unattend file using SIM for a few basic setup items and applied it during the sysprep.

After sysprepping when the machine boots up I got stuck at "setup is installing devices" screen, even though I know that the only drivers on the image are from MDT and specific to this model of PC. I modified the generalize phase of my unattend file to leave the drivers in place during the sysprep process.

However, I seem to still be getting errors in my file during the specialize phase and I cant figure it out. I will be posting my error logs and unattend file here shortly. 

Hi, I am using MDT 2013 and deploying Windows 8.1. I understand from that the format and partition step in the task sequence will create necessary partitions based upon detection of UEFI or BIOS mode on the hardware. However, i am not sure if a recovery partition is mandatory for Windows 8.1. I don't need any additional partitions other than EFI and OS. However, after deployment a recovery partition is always created. Please help me understand why is it created and how can i have task sequence not create thsi partition. I have unchecked create extra active partition option in format and partition step as well.

I recently purchased 3 new Surface Pro 3s and I built a separate deployment just for them (according to the TechNet How-To).

The first 2 Surfaces imaged and deployed without issue.  All Apps, Drivers and Metro App tiles work without any issues or glitches.  The third device (I imaged them all one at a time to make sure I did not destroy all 3 at once) took the image and loaded all the apps from the deployment, HOWEVER, once the device was joined to the domain the Tiles (Metro tiles for apps and programs) all fail except the Desktop.  They all have an "X" in the lower right hand corner, including the Store tile.  I have read through many articles and how-tos, but most of them require getting into the Store and changing some settings.  I cannot get into the store or even the "Change PC Settings" from the swipe of the right hand side.

Naturally I chalked this up to an issue with the image push and tried again, and again and again.  No matter what I do, change, skip, regedit, whatever, I always have the Dead Tiles once the machine is joined to the domain.  At one point I was blaming it on the user's profile and imaged a standard laptop and logged in as that user.  No issues.  I logged onto an existing machine with that user's credentials.  No problem again.  I tried logging into the Surface Pro with 4 different users of different authentication and logon scripts. NONE of them where able to access the Tiles.

I am at a loss and need this machine deployed or I will be forced to scrap the test program.

Hi, all!

I'm trying associate .tiff file against MODI 2007.

So, I've prepared reference .xml with associations with Dism /online

After that I've imported that xml to PC with Dism /online, dism says that operation completed correctly

Dism /online /get-defaultappassociation shows me that .tiff associated against MODI

But, nothing happens, tiff opens with photo vierwer

If I export xml from that PC it shows that .tiff associated against photo vierwer

What;s the problem? Does anybody know?

When MDT generates boot ISOs, it gives them a volume label of "DVD_ROM." Is there any way to get MDT to set a better label, like "Lite Touch x64" for that ISO?

I am using MDT to deploy Windows 7 x64 from a USB flash drive. After installing Microsoft .Net Framework 4.5 an error comes up with the Title of "Media Not Found" and "Please reinsert the media (CD, DVD, or USB needed to complete the deployment." Ironically, there is another window just behind that one stating that the media is available. (title "AutoPlay")

If I press the OK button in the first window, MDT continues.  If I don't press it in time, the computer sleeps.

I have tried adding a reboot right after installing Microsoft .Net Framework 4.5 but the problem still persists.

I will need this deployment to build over 700 workstations, so avoiding this hick up would save a lot of headache and time.Does anyone have any ideas?

Hi,

I'm trying to capture an image from a Windows 7 computer. The computer is not a member of the domain, as it is recommended per sysprep, but the MDT server is a member. I am asked several times for credentials in connecting to the deployment share. Once I run LiteTouch.vbs from the share and the PC reboots, I am asked again for credentials, and I provide the correct ones, yet the process cannot connect to the deployment share. My bootstrap.ini file is default with no user credentials saved (I can't save a domain account password in plain text on a server, house rules). The network is good. Where else can I troubleshoot?

Thanks

---

Jason Watkins MCSE, MCSA, MCDBA, CCNA

Hello,

I have a situation where I am receiving an "Unable to find LiteTouch.wsf needed to continue the deployment" when deploying an operating system from an external USB drive on an laptop (Dell Ultrabook - XPS 13 9343 specifically) that uses USB 3.0 ports exclusively.

Some Observations:

• After the OS is installed and the Windows desktop first appears, a Notification appears stating that it's "Installing device driver software". Clicking on the notification reveals that it installed the USB Host Controller but requires a Restart. As a result the external USB drive is never installed and assigned a drive letter.
• Rebooting the machine detects the USB drive and allows you to launch LiteTouch.wsf, but it then continuously complains about a dirty environment because the task sequence never successfully launched the first time.
• To compound the problem, the USB drive can take up to 40 seconds to be detected and assigned drive letter when the windows desktop appears after a task sequence initiated reboot. Litetouch.wfs has already been triggered by the Startup folder well before this.

Some Background:

• All required drivers are in USB Drive that is rendered by MDT
• This same USB solution works fine on an older Ultrabook when we use it's USB 2.0 port. The problem with the latest Ultrabook is that all of its USB ports are 3.0.

Has anyone else encountered this?

Is there a way to ensure that the USB is installed and available the very first time Windows launches and prior to LiteTouch.wfs being triggered?

Could the performance of Windows running on an SSD drive cause latency on detecting the USB drive?

I appreciate any feedback!

Rob

I'm trying apply offline patches to a Windows 7 WIM I created in September.  But after applying several patches and deploying to a test machine, Windows Update shows itstill needs the same set of patches I applied offline.

Ten-Thousand Foot Patching Overview:

1. Image machine
2. Determine necessary patches
3. Acquire patches from catalog.update.microsoft.com
4. Place all msu's in the same directory
5. Mount WIM & patch, pointing to the directory above
6. Commit, unmount & commit
7. Import WIM into MDT
8. Update OSD Task Sequence to use updated WIM
9. Image a test workstation using the updated Task Sequence which is laying down the updated WIM.
10. Run Windows Update
11. The unchecked & highlighted updates in the image below (also on my OneDrive here:http://1drv.ms/1Jdu6DT) are the updates I applied offline, yet are still required:
    
    

Please check my OneDrive here http://1drv.ms/1ulS2yh for just about everything you might want to review:

• Detailed patching process (in a text document): http://1drv.ms/1BFBR5i
• Logs of *every* DISM operation: http://1drv.ms/1ulS2yh
• Redirected output (stdout & stderr) of *every* DISM operation: http://1drv.ms/1ulS2yh
• CBS.LOG and WindowsUpdate.log after OSD (but before actually installing the same updates): http://1drv.ms/1ulS2yh
• Deployment logs are available upon request.
• DISM version is 6.3.9600.17031
• WIM patched on a Windows 8.1 Enterprise laptop

I'm using a VirtualBox VM to pilot some changes and I've run into an unusual problem that only seems to affect VirtualBox VM's.  Other machines (VMware VM's, Hyper-V VM's and physical) work fine no matter which setting for the Install OS step.

I discovered that the Install OS step in the TS was set to 'Specific disk and partition Disk 0 Partition 1', for whatever reason, and didn't change it because things were working.  (This is a new organization)  When its setup like this, the VirtualBox VM fails with "Failure ( 5456 ): Unable to determine Destination Disk, Partition and/or Drive. See BDD.LOG for more information."  In the BDD, right above that line it says "DestinationDisk and Partition did not yield a target Partition."

Curious, when I check `diskpart > lis dis` it says "There are no fixed disks to show."  I double checked the VM config & tried again.  As soon as I was in PE I checked diskpart and it shows disk 0 with 45GB free.  Good. Select the TS, it begins then fails again with the same error.  I go back into diskpart and the disk is missing. ??

I change the Install Os step to 'Logical drive letter stored in a variable', set the variable to 'OSDisk'.  I then checked the properties of the Partition under 'Format and Partition' and manually entered 'OSDisk' as the variable since the field was empty.  The rest of the properties look normal: Primary partition, 100%, make this a boot partition, NTFS file system, quick format.


One more try: Boot the VM, check the disks (OK), select the TS stalls on 'Format and Partition Disk Preparing Disk 0 Partitions ...'.  I open BDD and I see several lines that read "Waiting for Drive to Exist: X%"  Finally it fails with "ZTI ERROR - Unhandled error returned by ZTIDiskpart: Object Required (424)".  I check the disks again and its missing.  What the heck?

I created a brand new standard client TS, made zero customizations to it, & tried both the WIM we're deploying and a stock Win7 WIM but they both fail with the Object required error. 

Hi

I have diskpart script in preinstallation task sequence

SELECT disk 0
SELECT partition 1
FORMAT FS=NTFS LABEL="System" QUICK
EXIT

And I have "Install Operating System" step configured to install OS on first disk and first partition.

Everything works great, but there are some old WinXP computers that have OS files on disk C: and boot files on disk D:

So, the second partition has boot files and is being active. MDT wizard wiped out this partition and installed OS there. Why?
How to prevent it?