Okay, sorry but I think I have it figured out.
We use OSDInjection.xml to add in DaRT files so we can connect remotely during a build in WinPE. When that was set up original the same entries were added to the 64bit portion of the XML, so it copies the 32bit DaRT tools into the 64bit image. So when ZTISCCM.wsf checks for and finds the RemoteRecovery executable it's there so it attempts to start it. That fails since it is 32bit and it kills the Use Toolkit Package action. Sure enough, I shot myself in the foot. Sorry for taking up people's time. Mike ________________________________ From: [email protected] [[email protected]] on behalf of Marable, Mike [[email protected]] Sent: Tuesday, October 20, 2015 12:41 PM To: [email protected] Subject: [MDT-OSD] RE: OSD 64bit WinPE "Subsystem needed ... is not present" It seems to be the attempted startup of DaRT (RemoteRecovery.exe). Going through the ZTISCCM log the last thing is successfully logs is the setting of OSDStartTime. Lining that up with ZTISCCM.wsf, the next steps involve starting up DaRT. I manually start mimicking the steps. For example, the script checks for the existence of %SystemRoot%\System32\RemoteRecovery.exe, so checked to make sure the file is there. When I reached the point when the script attempts to start RemoteRecovery.exe (line # 305) I tried it on the system and sure enough, "The subsystem needed to support the image type is not present." Somehow I'm sure I've shot myself in the foot. Mike ________________________________ From: [email protected] [[email protected]] on behalf of Marable, Mike [[email protected]] Sent: Tuesday, October 20, 2015 12:27 PM To: [email protected] Subject: [MDT-OSD] RE: OSD 64bit WinPE "Subsystem needed ... is not present" No, the MDT files are untouched. I even created brand new MDT packages for this task sequence. Here is a screenshot of the error and prior dozen or so log entries. ________________________________ From: [email protected] [[email protected]] on behalf of Jason Sandys [[email protected]] Sent: Tuesday, October 20, 2015 12:17 PM To: [email protected] Subject: [MDT-OSD] RE: OSD 64bit WinPE "Subsystem needed ... is not present" That error message is indicative of something 32-bit trying to be executed but because an x64 WinPE image doesn’t have the 32-bit WOW layer, it fails. Have you modified the default MDT scripts in any way? What exactly does the log file show above this – just showing the error message doesn’t really tell us much. J From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Tuesday, October 20, 2015 11:05 AM To: <[email protected]> <[email protected]> Subject: [MDT-OSD] OSD 64bit WinPE "Subsystem needed ... is not present" I'm working on a new build that will be 64bit only (for UEFI machines) and it's failing. We're running CM2012 R2 CU3 and MDT 2013 with ADK 8.1. I started with a native, non-MDT integrated task sequence and it worked wonderfully. I then created a basic, out of the box MDT integrated task sequence and created new MDT Files and MDT Settings packages. Set it to boot using the 64bit boot image (same as the non-MDT integrated sequence used). When the MDT integrated sequence hits the very first "Use Toolkit Package" it fails. The SMSTS shows that it downloaded the MDT Files package but it then bombs out with: "Failed to run the action: Use Toolkit Package. The subsystem needed to support the image type is not present. (Error: 80070134; Source: Windows)" I've got to be missing something simple, but what? Thanks Mike ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
