Workstation Migration Assistant 1.0 RC1
Well, it’s been in development for quite some time, but I’m finally happy enough with the feedback from both my own company and external testers to make a more public release.
Please note that this IS a release candidate and as such, may be prone to a few bugs that have yet to be discovered. Rest assured however, that both myself and a 20-strong test team have been battering this for the past while so I’m confident that there’s no *major* bugs.
There’s a ReadMe file included, I *do* advise that you read that first before contacting me about problems. If you still think that you’ve got a valid query or have found a bug, please let me know.
So… Click here to download the Workstation Migration Assistant 
Dan
Thanks for the hard work this must have been to put together, I look forward to testing this.
Nice looking and very handy bit of work, I look forward to testing it out.
Seems like a great idea and the tool looks nice, however not having much success with Office 2007 settings migration. Although it could be I’m not configuring it right.
On second consideration, I think the Office 2007 issue may have been an activation issue.
Dan,
Will this run from within WinPE 2.0?
Sorry if this had been stated earlier somewhere and I missed it.
Thanks,
Randy
Correct me if I am wrong, but in order to run this GUI you need to install USMT on each computer to run the scanstate/loadstate?
From your ReadMe.rtf
Installation and configuration
• Extract the files to a local folder. Please note that WMA does NOT work from a network-location due to .NET security restrictions
Dan, thanks for producing this. Now I just need to find the time to test-drive it!
Randy: No, USMT will not work under WinPE 2.0 and either with WMA as it relies on the .NET framework.
Myton: You know, I hadn’t thought about that. Technically, no, USMT doesn’t need to be installed, WMA does have to be copied somewhere locally though. So you can copy USMT and WMA files to a Temp folder and run. I’ll look into fixing this .NET security issue - there MUST be some workaround to get WMA running from a network location.
Yeah if you can run the WMA from a network share that would be optimal. I have the WMA copied to a flashdrive and everytime I launch it prompts that a USB drive is detected and if I want to use it for the migration process and I say no because there is not enough room on the flash drive to save the data to it. It than goes on and gives me a warning unable to find the USMT installation C:\Program Files\USMT301\scanstate or something like that but give me the option to install the USMT and it downloads and saves the InstallUSMT301_x86.msi to my flash drive and installs the USMT on the computer. I had ran the scanstate and loadstate and on the 4 laptops I tested it downloaded and installed the USMT when testing the scanstate and loadstate.
Hi Dan,
I was able to get WMA to work without downloading the USMT and also got it to work on my flash drive without it giving me that prompt. I haven’t tried using WMA from a network share yet with the cmd you mentioned. I was thinking about creating a batch file to run it and will test next week for I am ready to leave and go home. By the way on an older computer I got an error launching WMA for the Net Framework version on the laptop was not at least a certain version. Might want to add that to the prerequisites for running the WMA. I really like the MailSend option of the success or failure scanstate and loadstate. I also like the health check feature for I had booted up a laptop that must have shutdown improperly and it flagged it…I thought that was pretty cool. Keep up the good work.
Myton
Hi Dan
I’ve developed a similar HTA for USMT migration but it executes capture and restore on the target machine remotely. This allows a helpdesk to manage this without visiting the users desktop. I used some sysinternals tools for the remote execution - (psexec, pskill) and it,s managed via a GUI.
I used cs.ini to manage the machine variables for the capture path.
Is the remote execution something that you would consider adding to your tool?
Cheers
Ian