Jump to content


  • 0
anyweb

sample XP to Windows 7 task sequences

Question

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

Recommended Posts

  • 0

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

  • 0

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

  • 0

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

  • 0

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

  • 0

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

  • 0

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

  • 0

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

Join the conversation

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

Guest
Answer this question...

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

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.