Workstation Migration Assistant 1.01
Doh, missed a bug, caused by a bloody typo. This has now been fixed.
Changelog and download link are in the Workstation Migration Assistant section
Download from here
12 Responses to “Workstation Migration Assistant 1.01”
Trackbacks/Pingbacks.
-
-
30. Jun, 2008
[...] Cunningham has released version 1.01 of his Workstation Migration Assistant program. As Dan puts [...]
Tried running the program, but it choked on size. I went to the config file, and renamed it to a txt. Modified the maxsize to a huge number and resaved. Is this the way to fix this?
Also, when I modified the config by renaming to txt, when I resaved it as a config, it still thought it was a txt file by the graphic. Is this normal?
Is there an easy way to modify the config other than using txt editor?
Arthur
Nope… doesn’t work. For some reason uses the hard coded value of 20480 or something like that. Is there a fix for this?
Arthur
I am new to the USMT. I have downloaded your app, for which I am excited about, thank you for the app., it looks really cool. However, I have no idea how to use it. I have read the “Read Me”, and have looked at the MigAssistant.Exe.Config, but it looks overwhelming. I am not a coder at all. I am simply trying to relocate a profile on a machine that is attached to a SBS 2003 that crashed and I had to reload and need to restore the trust between the machine and server. Do you have some “idiot proof” instructions that I could follow?
Thank you in advance.
Hello Dan,
Still waiting for a reply. Your program simply doesn’t work. Is there a patch for this? Also, I echo the comments by Clint as far as modifying the config file. It is very poorly documented, and difficult to figure out. Are you planning to get this program running? Do you know of another program like this on the market that currently runs?
Thanks
Arthur,
The file needs to remain called MigAssistant.Exe.Config. Just open Notepad or an XML Text Editor, open the file and modify that specific value. In the next release, I’ll make it so that if the value is 0, then there is no limit. You can alternatively acheive this by using the /MIGMAXOVERRIDE switch on the command-line.
I have to disagree that the configuration is poorly documented. Every item is detailed in the ReadMe file. A knowledge on some level of how to use USMT is required though. If you think my app is difficult to figure out, try sifting through one of the USMT Migration XML files!
Clint,
To perform a bog-standard capture / restore with all USMT defaults, all you need to do is modify the MigrationNetworkLocation value in the MigAssistant.Exe.Config file. This is the location on your network where USMT will store the data capture. The Workstation Migration Assistant will look after everything else for you.
Cheers, Dan
Dan,
I have read your response, but don’t understand it. How can I change the size? I do not understand your reference to a command line. I am just trying to run your program from the GUI.
Please give me a step by step on how to do this, as I simply cannot figure it out. As well, how do you specify where you want it to store the data? I have a USB hard drive attached, but there doesn’t seem to be any way to specify the target location.
You talk about modifying the the migration location, but once again I seem to have a problem with this. Your help would be appreciated
Thanks
Hello Dan
I am looking at you application to streamline the USMT tool, as you say it is very criptic to use and documentation leaves much to be desired. I have been using version 2.6 for a few years now as the means to migrate users data as our company refreshs computers. On average 150 to 600 oomputers a year. We have scripted the program with batch files and it works. The GUI of yours brings the use to a new level. I am not sure about some of the settings in your config file and do echo the other users that a bit more explanation would be nice. I changed the config file and migrated profiles as large as 26 gig without a problem.
A couple of comments.
Would it be possible to have a setting to allow for the way the profile path is created.
We currently use Store\Date\ComputerName\USMT3
The option to select other that one or all profiles would be great.
As we have many shared units that need 5-8 profiles backed up and all on these machines is not practical as they can have as many as 60 profiles on them.
We currently use the days feature to limit the profiles selected. This is a workaround and not the best solution.
The other feature that I see would be great if possible would be for your application to run from a network installed location of USMT and not reqire USMT to be installed on each computer.
Thanks for all your effort and it is a great tool.
Doug MacKenzie
not working – Application Error
The application failed to initialize properly (0×0000135). Click ok to terminate the application
xp sp3 english
Arthur,
- Click Start > Run, type Notepad “C:\WMA\MigAssistant.Exe.Config” where WMA is your WMA folder.
- Look for:
MigrationMaxSize- Change the value from 20480 to something higher, 81920 is around 80GB
- If you need to change the storage location…
- Look for:
MigrationNetworkLocation- Change the value to the required path
If a USB drive is attached, it will automatically be detected and you will be asked if you want to use it as the storage device, unless it 2GB or below in size. This is to prevent the prompt appearing when a small USB device is attached, like a Flash key.
Dan
Doug,
I’ll see what I can do about updating the documentation more.
Regarding the other items:
- Changing the path layout would undermine the automatic detection aspect of the Restore. It’s possible to match the username from backup to restore (since it would be the same user performing both), but computer-name could change, and the date *definitely* could change. Maybe it’s something I’ll investigate in the future but right now, I want to make the app as simple to use as possible, removing as much complication as possible.
- Again, being able to select one or all profiles keeps things simple, and definitive exclusions can still be made in the .Exe.Config file. Something I’ll look into in the future maybe.
- Exclusion of accounts older than a specified date is something I’ll definitely put in the next version. Forgot about it, thanks for pointing it out.
Running WMA from the Network is already possible, and is in the ReadMe file, but I didn’t clarify about the USMT part:
Extract the files to a local folder. It IS possible to run WMA from a network location, however this requires modifying the .NET security restrictions on each workstation you intend to run on. This can be done by running the following command from an Administrator Elevated command-prompt:
“C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol” -quiet -m -ag “LocalIntranet_Zone” -url “\\UNCPATH\WMA\App\*” FullTrust -n “Workstation Migration Assistant Assembly” -d “Grants full trust”
Where \\UNCPATH\WMA\App is the full path to the Workstation Migration Assistant
One this is done, just copy the local USMT folder to the same folder and it won’t need to be installed on every machine.
Cheers, Dan
Eli,
You don’t have the .NET Framework 2.0 installed. As per the ReadMe file:
Please note that the Workstation Migration Assistant requires the Microsoft .NET Framework 2.0 to function. If you don’t have it installed, you’ll receive an error when you try to run WMA
Dan