Systems Deployment

There's lots of threads on myitforum or the Microsoft Forums on this http://social.technet.microsoft.com/Forums/en-US/configmgrosd/threads so its worth having a look around there

Best starting point is to use the wizard provided with SCCM to deploy your image. Then look at the Task Sequence steps involved in the capture and restore . These take place when you run an in-place upgrade i.e. a Win7 deployment to an existing XP machine with SCCM client

I assume you've correctly created the USMT (4??) package and you must also create a State Migration Point (SMP) in SCCM. Then with a in-place upgrade as described if you look under the Computer Association tab you'll see an entry created for the existing machine called in-place. It requests the state store , capture the state store and then releases it i.e. uses USMT to copy the existing settings up to the SCCM SMP. Then at the end of the build if you look at the Task sequence steps it has line request state store, restore user state and release so its the reverse i.e. a loadstate command to pull all the saved settings down onto the new Win7 image

You need to understand and get this working correctly before proceeding. Next steps are when the state is captured for an "old" machine and transferred to a new machine. In this instance, yes you would create a custom task sequence with the three lines to request state store, capture and release, but be aware you MUST setup a computer association record between the old and new computers before you send out the advertisement to the old machine to capture its store

Having done this you will see the computer association record update. Then you can import the MAC address of the new machine into the console and specify the source machine i.e. the one you captured from. When the bare-metal build occurs on your brand new PC it will then restore the state captured onto the state migration point so the user gets the new machine with his/her settings included !

Sorry for the late reply and thanks for helping. I am using USMT 3.01 for the migration and installed the SMP role but I get this error:

SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error.
Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate.
Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use.
Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.
Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges.
Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy.
For more information, refer to Microsoft Knowledge Base.

I've have IIS, WebDev, and BITS components installed already. Re-installing the SMP several times does not help. Any suggestions?

OK, I was not able to resolve my errors with the SMP so I went back to what I had created in the first place as shown in my first post.

1. Created a USMT package with no program
2. Created a Capture TS with only the 'Capture User State' task and pointed it to my USMT package.
3. Created a Restore TS with onlly the 'Restore User State' task and pointed it to my USMT package.
4. Created 2 collections. 1 called Capture and the other Restore. Both have collection variables OSDStateStorePath and \\server\share\folder
5. Advertised the Capture TS to the Capture collection and advertised Restore TS to the Restore collection.

The step I was missing was the computer association. Once I associated the computers then I was able to capture the source computer today and restore the destination computer tomorrow. My only question left is about the captured files. After it restores the files, how do I get it to auto delete after a certain amount of days? I know the SMP has that option but I'm not using SMP.