Jump to content




anyweb

sample XP to Windows 7 task sequences



Recommended Posts

hi all,

 

as this is a common requirement, here are two Task Sequences I use for demoing Windows XP migrations to Windows 7,

 

Related Reading:-

 

OSDMigrateAdditionalCaptureOptions on Technet

OSDMigrateAdditionalRestoreOptions on Technet

 

Before you can use these sample task sequences you must have done the following Steps.

 

Using Computer Association add a computer to your Deploy XP collection, and then Deploy Windows XP to that computer. Once Deployed with XP you can use Direct Membership to add that computer to the Migrate XP to 7 Collection described below.

 

XP to Windows 7 Demo - X86 using Hardlinking

 

The first task sequence XP to Windows 7 Demo - X86 using Hardlinking.xml will migrate XP to Windows 7 using hardlinking

 

XP to Windows 7 Demo - X86 using Hardlinking.xml

 

XP to Windows 7 Demo - X86 using SMP

 

The second one uses a SMP *State Migration Point*

 

XP to W7 Demo - X86 using SMP.xml

 

simply import these task sequences into ConfigMgr, and replace the missing package references (configmgr X86 boot images, microsoft deployment 2010 settings, mdt2010 files, windows 7 autologin enable package, usmt4 package and the Windows 7 X86 WIM file itself).

 

 

See below screenshots to help you with that

 

 

Task Sequence References with hardlinking

 

xp to w7 demo references w hardlinking.jpg

 

 

Task Sequence References with SMP

 

xp to w7 demo references w smp.jpg

 

and then advertise the task sequences to a migrate XP to Windows 7 collection

 

migrate collection.jpg

 

add computers to the Migrate XP to Windows 7 collection and kick off the appropriate TS via RAP.

Share this post


Link to post
Share on other sites


HI,

 

I have downloaded the task sequence from this web site but I am not able to import that to my SCCM console.

I have installed MDT2010 on same sever on which my SCCM2007SP2 resides. When I try to imoprt the TS it thoows an error:

"An error ocurred while storing the task sequence.Please see logs for more information."

 

I am not able to figure out what is the issue.

 

Things I have done so far are:

Created an image of windows 7

Created a package for USMT

 

I have already tested the stand alone deployment of the captured image.

Can I do the hardlink migration( XP to Windows7) without using MDT2010.

 

If yes please guide me how can I configure the TS in SCCM?

 

 

I will be highely grateful for your help.

 

Regards,

Umesh Mishra

post-4930-12658852510215_thumb.jpg

Share this post


Link to post
Share on other sites

are you doing this on the actual server that you are going to deploy from or via an SCCM console ?

Share this post


Link to post
Share on other sites

are you doing this on the actual server that you are going to deploy from or via an SCCM console ?

 

I gigured out the issue. Actually I was trying to import the TS to SCCM console wihout enabling the MDT2010.Once I enabled the MDT and created all required packages using "Create Microsoft Deployment Task Sequence" wizard I was able to import the TS.

 

Now I am testing the TS for XP to Windows hardlink migration. If I come across any issue I will post back here.

 

Thanks for your great step by step articles and soulution to SCCM erros.

 

Umesh

  • Like 1

Share this post


Link to post
Share on other sites

I gigured out the issue. Actually I was trying to import the TS to SCCM console wihout enabling the MDT2010.Once I enabled the MDT and created all required packages using "Create Microsoft Deployment Task Sequence" wizard I was able to import the TS.

 

Now I am testing the TS for XP to Windows hardlink migration. If I come across any issue I will post back here.

 

Thanks for your great step by step articles and soulution to SCCM erros.

 

Umesh

 

Here is a problem again. I ran a mgrate from XP task sequence on a XP client, but none of my data migrated to Windows. Only the desktop wall paper got migrated. Data from desktop, my documents,PST files did not migrate. All data was gone.

 

I am attaching the few log files so that you can grab the culprit!!

 

Please help!

loadstate.log

scanstate.log

smsts.log

Edited by Umesh

Share this post


Link to post
Share on other sites

I imported the XML and I am surprised how many steps it has!

See this screenshot:

 

post-4113-12663487660194_thumb.jpg

 

I am a newbie to SCCM and my [working OSD] TS is only this long:

 

post-4113-12663487843087_thumb.jpg

 

Would it be possible to describe a simple USMT procedure?

 

All I want is to capture user state from one [existing] XP machine and restore that userstate to the Win 7 machine being deployed via SCCM-OSD.

Share this post


Link to post
Share on other sites

Do you have to install MDT2010 to do the OS deployment with SCCM? I have mine running, but it fails to bring the user state back down from the SMP every time. Any Ideas or input would be greatly appreciated.

Thanks

Dallas

Share this post


Link to post
Share on other sites

It is not needed, for an OS Deployment, to have MDT installed.

 

For help on your problem with bringing back the user state from the State Migration Point, we need more information (like logfiles and how your SCCM environment looks like). Also I would advise you to open a new topic for that.

Share this post


Link to post
Share on other sites

Unable to import the SMP XML file. It tells me it completed but the task sequence never shows up. I have tried it from my machine and the server.

Share this post


Link to post
Share on other sites

it's an mdt integration bug most likely, the task sequence will probably be in the root of your task sequences section in the OSD node.

Share this post


Link to post
Share on other sites

you don't need it, it's nothing more than a customised unattend.xml file which you can Deploy 7 without,

Share this post


Link to post
Share on other sites

I am trying to put a Task sequence together that saves the user data locally and migrates it in to Windows 7 from XP. I have been successful saving the data and creating a USMT folder with hardlink files in it. The problem is when the sequence continues the APPLY OS task does a "wiping" and I lose that folder. What are the ways I keep that folder intact for doing a load state later? Or, will the load state information pick up on what used to be there and pull it? Any help reguarding this would be great, I've been trying to figure this out in spare time for about 2 weeks now. Could someone please explain what takes place, and what it is I might be missing from the hardlinking example above.

Share this post


Link to post
Share on other sites

I have a task setup with an (OSDStateStorePath)variable. The original value was %_SMSTSUserStatePath% I tried it with this value then I also tried changing it to c:\MigrateData. Again the folder is showing up before the operating system is applied, but is wiped out when windows 7 does its wiping of data on the drive the image is being placed on. From reading other issues on the Technet forums this is something that configmgr will always do. I'm wondering what the solution to this is, is there something the locks the folder and prevents it from being wiped, or is there some script or something that is moving this folder to the X:\ drive and back during the applicatin of the image. I've read as much as I can on the Technet forums as I can regaurding hardlinking and its still a bit of a mystery.

Share this post


Link to post
Share on other sites

Well... its a pretty straight forward proces... when the OSDStateStorePath is being used it wil be untouched during a disk wipe.

 

For another Hardlink only example take a look here: http://www.petervanderwoude.nl/post/ConfigMgr-2007-USMT-40-and-using-Hard-Links.aspx

For another Hardlink and Offline example take a look here: http://www.petervanderwoude.nl/post/Capture-User-Files-and-Settings-Offline-(WinPE)-or-Online-(FullOS)-with-ConfigMgr-2007.aspx

Share this post


Link to post
Share on other sites

http://support.microsoft.com/kb/958808 says that you need to use a different location other then %_SMSTSUserStatePath%. I understand your saying that it is straight forward and that may be so, however, I'm still attempting to figure this out and only getting more confused because the example just doesn't seem to be working properly for me. I also read http://technet.microsoft.com/en-us/library/bb680631.aspx and this essentially says that _SMSTSUserStatePath is a variable of its own, is that true?

 

Operating System Image

 

1.Deletes all content on the target volume except files under the folder specified by the _SMSTSUserStatePath task sequence variable.

 

 

2.Extracts the contents of the specified .wim file to the specified destination partition.

 

 

3.Prepares the answer file:

 

 

A.Creates a new default Windows Setup answer file (sysprep.inf or unattend.xml) for the operating system that is being applied.

 

 

B.Merges any values from the user-supplied answer file.

 

 

4.Copies Windows boot loaders into the active partition.

 

 

5.Sets up the boot.ini or the Boot Configuration Database (BCD) to reference the newly installed operating system.

Share this post


Link to post
Share on other sites

Correct _SMSTSUserStatePath is a variable on its own that has a standard value(s) during the Task Sequence.

 

If _SMSTSUserStatePath is not working for you, then you should create your own location. Just don't forget to create that location! This means you need two steps (instead of one):

1. Set State Store Location – Set Task Sequence Variable --> Example: %OSDStateStorePath% = C:\StateStore.

2. Create State Store Location – Run Command Line --> Example: cmd /c MKDIR %OSDStateStorePath%.

Share this post


Link to post
Share on other sites

this is nice, I have successfully used the example in a hardlink scenario.

now I would like to test the SMP scenario, but I do not have MDT integrated.

is it possible to modify the sample XP to W7 using hardlinking so that it works entirely from SCCM (without the MDT scripts)?

or if someone would be so kind to share his/her example on this forum?

Share this post


Link to post
Share on other sites

Ok, i just need to recapp and understand this. If Im doing a side-by-side, from windows xp sp3 to a brand new Windows 7 machine, do i have to;

 

1. Install the Deployment tool on al of my XP machines?

2. Run a separate task sequesnce to capture the user state, if Im not doing it via PXE boot?

 

Im using SCCM 2007 SP2 with MDT 2010

 

Thanks

 

Clopez

Share this post


Link to post
Share on other sites

I know this an older thread, but hopefully I can get a solution.

 

I have been trying in vain to import the "XP to W7 Demo - X86 using SMP.xml" example into a test folder in SCCM. No matter what I try, it will not import. I was able to import the hardlinking example without any problems. Does anyone have any ideas why this particular .xml file will not import?

 

Thanks in advance,

Mike

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×