4 and 5 are setup that way, since folder with subfolders for the architecture... so maybe the older version needs to be setup that way..
There is a variable USMT3=YES or TRUE (can't remember) you would normally set the tells is to use the old version. Chris Nackers Microsoft MVP - Enterprise Client Management Email: ch...@nackersconsulting.com<mailto:ch...@nackersconsulting.com> Nackers Consulting Services, LLC From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Richard Zuraff Sent: Thursday, October 10, 2013 1:15 PM To: mdtosd@lists.myitforum.com Subject: [MDT-OSD] RE: Issue with Determine Local or Remote UserState not working with USMT 3.01. I'm not sure what the issue was, but I had to add the X86 folder and the x64 folder to the USMT 3.01 folder. Must have been a change on how they do the logic now with the USMT on MDT 2012. I didn't have to do this on MDT 2010 as we only have 32bit XP machines. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Chris Nackers Sent: Thursday, October 10, 2013 1:11 PM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: [MDT-OSD] RE: Issue with Determine Local or Remote UserState not working with USMT 3.01. Anything worthwhile in SMSTS.log? Your SMP site role configured correctly? Chris Nackers Microsoft MVP - Enterprise Client Management Email: ch...@nackersconsulting.com<mailto:ch...@nackersconsulting.com> Nackers Consulting Services, LLC From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Richard Zuraff Sent: Thursday, October 10, 2013 12:11 PM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: [MDT-OSD] RE: Issue with Determine Local or Remote UserState not working with USMT 3.01. No it's not even getting that far, it runs the script to determine if it should be local or on the State Migration Point. [cid:image001.png@01CEC5BC.4559F550] From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Chris Nackers Sent: Thursday, October 10, 2013 11:09 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: [MDT-OSD] RE: Issue with Determine Local or Remote UserState not working with USMT 3.01. Do you have a scanstate log? Or is it not even getting that far? Chris Nackers Microsoft MVP - Enterprise Client Management Email: ch...@nackersconsulting.com<mailto:ch...@nackersconsulting.com> Nackers Consulting Services, LLC From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Richard Zuraff Sent: Thursday, October 10, 2013 10:41 AM To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com> Subject: [MDT-OSD] Issue with Determine Local or Remote UserState not working with USMT 3.01. I'm trying to setup our XP image up in SCCM 2012 SP1 with MDT 2012 UP1 installed. The step is failing when I'm trying to run USMT part of the imaging process. This works fine in our SCCM 2007 with MDT 2010 UP1 environment. Has anything changed that it will not allow usmt 3.01 to work with MDT 2012 UP1? I'm not able to find anything online about this. Executing command line: Run command line Process completed with exit code 9701 Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. Property capture is now = Property estimate is now = Microsoft Deployment Toolkit version: 6.1.2373.0 The task sequencer log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. Checking for USMT Files in C:\_SMSTaskSequence\Packages\GMS0022E\X86 The USMT files in C:\_SMSTaskSequence\Packages\GMS0022E\X86 are not USMT4 or USMT5 FAILURE ( 9701 ): Unable to find any version of USMT, unable to perform user state migration. Command line returned 9701
<<inline: image001.png>>
