I took this script and customized it to my environment. I changed it so that it will use the computer name of the computer it is running from as computer a, so the user only has to enter the destination computer. I also added an exit button.
I do have one problem though. The computer association gets created in SCCM, and the data is backed up to the SMP just fine. But, in the migrationstatus.xml that gets created, it has the same GUID for the source and destination computer, even though the SCCM console shows a computer association created with the correct source and destination computer names..
This causes the 'Request State Store' step on the data restore task sequence to fail. If I manually change the guid in the xml file to the correct guid of the destination computer, it completes perfectly..