locked
Understanding the how to do a "Sccm OSD ZTI computer replace" migration. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
     

    I'm wondering how many of you on this forum have used SCCM 2007 R2 OSD for the replacement of existing xp computers with new computers running vista migrating user profiles with usmt.  It seems that the MDT-Client Replace task Sequence is suited for this.

     

    I am looking for more information on how the process works, the only thing I've found is this rather vague paragraph.  http://technet.microsoft.com/en-us/library/bb978374.aspx#EBAA called " Use the Import Microsoft Deployment Task Sequence Wizard and the Client Replace Task Sequence"

     

    We currently have SCCM 2007 R2 installed in our network with about 1400 Xp clients which will be replace with new hardware running vista Sp1.  Not sure if we'd want to keep the same computer names and not sure if this is a requirement of client replace Task Sequence.

     

    So I created a client replace task sequence only seems to create the steps for backing up the user profile then backing up the computer and wiping the disk.  So at this point I'm completely lost as to what Task Sequence one would use to Apply our vista image and most importantly name the new computer and restore the correct profile USMT capture file on each. Parallel to this how does one associate the Old-computer = New computer and then restore the correct USMT migration file to the new computer. And to make things a bit more completed we going to give our vista hardware image to our hardware vendor so the images can be applied by vendor.  ( this idea was save time by not having to copy the image to the New - Computer over the network during deployment.

     

    So fare my knowledge level of the SCCM OSD is limited to creating a reference computer and capturing it !

     

    Any help or pointers for reading material would be appreciated !

     

    Thank you.

    Naim
    Wednesday, January 14, 2009 4:46 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hey, Naim.  I know I went through all kinds of articles dealing with OSD trying to figure out what path was right for us.  Currently, when I upgrade a user from an old PC to a new PC (a side-by-side migration, I beleive that's called) I run a task sequence that uses USMT3 to backup all of the user data to the State Migration Point, then image a new PC with my standard image, and then download the user data from the SMP.

    The key to doing a side-by-side is setting up a computer Association.  Located in the OSD section of the console, this allows you to "link" two PCs to each other and migrate the settings from one to the other.  The only down-side to this, is that a brand new PC isn't in the SCCM database and has to be manually entered using the "import" feature.

    There are ways to automate this process in R2, such as setting up a collection to automatically name and import any unknown computer that PXE boots, but we haven't gone down that path.  Since we're a relatively small organization, manually importing the data is not a big deal.

    I'm sure I didn't answer all (if any) of your questions, so feel free to quiz me some more.

    Carl...
    Tuesday, January 20, 2009 8:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Also, you mentioned having your PCs "pre-imaged" by your hardware vendor.  With a side-by-side migration, you need to establish the association between the two computers BEFORE you run the USMT.  If you have a technician onsite, this isn't a big deal, but because you need the computers MAC address or GUID in order to import it into the database, you can't start the migration process until AFTER you've already gotten the information about the new computer.  It might be wise to discuss with your hardware vendor is they can send you a list of the PC's MAC addresses prior to shipping the PCs, so that you can create a file and import the entire list into the database all at once.

    Just a thought...
    Tuesday, January 20, 2009 8:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi CD Shriver,
    I just found your post here and this is what I have been trying to do as well.
    I made the link between my old computer and the new bare metal PC and was able to get USMT to grab the profile but I am not sure how to get the profile down to the new PC or even how to get the task to go from the old PC to jump over to the new PC.
    Do you do that with one task sequence or twoo?
    Could you show me an eampl of your task? Maybe share the xml?
    Thanks for the help,
    Sam
    Monday, June 8, 2009 10:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hey Sam,

    you're almost certainly going to need two Task Sequences to di it properly.  The way I've set it up is that I have two Task Sequences created, one for capturing user states and one for imaging the PC and then loading the user state at the very end.  I think I just used one of the default Task Sequences and modified it as needed.  Does that help?

    Tuesday, June 9, 2009 12:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    In your situation you won't be able to restore user datas while restoring the master image onto the new computer.

    What you'll need will be :



    1/ Create a Task Sequence to Capture on the Old Computer using USMT

    2/ Create a Task Sequence to Restore on the New Computer using USMT

    3/ Imaging the computer at the vendor and install SCCM Client + Insert into the Domain (Make sure the computer is detected in the All Systems collection)

    4/ Creating a computer association

    5/ Running the Capture TS on the Old Computer

    6/ Running the Restore TS on the New Computer

    Tuesday, June 9, 2009 2:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks CD Shriver,
    I have taken your advice and created two Task, one to capture the user settings and the other to push out the OS and restore the user settings.
    I have a task that will pusho our the OS currently so I am focusing just on the task to capture user data useing USMT. I have my migration point setup in SCCM and I have a share on the server but when I run the task nothing seems to happen.

    My task is:
    request state store
    capture user state (use state migration tool package - I have this pointing to my USMT package)
    release state store

    I then advertise this to my collection but nothing happens. Any suggestions or am I missing anything?

    Thank you,
    Sam
    Wednesday, July 1, 2009 4:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    did you make the advertisement mandatory ? are you doing any computer association ?
    My SCCM Guides http://www.windows-noob.com/forums/index.php?showforum=44
    Wednesday, July 1, 2009 4:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    One thing that got me, with USMT is that you actually have to install it on the SCCM server for it to work.  Originally, I just downloaded the USMT installation files and created a package from them, but that doesn't work.  For my server I installed USMT to the c:\program files\USMT folder, then shared that folder out as a USMT share and gave everyone read writes to it.  Then I made a package and pointed the source files at that share.

    Also, one thing to do is to check the specific log files for task sequences.  I think if you look in the client's CCM\logs folder you'll find a folder called SMSTSlogs (or something simmilar) and it will hold the log files for the Task Sequence that you just ran.  It should contain logs that describe what the USMT package was doing and may point you in the right direction.

    Carl....
    Wednesday, July 1, 2009 5:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for everyone's input. I did get it to work.
    I had created a share for USMT at one point. I was having trouble with it working and I recreatedt the share and recreated the package. that did not work either.
    I had also created a share for the SMP to use and called it d:\user data and gave everyone read access. That did not work.

    After reading through the input in this forum I deleted my SMP, deleted the share and then recreated a folder called d:\UserData without making it a share. I think recreated the SMP and pointed it to this folder. It now works.

    I am not sure if it was the share permissions that it did like or if it did not like the space on d:\user data but either way it now works.

    Thank you again for the informatin I will now test the who process of:

    / Create a Task Sequence to Capture on the Old Computer using USMT

    2/ Create a Task Sequence to Restore on the New Computer using USMT

    3/ Imaging the computer and install SCCM Client + Insert into the Domain (Make sure the computer is detected in the All Systems collection)

    4/ Creating a computer association

    5/ Running the Capture TS on the Old Computer

    6/ Running the Restore TS on the New Computer



    Sam
    Wednesday, July 1, 2009 7:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey Sam,

    Great Work.  Would you mind sharing your task sequences so that we can import them?  And maybe even screen shots? 

    That would really help. 

    Thank you.

     

    Tuesday, March 22, 2011 1:46 PM