Hi there, i spent some time recently trying to get this working.
In the end we used microsoft's USMT via landesk - which works nicely and is very simple to use.
In your template run "scanstate" in system migration section and "loadstate" in system configuration section
i was able to get LANDesk profile migration working using USMT as well. However, my method was to substitute SMA with USMT and have the profile migration templates work as as designed including machine mapping. This means I am able to use "Launch Template" in my capture template to automatically create the migration task that migrates the captured profiles to the target machine.
Of course, you can still capture the profiles as a stand-alone task and migrate them later, after mapping the machine in "Machine mapping".
of interested, please let me know and I will let you know how it can be done.
Yes, If you don't mind. I would really appreciate that. Let me know what I need to do.
I have been working on profile migration and would prefer to use USMT, but cannot figure out how to use machine mapping with it. If you could post how you accomplished that, it would be greatly appreciated.
Were you able to get this working?