Dislittlepiggie

Hi there. I've got a deployment I need to run using and MDT TS with UDI. My goal is to use the UDI to install the OS, and possibly some optional applications to a new machine in a side by side install. I'm using a State Migration point to hold captured data for the restore. The capture is running fine, and I can restore data now using a basic data restore TS. My problem is that i'm using what is effectively a 'standard' Client install MDT task sequence in SCCM 2007, with a UDI interface. The default data restore options in the UDI look to me as if they expect an inplace upgrade. I can select data restore options from a USB drive, or a network space, but I can't tell it to use the State Migration Point and restore according to the Computer Associations in SCCM. Is there a way to get the UDI to use the SMP? or do I need to delete that page from the UDI and put in some State restore steps manually?

Found the issue. I have multiple site servers. Primary with 2 children. Creating an association must be done on the local site server for the migration. For example, if you create the association on the parent, and capture/restore on a child site, it doesn't work. If you create the association on the child site where the c/r happens it works fine. Not sure why the location matters but it does.

I created a basic capture TS, and advertised it to a collection containing the source machine. I then ran the TS from within XP on the machine from the run advertised programs app in control panel.

Here's the associations

oops... typo on my part. I'm running version 4.00.6487.2000, e.g. sp2 on my servers.

Ive inherited an SCCM 2007 SP2 environment. I'm trying to get OSD and USMT working. I've setup MDT integration, and USMT 4 in my environment. My OS deploys fine. So, if I do a basic new machine install, no problem. I tried setting up a computer association assuming I would have a new machine as the target of the data. So, I created the association using the MAC address of the new machine as the target, and used the existing computer object of my source machine as the source in the computer association. I created a basic MDT task sequence to capture my data on my fired up my older XP machine,advertized the TS to a capture collection with my XP machine in it, and ran a state capture on it from XP (I did not boot to PE and run it). After I figured out there were some old KB's I needed to remove, and/or run a cert fix on I got the capture to run fine. The data moved up into my state migraiton point without a problem. When I tried doing a new install on my target machine, the user state did not move into place. When I looked at my computer associations, I saw that a new association had been created. The new association is an inplace upgrade of my XP machine to my XP machine (source and target at teh same box). No migration information is listed in my side by side migration computer association. It's as if the capture TS just ignored that I wanted it to move to a new machine, and assumed it should do an inplace upgrade. Help!