Skip to content

Some Basic Questions about Side By Side Migrations

Featured Replies

I ended up canning the whole usage of USMT 4.0 in SCCM for side by side migrations. Now I use a batch file that includes the command line for USMT Scanstate and Loadstate using offline migration. I basically do the following:

 

1. build my new machine using SCCM

2. Pull the hard drive from the old machine and connect it to the new machine (either via USB or E-Sata)

3. Plug in a USB thumbdrive containing USMT 4.0 and my batch files for both scanstate and loadstate

4. Verify the drive letters match the drive letters in my command line in the batch file (there are many ways to get around this step...I am just lazy)

5. Run Scanstate.bat (this runs scanstate using the following command line:

e:\USMT\x86\scanstate.exe C:\Migrate /offlineWinDir:F:\Windows /o /localonly /c /efs:copyraw  /v:5 /l:E:\Logs\scanstate.log /progress:E:\Logs\scanstateprogress.log /i:E:\USMT\x86\miguser.xml /i:E:\USMT\x86\migapp.xml /uel:90 /ui:ats\*

You will want to modify this, as I am only pulling domain profiles...so ATS is our domain

You will notice that I am saving logs back to the thumb drive...I am scanning a windows folder on the E drive (the drive we pulled from the old pc) and a local store on the new pc C:\migrate.

 

6. Run Loadstate.bat (runs the loadstate on the new pc)

e:\USMT\x86\loadstate.exe C:\Migrate /c  /v:5 /l:E:\Logs\loadstate.log /progress:e:\Logs\loadstateprogress.log /i:E:\USMT\x86\miguser.xml /i:E:\USMT\x86\migapp.xml /lac /uel:90  /ui:ATS\*

Again, we are running the loadstate from our thumb drive...it is saving the logs to the thumbdrive...and it is restoring the data from the mig file created on the local C drive from our scanstate.

 

It just works for us...seems pretty simple, and cuts down on the amount of time to migrate data. We migrated 17GB with 15000 files..took 12 minutes to scan...and 9 min to load.

 

Hope this helps.

 

PS- the batch files are simply the code snippets above...just copy and create a batch file with each of the command lines (and adjust for drive letter differences and whatnot)

 

Thanks for responding, but this will not work in our scenario. Due to the number of deployments and location etc we won't be able to move hard drives. We will have to use the SMPs to hold the data for the migration. I found this hotfix today and I'm wondering if it will help resolve this problem.

 

http://support.microsoft.com/?kbid=980270

Well, I think I may have determined what my issue is. I'm still testing, but I think I've made some progress.

 

Here is an example of how domestic is configured.

 

C01 <- This is the central site or top level

|

P01 <- This is the US Primary Site Server

| | |

S01 S02 S03 <- These are Secondary Sites at various US locations

 

 

So, I was logged into C01 when creating the Computer Associations. While in the console, it was listed as side-by-side like what is shown in the screen shots. However, when completing the capture, it created a new entry labeled as In-Place. After tons or research I came across a little note on Microsoft's documentation that A Site-By-Site is not possible over Parent/Child sites. This got me thinking.

 

First of call, C01 does not have ANY agents assigned to it nor a distribution point. So, The only other Server with a Console installed is P01. I logged into P01 and created the Side-by-Side computer association for two machines that reside in S01. I did a capture state and sure enough the record was updated and the backup location was listed! Oddly, when I check the computer associations area on C01, it creates two entries that are identical and are labeled as In-Place....no idea what is going on there.

 

For my next test, I created a Side-by-Side migration of a machine that is in P01 and another in S01. This one did not restore successfully since it could not locate the data. The capture for S01 went to S01's SMP where as the restore for the machine in P01 was looking for it in P01's SMP....which it obviously wasn't at. Just for testing, I copied the backed up folder from S01's SMP to P01's SMP and it was able to locate it and pull it down. However, this also demonstrates that you can only use Side-by-Side migration for machines that talk to the same management point.

 

P01->P01 Good

S01->S01 Good

S01->P01 Bad

P01->S01 Bad

 

Obviously, if we did the scanstate and loadstate manually via command line and not using the SMP's there wouldn't be an issue. Or, if all sites used the SAME location for its SMP I could see that potentially working.

 

Sorry for the long post, but I hope this may help others in the future.

  • 6 months later...

Hey,

 

I am sorry but could you point me to where anyweb has that side-by-side ts? I want to compare it to mine. I pretty much used the MDT 2010 Client Replace task sequence to gather the source. Then used the Standard Client task sequence to try and deploy the image and migrate the user settings to the machine. But it doesnt seems to be working.

 

Any help would be appreciated.

 

Thanks again.

  • 4 years later...

We need to do a Windows 7 to Windows 7 migration. We are doing a hardware refresh and want to give users a new laptop/desktop and preserve their settings using USMT. I have read this thread and there is a ton of stuff here. I also read this. I have imported the Side by Side Migration task sequence from ANYWEB where can I download this same task sequence for CM2012?

And is there a basic how-to on doing a side-by-side? Something that covers all the steps? or is it just a hodge-podge of links you have to sift through? Thanks.

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.