Jump to content


anyweb

using Offline Mode in Windows PE using USMT 4 via a task sequence in SCCM 2007 SP2

Recommended Posts

My SCCM is SP2 R2 with MDT2010 Update 1 integrated.

 

I'm using anywebs imported Task Sequence for USMT offline migration.

 

So this is my problem:

 

I have XP operating systems where all the profiles are located in the root of d -partition (D:\Documents and settings).

 

I have a plain Win 7 image and I've configured unattend.xml file so that it moves the Win 7 profile folder "users" to d -partition. (d:\Users) during the task sequence. When I ran the the offline migration task sequence it run perfectly and there are no errors in the log files.

 

But still I can not get the profile files to migrate correctly. After the migration has completed and when I log in to the computer I can see both the d:\Documents and settings folder (which has all the profiles that should be migrated) and D:\users folder in the d -partition. And the just logged on user account is of course created in the users folder.

 

So it simply seems that the user files don't get migrated.

 

I'm really badly stuck with this problem.

 

Does somebody have any idea what the problem might be?

 

Do I somehow have to modify the MigUser.xml file to scan the d -drive?

Share this post


Link to post
Share on other sites


Can you please explain the "special workaround" for the first USMT package which uses the x86 files? I need to go from 32bit XP to 64 bit 7. Also I was planning on putting the captured user data on an external drive (or network) as I need to resize the drive partitions, has anybody done this?

 

Regards,

 

DGA

Share this post


Link to post
Share on other sites

the workaround simply tells scanstate what to do (command line) via a batch file, and you can store the state on a network share as long as it's not hardlinked, and yes i've done it right here in this MultiPurpose FrontEnd HTA

Share this post


Link to post
Share on other sites

Thanks for the info.

 

Two questions:

 

I need to resize the local partitions, I assume this means I cannot use hardlinking?

 

Has anybody been able to migrate any of the regional settings during an offline USMT migration?

 

Thanks...

Share this post


Link to post
Share on other sites

OK, so I can now hardlink and reformat the local drives, which is cool...

 

It would be nice to get the regional settings migrated over, I cannot believe this is not possible....

Share this post


Link to post
Share on other sites

I do have another question. Is there a way to force a PXE boot without going to each machine and physically setting up the bios? I read something about the Dell Client Configuration Utility but it looks fairly complicated and only works on Dells. We mostly have Dells but we have several IBMs too. I know, if anyone knows, You Know.

Thank You.

 

There's alo a 1E product which has a PXE helper... we are assessing it now and Ill elt you know how it goes.

Share this post


Link to post
Share on other sites

Couldn't you do it without the batch file? You can set the TS variable USMT_WORKING_DIR as a TS step and then use a "Run command line" TS step to run the scanstate.exe can't you?

Share this post


Link to post
Share on other sites

I unfortunately skipped page 2 of this thread and was wondering why the xcopy command was copying all of the contents of the SMSPKGn$ share and made a little more flexible workaround.

 

Instead of needing to reference the package name in the xcopy command, you can instead:

1) Create a batch file and name it, for example, install.cmd in the USMT x86 source folder with the following content(s):

xcopy "%~dp0*" %Systemdrive%\USMTbits /herciy

2) in the Xcopy task sequence, change the commandline to simply "install.cmd"

 

This can be done for each XCOPY TS and eliminates the need to reference the Package ID.

Share this post


Link to post
Share on other sites

Has it ever been determined why user data is not being restored but instead still sitting in the USMTOffline folder?

 

I receive a task sequence error when it attempts to restore, when I login I can see all the data in the folder but it is not restored. My USMT 4 package points to the USMT root folder with the x86 and x64 subfolders within. I have it set so advertisement data is downloaded to the DP.

Share this post


Link to post
Share on other sites

Which error do you get?

 

I will run it again at work tomorrow and reply back. I've been trying a few different methods trying to get this to work and the furthest I've gotten so far is just not having the data restore back into the directories. I've also tried using this method instead:

 

http://blogs.technet.com/b/configurationmgr/archive/2010/06/30/how-to-use-usmt-4-hardlinking-in-a-configuration-manager-2007-task-sequence.aspx

 

So I could use it also for W7 to W7 rebuilds but I get an immediate error on my first task sequence when I try to restart into the full Windows OS, it gives me an error code that translates to the operation is not allowed.

 

Does anyone mind sharing their XML so I can compare to what I have setup to see where I may be going wrong.

Share this post


Link to post
Share on other sites

post your smsts.log here and if necessary the scanstate.log

Share this post


Link to post
Share on other sites

Right now I am using a different method which seemed to work without errors on the screen, however data was still not restored.

 

http://sccm.haas.se/?p=272

 

Error is IsUSMTPreLonghorn failed (0x80070002)

UserStateMigrationAction: GetUSMTBinaryFailed (0x80070003)

Failed to initialize

Failed to run the action Restore User State. The system cannot find the file specified.

 

Right now I am trying the capture with the USMT package point to the USMT root and then with the restore USMT package pointed directly to x86 to see if it is having issues deciphering what to execute. I can see all the USMT files (x86 and x64) being downloaded right before trying to execute the restore function, so I am wondering if it is looking in the USMT root and not seeing the file it needs.

 

I cannot find a loadstate log on the PC when going into F8. I can only see the smts logs.

post-11088-0-10401900-1314131381_thumb.jpg

Share this post


Link to post
Share on other sites

I did a bit more digging today and was looking through the Config Mgr. It looks like our primary site had the latest SCCM client installed, however the secondary sites never had their packages updated with the latest SP2 client, so they were installing SP1 which was in their package folder. I've updated the sites this evening and am hoping this will fix the issue, I know SP2 is needed for USMT 4 to work, so if all my other items are in order - I'm hoping to report back with success!

Share this post


Link to post
Share on other sites

Well, I finally got things working...my two main issues were that the central site had SP2 Config Mgr. Client but the distribution points had not been updated.

 

After updating those, I had to include the following in my scanstate.

 

/ui:*.* /ue:Administrator /ue:*\*

 

You could also do %computername%\* if you have accounts which have a \ in them which need to be migrated. I did not want any local accounts to be migrated.

Share this post


Link to post
Share on other sites

well done on solving the issues !

Share this post


Link to post
Share on other sites

I've got this working now - thanks anyweb for your excellent work!

 

One question: when firing off the TS, everything seems to work properly.. no significant errors or anything, but the "do x86 scanstate" stage seems to take a long while - i.e. 25-40 minutes plus, even for a base image with nothing on it. I am familiar with the USMT outside of SCCM, and I do know that when running in the Windows XP OS, it's definitely quicker than that. Is there something that my "do x86 scanstate" portion of the TS is getting held up on? I tried checking the scanstate.log, but it was nowhere to be found in the C:\USMTbits\x86 folder - which could mean that the scanstate hasn't even started yet and is still "hung." Eventually, it does go through though.... anyone else experience this?

Share this post


Link to post
Share on other sites

I'm hoping someone can help with this!

 

As stated in my above post, the "do runscanstate x86" step takes forever... after examining my smsts.log... it's almost as if it's not even doing anything for an entire half hour - THEN it starts to migrate the profiles and shows the percentages.

 

Also - since then, for whatever reason, it's telling me my boot image is inaccessible, and thus, my TS fails directly after the scanstate.

 

I've attached my smsts.log ...PLEASE someone help!

smsts.log

Share this post


Link to post
Share on other sites

scanstate works fine see here > Successfully complete the action (do X86 scanstate) with the exit win32 code 0

 

after that it trys to apply the operating system (are you sure the OS wim image is correct ?)

 

<![LOG[Not a data image]LOG]!><time="16:11:14.844+240" date="09-09-2011" component="ApplyOperatingSystem" context="" type="0" thread="408" file="applyos.cpp:320">

<![LOG[ApplyOSRetry: ]LOG]!><time="16:11:14.844+240" date="09-09-2011" component="ApplyOperatingSystem" context="" type="0" thread="408" file="applyos.cpp:331">

<![LOG[TSLaunchMode: UFD]LOG]!><time="16:11:14.844+240" date="09-09-2011" component="ApplyOperatingSystem" context="" type="0" thread="408" file="applyos.cpp:332">

<![LOG[OSDUseAlreadyDeployedImage: FALSE]LOG]!><time="16:11:14.844+240" date="09-09-2011" component="ApplyOperatingSystem" context="" type="0" thread="408" file="applyos.cpp:333">

<![LOG[Rebooting and retrying]LOG]!><time="16:11:14.844+240" date="09-09-2011" component="ApplyOperatingSystem" context="" type="0" thread="408" file="applyos.cpp:345">

<![LOG[Process completed with exit code 0]LOG]!><time="16:11:14.844+240" date="09-09-2011" component="TSManager" context="" type="1" thread="1708" file="commandline.cpp:1102">

<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="16:11:14.844+240" date="09-09-2011" component="TSManager" context="" type="1" thread="1708" file="instruction.cxx:3010">

<![LOG[successfully complete the action (Apply Operating System) with the exit win32 code 0

 

and that appears to complete ok, it then claims it needs to retry (possibly due to bad image ?)

 

<![LOG[The action (Apply Operating System) requested a retry]LOG]!><time="16:11:14.954+240" date="09-09-2011" component="TSManager" context="" type="1" thread="1708" file="engine.cxx:263">

<![LOG[Reboot to WinPE]LOG]!><time="16:11:14.954+240" date="09-09-2011" component="TSManager" context="" type="1" thread="1708" file="engine.cxx:453">

<![LOG[Calling RebootSystem()]LOG]

 

[staging boot image DOT00001]LOG]!><time="16:11:14.954+240" date="09-09-2011" component="TSManager" context="" type="1" thread="1708" file="bootimage.cpp:672">

<![LOG[0, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\encryptablevolume.cpp,368)]LOG]!><time="16:11:15.344+240" date="09-09-2011" component="TSManager" context="" type="0" thread="1708" file="encryptablevolume.cpp:368">

<![LOG[Checking to see if the data path is on a bootable volume]LOG]!><time="16:11:15.344+240" date="09-09-2011" component="TSManager" context="" type="1" thread="1708" file="bootimage.cpp:939">

<![LOG[buffer was too small to get disk layout. Trying again with 1248 bytes]LOG]!><time="16:11:15.344+240" date="09-09-2011" component="TSManager" context="" type="1" thread="1708" file="diskutils.cpp:1269">

<![LOG[0, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\encryptablevolume.cpp,368)]LOG]!><time="16:11:15.359+240" date="09-09-2011" component="TSManager" context="" type="0" thread="1708" file="encryptablevolume.cpp:368">

<![LOG[boot Image not found in local data cache. Staging is required

 

then it claims the boot image is not found (you are using multicasting here it seems also ?)

 

<![LOG[Boot Image package not found.

Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="16:13:15.386+240" date="09-09-2011" component="TSManager" context="" type="3" thread="1708" file="bootimage.cpp:1002">

 

so is the boot image distibuted to both dps ? is your image wim a valid captured OS ?

Share this post


Link to post
Share on other sites

Yes the scanstate action completed with no errors, but if you look here, I get the "Starting the Migration Process" (the first step of the USMT) appears at 15:36, and then it doesn't start the first gathering of profile data until 16:10... if I run the USMT from a full OS standpoint, the gathering of the profile data starts almost immediately. It seems as though there's definitely a hold up here, and the ts is idle for about 30 minutes during the 'run scanstate x86' portion:

 

 

<![LOG[Starting the migration process]LOG]!><time="15:36:17.171+240" date="09-09-2011" component="InstallSoftware" context="" type="1" thread="1812" file="runcommandline.cpp:34">

<![LOG[Offline engine startup from WinDir - c:\windows]LOG]!><time="16:10:33.614+240" date="09-09-2011" component="InstallSoftware" context="" type="1" thread="1812" file="runcommandline.cpp:34">

<![LOG[Processing the settings store]LOG]!><time="16:10:33.614+240" date="09-09-2011" component="InstallSoftware" context="" type="1" thread="1812" file="runcommandline.cpp:34">

<![LOG[]LOG]!><time="16:10:33.614+240" date="09-09-2011" component="InstallSoftware" context="" type="1" thread="1812" file="runcommandline.cpp:34">

<![LOG[Examining the system to discover the migration units]LOG]!><time="16:10:33.614+240" date="09-09-2011" component="InstallSoftware" context="" type="1" thread="1812" file="runcommandline.cpp:34">

<![LOG[]LOG]!><time="16:10:33.614+240" date="09-09-2011" component="InstallSoftware" context="" type="1" thread="1812" file="runcommandline.cpp:34">

<![LOG[ S-1-5-21-1210859283-1907650544-1231754661-71091 (SWDist) (1 of 4): 0% done ]LOG]!><time="16:10:33.879+240" date="09-09-2011" component="InstallSoftware" context="" type="1" thread="1812" file="runcommandline.cpp:34">

<![LOG[ S-1-5-21-1210859283-1907650544-1231754661-71091 (SWDist) (1 of 4): 42% done ]LOG]!><time="16:10:33.879+240" date="09-09-2011" component="InstallSoftware"

 

As for the OS image, there shouldn't be any problems with it. There's nothing out of the ordinary on the WIM file, and I've used it countless times in my standalone Windows 7 Base Image task sequence. Correct me if I'm wrong, but the steps here would be:

 

Scanstate

Stage the boot image

Apply the Operating System

 

It seems as though the root of the problem is that the boot image is not being loaded successfully (although it works fine from another TS), and yes, I've updated the x86 boot image on both DPs. Why would it try to apply the operating system before the boot image is even loaded?

 

As for the scanstate.log, that's the one thing I am going to check as soon as I get back to the office on Monday. I was about to examine it briefly on Friday evening before I left, but I checked both C:\USMTbits\x86 and X:\Windows\temp and I did not see it listed there from within the command shell.

 

Thanks in advance for your help guys! I really want to tackle this.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...