MDT 2012 U1 Blue Screen on task sequence ??

My Customer have MDT 2012 U1, so when he start a task sequence when the task start apply operating system, after the system restart and when the computer install the system the blue screen appear. It is very strange beacause the same task sequence work on
some other model but in this Lenove M82 (3306-G1F) and M82 (M3395-AB4) we have the same error. But on other Lenovo model the same task work very fine. Why?
SMSTS.log
We do not find an available volume to store the local data path TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a global environment variable _SMSTSNextInstructionPointer=24 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a TS execution environment variable _SMSTSNextInstructionPointer=24 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a global environment variable _SMSTSInstructionStackString=22 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a TS execution environment variable _SMSTSInstructionStackString=22 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Save the current environment block TSManager 2014-09-11 08:54:07 1892 (0x0764)
pszPath[0] != L'\0', HRESULT=80070057 (c:\qfe\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,58) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\environmentlib.cpp,639) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Failed to save environment to (80070057) TSManager 2014-09-11 08:54:07 1892 (0x0764)
TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
Unknown error (Error: 80070057; Source: Unknown) TSManager 2014-09-11 08:54:07 1892 (0x0764)
SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Failed to persist execution state. Error 0x(80070057) TSManager 2014-09-11 08:54:07 1892 (0x0764)
Failed to save execution state and environment to local hard disk TSManager 2014-09-11 08:54:07 1892 (0x0764)
Start executing an instruciton. Instruction name: New Computer only. Instruction pointer: 24 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a global environment variable _SMSTSCurrentActionName=New Computer only TSManager 2014-09-11 08:54:07 1892 (0x0764)
Set a global environment variable _SMSTSNextInstructionPointer=24 TSManager 2014-09-11 08:54:07 1892 (0x0764)
Evaluating an AND expression TSManager 2014-09-11 08:54:07 1892 (0x0764)
Evaluating a variable condition expression TSManager 2014-09-11 08:54:07 1892 (0x0764)
Variable = DeploymentType TSManager 2014-09-11 08:54:07 1892 (0x0764)
Value = NEWCOMPUTER TSManager 2014-09-11 08:54:07 1892 (0x0764)
Operator = equals TSManager 2014-09-11 08:54:07 1892 (0x0764)
Expand a string: equals TSManager 2014-09-11 08:54:07 1892 (0x0764)
Expand a string: DeploymentType TSManager 2014-09-11 08:54:07 1892 (0x0764)
Expand a string: NEWCOMPUTER TSManager 2014-09-11 08:54:07 1892 (0x0764)
The variable condition expression is evaluated to be TRUE TSManager 2014-09-11 08:54:07 1892 (0x0764)
The AND expression is evaluated to be TRUE TSManager 2014-09-11 08:54:07 1892 (0x0764)
The condition for the group (New Computer only) is evaluated to be true TSManager 2014-09-11 08:54:07 1892 (0x0764)
The group (New Computer only) has been successfully started TSManager 2014-09-11 08:54:07 1892 (0x0764)
Sending status message . . . TSManager 2014-09-11 08:54:07 1892 (0x0764)
Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 2014-09-11 08:54:07 1892 (0x0764)
User did not specify local data drive TSManager 2014-09-11 08:54:07 1892 (0x0764)
Volume D:\ is not a fixed hard drive TSManager 2014-09-11 08:54:07 1892 (0x0764)
Volume X:\ is not a fixed hard drive TSManager 2014-09-11 08:54:07 1892 (0x0764)
Volume Z:\ is not a fixed hard drive TSManager 2014-09-11 08:54:07 1892 (0x0764)
BDD.log
Property LogPath is now = X:\MININT\SMSOSD\OSDLOGS LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Property Debug is now = FALSE LiteTouch 2014-09-11 08:53:34 0 (0x0000)
ZTIUtility!GetAllFixedDrives (Faux) LiteTouch 2014-09-11 08:53:34 0 (0x0000)
ZTIUtility!GetAllFixedDrives = LiteTouch 2014-09-11 08:53:34 0 (0x0000)
No task sequence is in progress. LiteTouch 2014-09-11 08:53:34 0 (0x0000)
New ZTIDisk :
\\MININT-KGJQ3PL\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Found Possible OS TargetDisk:
\\MININT-KGJQ3PL\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" LiteTouch 2014-09-11 08:53:34 0 (0x0000)
GetPartitions: 0 LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Did not find disk. LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Property SMSTSLocalDataDrive is now = LiteTouch 2014-09-11 08:53:34 0 (0x0000)
Unable to connect to BCDStore. LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Not running within WinPE or WinRE. LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property DeploymentMethod is now = UNC LiteTouch 2014-09-11 08:53:40 0 (0x0000)
DeploymentMethod = UNC LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property DeployRoot is now = X:\Deploy LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Using a local or mapped drive, no connection is required. LiteTouch 2014-09-11 08:53:40 0 (0x0000)
DeployRoot = X:\Deploy LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property DeployDrive is now = X: LiteTouch 2014-09-11 08:53:40 0 (0x0000)
DeployDrive = X: LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property PHASE is now = PREINSTALL LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property DeploymentType is now = NEWCOMPUTER LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Phase = PREINSTALL LiteTouch 2014-09-11 08:53:40 0 (0x0000)
About to run command: wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /inifile:Bootstrap.ini LiteTouch 2014-09-11 08:53:40 0 (0x0000)
Property inifile is now = Bootstrap.ini ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
------------------------- Object Initialization ------------------------- ZTIGather 2014-09-11 08:53:40 0 (0x0000)
------------------------- Initialization ------------------------- ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Synchronizing the environments. ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property DeployRoot is now = X:\Deploy ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property DeployDrive is now = X: ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Finished synchronizing the environments. ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property definition is now = BDD_Welcome_ENU.xml Wizard 2014-09-11 08:53:40 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 Wizard 2014-09-11 08:53:40 0 (0x0000)
Getting OS info ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property OSCurrentVersion is now = 6.1.7601 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property OSCurrentBuild is now = 7601 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property OSVersion is now = WinPE ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property IsServerOS is now = False ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property IsServerCoreOS is now = False ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Finished getting OS info ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Getting HAL information ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Not Wizard = Faux Wizard 2014-09-11 08:53:40 0 (0x0000)
Property WizardComplete is now = N Wizard 2014-09-11 08:53:40 0 (0x0000)
Property HALName is now = acpiapic ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Finished getting HAL information ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Getting network info ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Checking network adapter: [00000000] Intel(R) 82579LM Gigabit Network Connection ZTIGather 2014-09-11 08:53:40 0 (0x0000)
MAC address = 44:37:E6:D0:8F:EF ZTIGather 2014-09-11 08:53:40 0 (0x0000)
IP Address = 10.26.33.23 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
IP Address = fe80::8d70:f039:f93f:e5e9 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Default Gateway = 10.26.32.1 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property IPAddress001 is now = 10.26.33.23 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property IPAddress002 is now = fe80::8d70:f039:f93f:e5e9 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property MacAddress001 is now = 44:37:E6:D0:8F:EF ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Property DefaultGateway001 is now = 10.26.32.1 ZTIGather 2014-09-11 08:53:40 0 (0x0000)
Finished getting network info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Getting DP info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Unable to determine ConfigMgr distribution point ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Finished getting DP info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Getting WDS server info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Unable to determine WDS server name, probably not booted from WDS. ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Finished getting WDS server info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Property HostName is now = MININT-KGJQ3PL ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Getting asset info ZTIGather 2014-09-11 08:53:41 0 (0x0000)
Unable to determine asset tag via WMI. ZTIGather 2014-09-11 08:53:41 0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll) Result : 0 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
RUN: regsvr32.exe /s "X:\Deploy\Tools\x86\Microsoft.BDD.Utility.dll" ZTIGather 2014-09-11 08:53:42 0 (0x0000)
FindFile: The file x64\Microsoft.BDD.Utility.dll could not be found in any standard locations. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
FindFile(...\Microsoft.BDD.Utility.dll) Result : 1 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
RUN: regsvr32.exe /s "" ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property AssetTag is now = ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SerialNumber is now = MJ24PLX ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Make is now = LENOVO ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Model is now = 3306G1F ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Product is now = MAHOBAY ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property UUID is now = 4C5C19C8-5CD9-11E3-8E8B-153233E31400 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Memory is now = 3891 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Architecture is now = X86 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property ProcessorSpeed is now = 3300 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property CapableArchitecture is now = AMD64 X64 X86 ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsLaptop is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsDesktop is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsServer is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsUEFI is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsOnBattery is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsX86 is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsX64 is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsSLAT is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Finished getting asset info ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Getting OS SKU info ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Unable to determine Windows SKU while in Windows PE. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Determining the Disk and Partition Number from the Logical Drive X:\WINDOWS ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property OriginalArchitecture is now = ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Getting virtualization info ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsHypervisorRunning is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsVT is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsNX is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property Supports64Bit is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property SupportsHyperVRole is now = True ZTIGather 2014-09-11 08:53:42 0 (0x0000)
This computer does not appear to be a virtual machine (BIOS is 'LENOVO - 14c0'). ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsVM is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Finished getting virtualization info ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Connection succeeded to MicrosoftVolumeEncryption ZTIGather 2014-09-11 08:53:42 0 (0x0000)
There are no encrypted drives ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property IsBDE is now = False ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Processing the PREINSTALL phase. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Determining the INI file to use. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Finished determining the INI file to use. ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Using from [Settings]: Rule Priority = DEFAULT ZTIGather 2014-09-11 08:53:42 0 (0x0000)
------ Processing the [DEFAULT] section ------ ZTIGather 2014-09-11 08:53:42 0 (0x0000)
Property DEPLOYROOT is now = \\10.26.32.40\DeploymentShare$ ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: DEPLOYROOT =
\\10.26.32.40\DeploymentShare$ ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property USERID is now = Administrateur ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: USERID = Administrateur ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property USERDOMAIN is now = crdiq03 ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: USERDOMAIN = crdiq03 ZTIGather 2014-09-11 08:53:43 0 (0x0000)
<Message containing password has been suppressed> ZTIGather 2014-09-11 08:53:43 0 (0x0000)
<Message containing password has been suppressed> ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property KEYBOARDLOCALEPE is now = 0c0c:00001009 ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: KEYBOARDLOCALEPE = 0c0c:00001009 ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property SKIPBDDWELCOME is now = YES ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Using from [DEFAULT]: SKIPBDDWELCOME = YES ZTIGather 2014-09-11 08:53:43 0 (0x0000)
------ Done processing X:\Deploy\Scripts\Bootstrap.ini ------ ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Remapping variables. ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property TaskSequenceID is now = ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Property DeploymentType is now = NEWCOMPUTER ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Finished remapping variables. ZTIGather 2014-09-11 08:53:43 0 (0x0000)
ZTIGather processing completed successfully. ZTIGather 2014-09-11 08:53:43 0 (0x0000)
Command completed, return code = 0 LiteTouch 2014-09-11 08:53:43 0 (0x0000)
Property WizardComplete is now = Y Wizard 2014-09-11 08:53:44 0 (0x0000)
About to run command: wpeutil.exe SetKeyboardLayout 0c0c:00001009 LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Command completed, return code = 0 LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Validating connection to \\10.26.32.40\DeploymentShare$ LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Mapped Network UNC Path Z: =
\\10.26.32.40\DeploymentShare$ LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Found Existing UNC Path Z: =
\\10.26.32.40\DeploymentShare$ LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Successfully established connection using supplied credentials. LiteTouch 2014-09-11 08:53:44 0 (0x0000)
About to run command: wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /nolocalonly LiteTouch 2014-09-11 08:53:44 0 (0x0000)
Property definition is now = WelcomeWiz_Initialize.xml Wizard 2014-09-11 08:53:44 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 Wizard 2014-09-11 08:53:44 0 (0x0000)
Property nolocalonly is now = ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Microsoft Deployment Toolkit version: 6.1.2373.0 ZTIGather 2014-09-11 08:53:44 0 (0x0000)
------------------------- Object Initialization ------------------------- ZTIGather 2014-09-11 08:53:44 0 (0x0000)
------------------------- Initialization ------------------------- ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Synchronizing the environments. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Property DeployRoot is now = \\10.26.32.40\DeploymentShare$ ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Property DeployDrive is now = X: ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Finished synchronizing the environments. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Skipping local settings gathering because it has already been done. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Processing the PREINSTALL phase. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Determining the INI file to use. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Not Wizard = Faux Wizard 2014-09-11 08:53:44 0 (0x0000)
Property WizardComplete is now = N Wizard 2014-09-11 08:53:44 0 (0x0000)
Using DEFAULT VALUE: Ini file =
\\10.26.32.40\DeploymentShare$\Control\CustomSettings.ini ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Finished determining the INI file to use. ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Added new custom property MYCUSTOMPROPERTY ZTIGather 2014-09-11 08:53:44 0 (0x0000)
Using from [Settings]: Rule Priority = DEFAULT ZTIGather 2014-09-11 08:53:45 0 (0x0000)
------ Processing the [DEFAULT] section ------ ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property EVENTSERVICE is now = http://10.26.32.40:9800 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: EVENTSERVICE = http://10.26.32.40:9800 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property OSINSTALL is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: OSINSTALL = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property JOINWORKGROUP is now = GROUPE ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: JOINWORKGROUP = GROUPE ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property TIMEZONE is now = 035 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: TIMEZONE = 035 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property TIMEZONENAME is now = Eastern Standard Time ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: TIMEZONENAME = Eastern Standard Time ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property KEYBOARDLOCALE is now = 0c0c:00001009 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: KEYBOARDLOCALE = 0c0c:00001009 ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property USERLOCALE is now = fr-CA ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: USERLOCALE = fr-CA ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property UILANGUAGE is now = fr-CA ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: UILANGUAGE = fr-CA ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPCAPTURE is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPCAPTURE = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
<Message containing password has been suppressed> ZTIGather 2014-09-11 08:53:45 0 (0x0000)
<Message containing password has been suppressed> ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPAPPLICATIONS is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPAPPLICATIONS = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPCOMPUTERBACKUP is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPCOMPUTERBACKUP = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPDOMAINMEMBERSHIP is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPDOMAINMEMBERSHIP = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPCOMPUTERNAME is now = NO ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPCOMPUTERNAME = NO ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPDEPLOYMENTTYPE is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPDEPLOYMENTTYPE = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPUSERDATA is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPUSERDATA = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPPACKAGEDISPLAY is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPPACKAGEDISPLAY = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Property SKIPLOCALESELECTION is now = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000)
Using from [DEFAULT]: SKIPLOCALESELECTION = YES ZTIGather 2014-09-11 08:53:45 0 (0x0000

Hi,
I agree with Damon.
Might be the ConfigMgr Driver Injector will help you.
This tool will allow you to capture installed drivers on your workstations and then will automatically import them in ConfigMgr 2012.
http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d
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.

Similar Messages

Distribute Customer Updates in SCCM 2012 (CU's) using a Task Sequence

I want to utilize a Task Sequence to Distribute Customer Updates to SCCM 2012 Clients. I currently have 2 collections for pre-CU 4 clients, one for 32 Bit Clients (x86) , one for 64 Bit Clients (x64). I have a package pertinent to each collection
which I use to distribute the updates.
However, instead of segregating them by collection, I would like to have one big collection, and have the Task Sequence sort out which package should load on which collection.
I've tried using the RUN COMMAND LINE, and INSTALL PACKAGE options to no avail. Is there a way to utilize a Task Sequence for this undertaking, or should I just continue the way I'm currently doing it.
Thanks ,
Dan

You can set Collection Variables for the two collections, then add running condition in the Task Sequence Steps for corresponding collections.
Juke Chou
TechNet Community Support

2 questions - missing boot image, create mdt task sequence button missing

I'm learning SCCM 2012. I am watching a training video and the instructor shows a "Create MDT Task Sequence" button at the top of his ribbon bar when going into Task Sequence. I do not have this button - where did it go? I am
using 2012 SP1.
All I see is "Create Task Sequence" and "Create Task Sequence Media" but not "Create MDT Task Sequence".
Also - I only have an x86 boot image, and no x64. How do I get this into my inventory?
Thank you
Nathan

"Create MDT Task Sequence" will be visible after you install MDT and integrate it to SCCM.
MDT is different product and not part of default SCCM installation.
You can integrate MDT to SCCM to create advanced Task Sequence if the default is not suitable for your needs.
Integrate MDT to SCCM.
MDT latest version is 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=40796
For creating x64 boot image:
http://social.technet.microsoft.com/Forums/en-US/a3877a66-d35c-49ca-95c5-1c02d1611f2f/default-x64-boot-image-not-created-during-sccm-2012-setup
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

MDT 2012 - Tools folder not being copied over post OS install

Just started having this issue after rebuilding my 2010 DS into 2012. Using a standard task sequence, I am not doing any special with the DiskPart either. Installing to Disk 0, Partition 1. After it goes through the PostInstall phase, it is supposed to reboot
and then go into Windows and continue the task sequnce. Instead, I get a message that it is unable to find the SMS Task Sequencer. The error in the log is basically, could not locate the TSMBootStrapper in the standard locations. I look in the MININT folder
and the Tools folder is missing. If I manually copy the folder from the DS and manually kick-off the LiteTouch.wsf it then continues just fine.
I need help figuring out why the folder is not being copied into the MININT folder before the reboot.
This seems to only be happening on laptops. When I deploy to a desktop or a VM, the task sequence proceeds without issue.

IT is possible that when upgrading your MDT Deployment share from version X to Version Y, some of the scripts were not copied over correctly.
Create a *New* deployment share from scratch using the newer version of MDT, and see if that works, if it does, then start migrating over content from the bad share to the known good share, use tools like WinDiff.exe to verify each script.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Unable to read task sequence configuration disk

Target Server is an HP ProLiant BL460c G5
I'm trying to load my reference iso via the iLO connection, mounting the image to the CD drive. I used the same process to create the WIM file on my Source Server and it worked fine. I boot from the CD, it loads windows files, then comes up to
the SCCM screen with the error "Unable to read task sequence configuration disk."
Any ideas what's going on?

In my case I had the same error using SCCM boot media in a USB 3.0 port. Solution was here to use a USB 2.0 port to solve it.
Maybe this will help you:
http://www.jamesbannanit.com/2012/02/unable-to-read-task-sequence-configuration-disk-in-sccm-osd/
My blogs: Henk's blog and
Virtuall | Follow Me on:
Twitter | View My Profile on:
LinkedIn

Task Sequence Stops at UDI Wizard

Im using configmgr 2012 R2 with MDT integration. I have a task sequence that is getting stuck on the UDI wizard stage. In the progress bar it just gets stuck at UDI Wizard and gets no further. the smsts log stops at "mapping server
share" the user logged in has permissions to that drive and I can browse it.
I have used this udi wizard in other task sequences before. any ideas on where to look?
log file located at
http://www.filedropper.com/smsts11

I'm having a pretty similar problem. I have a task sequence to capture user state and at the end, there is a section to copy logs. The task sequence just stops there.
The last line in smsts.log is "Mapping server share: \\server\share$".
The last line in zticopylogs.log is "Mapping server share: \\server\share$".
The last few lines in BDD.log are...
Microsoft Deployment Toolkit version: 6.2.5019.0 Wizard 2/21/2014 1:49:50 PM 0 (0x0000)
The task sequencer log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. Wizard 2/21/2014 1:49:50 PM 0 (0x0000)
Not Wizard = True Wizard 2/21/2014 1:49:50 PM 0 (0x0000)
Property UserCredentials is now = False Wizard 2/21/2014 1:49:50 PM 0 (0x0000)
Validate Against UNC: \\server\share$ Wizard 2/21/2014 1:49:50 PM 0 (0x0000)
Validate Against UNC: \\server\share$ Wizard 2/21/2014 1:49:50 PM 0 (0x0000)
It hangs pretty much indefinitely. I'm really stumped on this one because there aren't error codes or anything else to look up.

Maximum allowed run time for a task sequence

I found if i left the maximum allowed run time for a task sequence with a defualt value of "0" in configuration manager 2012 r2 cu2,the required task sequence would never run without a maintenance window larger than
12H.
At client side,the servicewindowmanager.log always said this required task sequence had a maximum runtime of 43200 seconds(12h).
servicewindowmanager.log:
OnIsServiceWindowAvailable called with: Runtime:43200, Type:5
Program cannot Run! Setting *canProgramRun to FALSE
There does not exist a Service Window of this Type, for this duration. The Program will not run.
If i set maximum allowed run time to 120 minutes,task sequence would run under a 3h mainenance window.
So if you leave the maximum allowed run time for a task sequence with a value of "0" then client agent will evaluate it as 43200(12h) for a required deployment,is it true? have i missed something?

Hi,
That is correct it will default to the same value as a program with a "Unknown" maximum runtime value, Unknown is also evaluated to 0 = 12h so that is correct behaviour.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

MDT 2012 - Task Sequence Not Completing

I'm a complete novice with MDT 2012, but I have had pretty good luck getting a deployment for Server 2008 R2.
I have a reference system, and I do a very vanilla sysprep and capture using the template task sequence with no changes.
My deployment has a few app installs and other configuration items, but nothing too exotic.
My problem is this: during deployment, after applying the system from WinPE, I perform the final reboot. At this point, the expected action is for an autologon to take place, and for the local Administrator account to run c:\Litetouch.vbs, which does some final
cleanup and a few tasks that require the target system to be running.
This isn't happening on my system. And a look at the registry shows that the autologon stuff has not been set up, so it won't ever happen. It's not a matter of having an incorrect account, or a count of 0, none of the autologon registry keys are even present.
In trying to solve this (I believe it worked when I first started!) I've stripped down my deployment to a pair of task sequences that have no customization
at all in either the capture or the deployment task sequences, and still no luck. So I believe that something has changed in my reference system - but I unfortunately can't roll back.
What is driving me a little nuts is that I can't tell when that autologon information is supposed to be inserted in the registry. There is code in Litetouch.wsf that appears to do it, in function PopulateAutoAdminLogon, but I can't come up with a scenario in
which this function gets called. I am guessing that perhaps sysprep does it when creating the WIM, but I can't seem to find good information on that.
I've done a lot of searching on this, and unfortunately the answer space is cluttered with people who have a similar sounding but completely different problem - they want their deployed system to do an autologon, and after deployment their system comes up with
the logon screen instead of doing what they want. I've seen a few people post similar problems to mine, but nobody has received an answer. This one is pretty close, it suggest I might have a group policy item that disables the local admin account, but I don't
think it hits the mark for me.
http://social.technet.microsoft.com/Forums/en-US/mdt/thread/e625aa88-2415-4a2a-9e79-ac6b37119c27
So in a nutshell: when deploying a system using MDT 2012, at what point do the autologon items from unattend.xml stuffed into the registry for use after state restore/reboot in the task sequence? And what can go wrong with that?
- Mark

Same here, can't find any solution though. Did you ever work it out?

What determines whether an application gets a green check or a yellow warning sign in the deployment summary screen when using an MDT/UDI task sequence?

I am trying to get Office 2010 to install using a UDI task sequence, and it IS installing, but it has a yellow exclamation point next to it at the summary screen after the task sequence completes, as does another app I am trying to install.
The apps that use an .MSI are fine, and get the green check, but the two apps that use .exe for their installers get the yellow warning sign. I assume this has to do with exit codes or detection rules, but I am very new to SCCM (using 2012 and MDT
2012 Update 1), so I need some help.
Thank you!
EDIT: This probably has to do with the fact that SuccessOrFailureCode being blank. I have been pouring over .vbs scripts and logs, but they all seem to indicate that my application installs just fine, with an exit code of 0. Where does this screen
get the SuccessOrFailureCode?
Like
This
Quote
MultiQuote
Edit

I have some updated info on this problem.
I am trying to install Symantec Endpoint Protection with a custom wrapped .EXE file, and I have created detection rules for the install.
According to AppEnforce.log, SEP is installing and returning an Exit code of '1', and that is being handled with my custom return code handling, which I've defined as a 'success'. However, the deployment summary is still showing a yellow exclamation point
next to the SEP install, and the SuccessOrFailureCode is blank.
Why isn't the SuccessOrFailureCode equal to '1'? Where is the disconnect between the AppEnforce.log and the deployment summary.

Task sequence fails after upgrading to 2012 R2 and MDT 2013

After upgrading to 2012 R2, my task sequence fails after the Setup Windows and ConfigMGR & Restart Computer. Instead of continuing to run the task sequence and load up the MDT Toolkit Package, it just stops at the Windows 7 login screen.
Do I need to create new toolkit & settings packages with MDT 2013 settings? Or do I just need to create a new task sequence?
I can't figure out what log to look at on the VM that I am imaging. If someone can point it out maybe there's some useful information. Thanks.
My task sequence

It sounds a lot like that it could be failing at the client installation. Please take a look at the client installation logs.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Here are the log files from c:\windows\ccmsetup\logs .. I took a glance and things run with success 0 which should mean no error right? The system also has the client installed with the CU2 patch.
Client Logs
Searched a bit online and people are saying it's due to the incorrect boot image. I was using a WinPE 5.0 I created on this TS but I'm going to make another and see where it goes.
This was the solution.

SCCM 2012 SP1 and MDT 2012 Task Sequence Templates, MDT File/Settings Packages

We're setting up SCCM 2012 integrated with MDT 2012 for our OSD. My main issue is finding actual reference material for the MDT task sequence templates when integrated with SCCM. The MDT documentation has a lot of information on variables and task sequences
outside of SCCM integration.
One thing I'd love to find information on is what's actually going on during an MDT Client Task Sequence template. I found this http://social.technet.microsoft.com/Forums/en-US/645a77b2-5be6-431d-818c-57d24b1435cc/understanding-mdt-task-sequence?forum=configmgrosd but
it doesn't delve into the kind of detail I'm looking for. I can dig up information through the MDT reference material on some things, but I just can't find anything out there that actually walks you through an SCCM/MDT task sequence template. For instance,
under State Restore what is being referenced in Install Software with base variable name PACKAGES, vs Install Applications and base variable name COALESCED APPS. And, where are you supposed to put these applications? That's just a specific example, I'm hoping
to find some kind of walkthrough.
Two things I'm hazy on are the MDT packages. What exactly are the MDT Settings Package, and the MDT Files Package? What are they used for? What benefits do you get out of using them? And, how exactly do you use them? I know one of them has something to do
with customsettings.ini, but what's the point of using SCCM with MDT if you still have to muck around in the customsettings.ini file?
Either way, it seems like there are a lot of references to SCCM task sequences, and a lot of references to MDT task sequences. But, not together. Which is a bit annoying since the MDT-integrated task sequence templates are very obviously different than either
SCCM or MDT by itself. Any help would be appreciated, even just information on where to look. Maybe I'm just really bad at finding reference material for SCCM/MDT. Thanks.

When MDT integrated with SCCM, We need the following MDT components to be created:
MDT Boot image
MDT Toolkit Files
MDT Settings
The MDT boot image (for example) gives you extra abilities over the standard ConfigMgr boot image such as the ability to display a HTA Refer here:
http://www.windows-noob.com/forums/index.php?/forum/98-frontends-and-web-services/
MDT Files once created, you will find UDIWizard_Config.Xml file in which you can start User driven Installation OSD using UDI designer.
Refer these links for better understanding:
http://www.windows-noob.com/forums/index.php?/topic/5131-using-sccm-2012-rc-in-a-lab-part-16-integrating-mdt-2012-rc1-with-configuration-manager-2012/
http://www.windows-noob.com/forums/index.php?/topic/5221-using-sccm-2012-rc-in-a-lab-part-17-using-mdt-2012-rc1-within-configuration-manager-2012/
http://www.windows-noob.com/forums/index.php?/topic/5250-using-sccm-2012-rc-in-a-lab-part-18-deploying-a-udi-client-task-sequence-with-mdt-2012-rc1-integrated-in-configuration-manager-2012/
Thanks, Prabha G
Thanks for the quick reply. But, what about the MDT Settings Package? Also, both have a pretty big folder structure for each package. Surely it does more than just provide a couple xml and ini files? I'm not looking for anyone to spoon-feed me the information,
but at least a pointer in the right direction for finding the reference material. It seems for SCCM/MDT integration you have to go all over the place finding scraps of information to put together.
Also, any info on the SCCM/MDT task sequence templates? Thanks.

MDT 2012 Blue Screen AHCIX64s.sys

Hello All,
I am having a problem after updating my deployment share image for MDT 2012. I am pretty sure the deployment share had not been updated in about 4-5 months and we had recently received some new hardware and added new drivers to MDT. I added the
drivers, and 3 of the 4 models booted just fine, the 4th claimed it didn't have drivers.
SO I went through and updated the boot image and added the new image to WDS. Now when I attempt to netboot any machine, I get a BLUE SCREEN OF DEATH referencing ahcix64s.sys. I went through every driver I could find for the last 6-12 months that
referenced ahci and unchecked "enable this driver". I then went through and updated the deployment share and added the new image to WDS. I am still getting the BLUE SCREEN OF DEATH.
Any suggestions on how to fix this? DO I need to delete all the drivers, as opposed to unchecking the "enable this driver"?
Joe

Are you getting the BugCheck on all machines or just one machine? Specifically, what is the error?
I have encountered problems with the Intel ACHI driver, since the *.inf file is identical between x86 and x64 it's difficult to know which driver package is for which OS. Hopefully MDT is doing the right thing here, and filtering out the correct version. How
many achi driver versions are being injected into the WinPE image (check the DISM.log)?
-k
Keith Garner - keithga.wordpress.com

Mdt 2012 sp1 command line does not run from task sequence

Hi,
I am hoping I can explain this correctly. I am using MDT 2012 and having an issue with running command lines, powershell and batch files that I setup.
The task sequence is set to use an account called "MDTService". it has rights to join the domain but is not in the local admin group of the reference image. a domain GPO renames the local admin account CoAdmin.
when running a command line to, for example, run xcopy a folder and subdirectories to the "program Files x86" directory, it does not copy.
When I log on to the system and use an admin account to manually run the command I do not have an issue. if I log onto the system with the MDTService user and run it, it fails.
How do I get the commands to run from the MDT task sequence? I do not want to make the MDTService user an admin. I have tried the run as option in the task sequence but that did not work. maybe is set it wrong. I used a domain\Admin
account which did not work.
what can I clarify or logs can I post to provide more details.
Thanks in advance.

Any account that needs to add files under %ProgramFilesx86% must be granted administrative privileges.
Keith Garner - keithga.wordpress.com

Applications not being deployed during task sequence - MDT 2013 + SCCM 2012 R2

Hi everyone,
I have recently integrated MDT2013 with my SCCM 2012 R2 and I am trying to move away from OSD in SCCM and switch to MDT. I managed to get a blank image deployed and now I am trying to tweak CustomSettings.ini to install applications based on the default
gateway and model. For some reason, the apps are getting pulled but not deployed. Here is what I have in the files:
Settings Package - CustomSettings.ini
[Settings]
Priority=DefaultGateway, Model, Default
Properties=MyCustomProperty
[OptiPlex 9020]
Applications001=Mozilla Firefox
[DefaultGateway]
192.168.XXX.254=Poland
192.168.XXX.254=London
[Poland]
Applications001=ESET
[Default]
DoCapture=No
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES
Administrators001=myDomain\adminGroup
Applications001=Skype
Applications002=Office Professional Plus 2010
When the TS runs, I can see it's getting all the apps from the list, here is a snippet from ZTIGather.log
Using from [Settings]: Rule Priority = DEFAULTGATEWAY, MODEL, DEFAULT
------ Processing the [DEFAULTGATEWAY] section ------
Match found for default gateway 192.168.XXX.254, retrieving settings.
------ Processing the [Poland] section ------
Property APPLICATIONS001 is now = ESET
Added value from [Poland]: APPLICATIONS = ESET
------ Processing the [OptiPlex 9020] section ------
Property APPLICATIONS001 is now = ESET
Property APPLICATIONS002 is now = Mozilla Firefox
Added value from [OptiPlex 9020]: APPLICATIONS = Mozilla Firefox
------ Processing the [DEFAULT] section ------
Property OSINSTALL is now = Y
Using from [DEFAULT]: OSINSTALL = Y
Property DOCAPTURE is now = No
Using from [DEFAULT]: DOCAPTURE = No
Property SKIPCAPTURE is now = YES
Using from [DEFAULT]: SKIPCAPTURE = YES
<Message containing password has been suppressed>
<Message containing password has been suppressed>
Property SKIPPRODUCTKEY is now = YES
Using from [DEFAULT]: SKIPPRODUCTKEY = YES
Property APPLICATIONS001 is now = ESET
Property APPLICATIONS002 is now = Mozilla Firefox
Property APPLICATIONS003 is now = Skype
Added value from [DEFAULT]: APPLICATIONS = Skype
Property APPLICATIONS001 is now = ESET
Property APPLICATIONS002 is now = Mozilla Firefox
Property APPLICATIONS003 is now = Skype
Property APPLICATIONS004 is now = Office Professional Plus 2010
Added value from [DEFAULT]: APPLICATIONS = Office Professional Plus 2010
Property ADMINISTRATORS001 is now = myDomain\adminGroup
Added value from [DEFAULT]: ADMINISTRATORS = myDomain\adminGroup
------ Done processing CustomSettings.ini ------
So the settings do get picked up and selected. ZTICoalesce.log also shows the apps picked up:
Coalesce pattern to be used: Applications
Coalesce base variable to use: CoalescedApps
Added value ESET-KRKLON from APPLICATIONS001 to the list
Added value Mozilla Firefox from APPLICATIONS002 to the list
Added value Skype from APPLICATIONS003 to the list
Added value Office Professional Plus 2010 from APPLICATIONS004 to the list
Property CoalescedApps01 is now = ESET
Property CoalescedApps02 is now = Mozilla Firefox
Property CoalescedApps03 is now = Skype
Property CoalescedApps04 is now = Office Professional Plus 2010
ZTICoalesce processing completed successfully.
Now when I go to the smsts.log file, I can see this:
App policy for 'ESET' not received. Make sure the application is marked for dynamic app install
Policy download failed, hr=0x80004005
and later
Failed to run the action: Install Application.
Unspecified error (Error: 80004005; Source: Windows)
After that, no other apps are mentioned and seems like the failure on ESET drops the whole sequence and moves forward. I can see later the default admin being added correctly.
Any ideas what I may be missing here? Especially on the failed policy download?
Thanks
Jakub

HI,
"App policy for 'ESET' not received. Make sure the application is marked for dynamic app install"
Is the ESET application deployed? it sounds like it could be the check box on the application "Allow this application to be installed from install application task sequence action without beeing deployed" that is missing? If the application isn't
deployed this checkbox must be ticked.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

MDT 2012 Suspend Task Sequence Problem

Hi ,
I have been using LTISuspens.wsf without problem in my MDT 2010 and MDT 2010 U1 for a long time. Recently I have create my test MDT 2012 and I have problem with this task.
I have created the new Run Command line cscript.exe "%SCRIPTROOT%\LTISuspend.wsf" in State Restore section. The build and capture TS is stopping correctly and I have the LTISuspend icon on the desktop. After resuming the TS, it going correctly through, running
sysprep, pop in again Set Network Location window, I can see it is running “Apply Windows PE (BCD)” step and then stops. There is message “suspended” and “The task sequence has been suspended true Use the…..”
Any ideas what I am doing wrong?
My customsettings.ini is from MDT 2010 and there they are fine.
I am capturing Windows 7.
Thanks
Vinnie

Hi,
A few suggestions below for each of your issues.
Issue 1 is that you don't see any task sequences in the wizard
- Have you updated your deployment point after upgrading to 2012? if not then do this now
- Have you updated your boot media with the newly generated Litetouch_x86.wim (meaning your boot CD, boot USB or WDS)
The thinking behind this is that if you are using MDT 2010 boot media to try and speak to an MDT 2012 DS then you will have the same problem.
Issue 2 is that you've had the TS running in the past but it's broken for one reason or another.
- Have you recreated your Task sequence using the MDT 2012 client template? There are (minor but critical) differences in the logic between the versions of MDT and the new task sequence template has been updated as such. Using an MDT 2010 template with
MDT 2012 scripts can cause this.
These are 3 things that cause similar issues to you following an upgrade.

MDT 2012 U1 Blue Screen on task sequence ??

Similar Messages

Maybe you are looking for