Comments on: A quick look at: Workstation Migration Assistant

By: Jason

Jason — Sat, 14 Feb 2009 10:27:28 +0000

Dan, can I have a copy for testing. jason

By: Dave Wrede

Dave Wrede — Wed, 11 Feb 2009 21:14:44 +0000

Just found this tool and it seems to work as expected (at least on XP to XP). We’re testing for XP to Vista and have created a .BAT file to make the necessary .NET changes. So far little luck. But we’re keeping on it. Is there a way to select individually select the users to move? Is it possible to move the information store to a computer with a different name?
Thanks,
Dave

By: Richard

Richard — Mon, 31 Mar 2008 15:37:00 +0000

In answere to a couple of queries regarding using WMA with Microsoft Deployment Toolkit (WMA) – and adjusting the ZTIUserState.wsf file to use WMA – I would suggest going for a more componentised solution – add the call for the WMA tool to the task sequence as a new task (useing some of the command line options that Dan has built in)and disable the standard USMT tasks (within the state capture and state restore groups) within the task sequencer. MDT’s use of USMT is designed to be hands off – that is it runs USMT as an unattended task to capture and then as another unattended task to restore – WMA by its design requires user intervention – so I would drop it in as a new set of tasks – particularly useful if you are creating a media based deployment using MDT…

Richard – Microsoft UK

By: Dan

Dan — Thu, 27 Mar 2008 20:13:36 +0000

Well, between the debug log and the generated logfiles you can get a very good idea of what’s happening. In fact, the ScanState.Log will give the full command-line.

Btw, Error 12, from what I recall, is because you’re running ScanState or LoadState without being a Local Administrator.

Cheers, Dan

By: Kevin Egan

Kevin Egan — Thu, 27 Mar 2008 19:48:14 +0000

Thanks Dan. One particular benefit to what I suggest is a PowerShell-like view of what WMA is doing. It would go a long way to helping people understand USMT as well (it is not well documented at all!). For example, I can’t get my own scanstate and loadstate scripts to run at all (getting ERROR 12) and would really like to compare against how WMA is writing and running the commands as they seem to work (congrats!).