Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all articles
Browse latest Browse all 11297

Dirty Environment Detected MDT In-Place Update to Windows 10

$
0
0

Hi Guys,

I am running an in place upgrade task sequence on MDT 2013 Update 2 from windows 7 to windows 10.  95% of the workstations complete successfully with about 5% (so far) failing to complete.  When the devices that are getting stuck reboot I experience the dirty environment prompt, which from most of my research appears to be due to an unexpected reboot.  I am not installing any applications which would trigger such a reboot, I am however running the pre and post application windows update tasks which installs windows patches and drivers that have been posted to windows update for the device. I am thinking this may be due to the multiple driver updates taking place after the upgrade though I am unable to identify why (As this is all handled through windows update, I am not injecting any drivers loaded into MDT).  Any ideas here? I do notice on the devices failing I am receiving the following errors in the BDD.log which I am not receiving on the successful devices.

FAILURE (Err): -2147024770  0x8007007E: CreateObject(Microsoft.BDD.Utility) - ZTIGather 6/26/2016 9:41:41 PM	0 (0x0000)
FAILURE (Err): 424: GetVirtualizationInfo for Gather process - Object required ZTIGathe 6/26/2016 9:41:41 PM	0 (0x0000)


And the ZTI!GetAllFixedDrives on the successfully devices returns C: D: E:  / where on the failures only returns C: D:

Failure

ZTIUtility!GetAllFixedDrives =   C:  D:	LiteTouch	6/26/2016 9:48:33 PM	0 (0x0000)

VS.

Sucess

ZTIUtility!GetAllFixedDrives =   C: D: E:	LiteTouch	6/24/2016 6:32:37 PM	0 (0x0000)

Any assistance would be greatly appreciated as I try to move the success rate closer to 100%.  I can post more of the logs if needed. Thanks in advance!

 


Viewing all articles
Browse latest Browse all 11297

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>