Is anyone out there? Is there anything you'd like to see a blog post about? I can’t guarantee that we will answer your question but I can promise that we will try. Drop a comment and let us know.
I'm USMT user, I try to use the following command to migrate XP to XP, but not just the login account was migrated, some other local accounts were copy to the intermediate storage, which cause the loadstate fail. please help on this, thanks!
scanstate o: /targetxp /i:migsys.xml /i:migapp.xml /i:miguser.xml /i:migabc.xml /o /c /v:13 /uel:0 /localonly /l:scan.log /efs:decryptcopy /nocompress
loadstate o: /i:migsys.xml /i:migapp.xml /i:miguser.xml /i:migabc.xml /c /v:13 /uel:0 /l:load.log /nocompress
And one more thing is some users will encounter the duplicate files in target PC, just like source PC has abc.bmp file, after the migration, then target PC will get abc.bmp and abc(1).bmp. do you have any idea?
Wouldn't mind seeing some information posted about best practice around config.xml and how to understand the components in the manifest dll files. ie. some of the titles are not clear for users who are starting out with automated migrations.
I would like to have a library of custom.xml fragments, from where I can choose snippets to migrate applications, which are not covered by default.
E.g. the user templates of Word 2000 are not migrated be default.
I second the comment about config.xml. Does it help reduce scan times? When would it be best to use it?
I would like to see some information on when and how conditions are processed. I have had a few cases where different version of software was used and files needed to be migrated during a reimage.
RelativeMove works and this is easy to do. However, I have run into some cases where you do not know the version of the software that will be installed after the reimage and software install. USMT does not seem to process condition statements on the loadstate only on the scanstate?
Could you give us some insight in to why printers are not migrated from xp to xp and any thoughts on best practices for doing so? I also would like to see more information about config.xml. Other than that I'd like to offer my thanks for an excellent tool.
I would LOVE to see a repository for USMT. Sample XML configs, custom scripts, batch files, etc. I believe that he community would benefit so much from this. I know that I have struggled with the documentation and if I saw some sample configs that accomplished similar tasks that I wished to accomplish, it would be a major help. It can also benefit others by saving a ton of time. If someone has already created and posted a the XML for migrating an application you need to migrate, then you just saved a few minutes (or hours!) work.
I too would like to see a place to see XML code that other have created. I visit many customers and help them with desktop deployment for XP or Vista and I've had to write several custom USMT XML code to capture specific information. I'm sure people on this blog would benefit from what I've done and I too will benefit from seeing what others have done.
Writing custom USMT code is challenging with many hours to troubleshoot and get it just right.
What I'd really like to see in future updates to the tool is a viewer to browse through the .mig files. I got USMT3.0.1 running with a DOS read-response thing going on that would build the switches and parameters of the scanstate and loadtstates, depending on what menu options the person chooses. Now it's been embraced by our legal dataa retention department as a legitimate alternative form of data capture to Ghost, and the only thing holding us back is that there is no method to view contents of the compressed mig files without loadstating it back down onto a host machine.
Frankly I'm just happy you guys have a site up now :)
I'd like to see some USMT tweaking tutorials...
For example: I would like to be able to perform a scan on a PC that will migrate all the usual data from the one specific user and migrate the non-profile data - but without going near any other profiles.
Usually the files are migrated from other profiles because their file extensions are included in the MigUser.xml, so even though USMT in this case will only migrate the PROFILE I want, it will still create other profile folders and populate them with the migrated filetypes it brought over... thus giving end-users the impression that I brought over their long lost colleagues' stuff over also.
I'm not sure if I'm conveying that adequately...
I know this post is kinda late, but I just found the site. I'm not a big user of USMT, but will be in the future. From past experience I have never been able to figure out if you could just get a trial run w/o having to actually backup the user data. Just a log file that lists what files and settings would be backed up would help tweak an XML to make sure you caught everything.
Hi, I wonder if I can use USMT to run scheduled backup of users files to a NAS, is it recommended?? If it so can you give me some ideas? Like, how to avoid certain files extensions, etc. And the most important, Can I do Shadow Copies of locked files you know like outlook.pst. Thank you.
Hello, we have been upgrading our machines from XP to Win7 and using USMT for user state migration, and everything has worked beautifully! Until lastnight. This one laptop is giving us a hard time with the restore process. We keep getting error 34 even when using our highest admin rights. I have tried to restore it using command promt with my admin account (run as different user). I have tried the command promt as an administrator and with my email enabled admin account. AND I have tried going directly to the server and running the RESTORE.cmd from there. One thing I should mention although no one in my shop thinks it's a problem. We were backing up and restoring to the same laptop and changed the name of the laptop before the restore was run. However I have tried using both the new and old computer names as the source computer name.
Using gmail and outlook, Outlook sometime (in around 20% of the cases) hangs in the process of "loading profile" after user has been migrated
to a new system.
I have been reading that the success rate of USMT can be enhanced by doing it offline. So... I am testing a solution to boot the source PC up
with WinPE through our PXE-booting solution, and before deploying the new OS, we are doing a USMT scanstate like this:
"\\Intserv01\usmt\x86\Scanstate.exe" \\intserv01\usmt\%computername% /ui:* /i:"\\Intserv01\usmt\x86\migdocs.xml" /i:"\\Intserv01\usmt
\x86\miguser.xml" /i:"\\Intserv01\usmt\x86\migapp.xml" /o /c /vsc /offlinewindir:d:\Windows /targetWindows7
Now... because the WinPE is not part of the domain, the SID's are migrated... so when doing a loadstate on the target:
set /p brugernavn= "Tast brugernavn (udelad domainname drc-ad.dk)= "
set /p maskinnavn= "Tast maskinnavn (som den hed under forste USMT-korsel altsaa uden W7)= "
"\\Intserv01\usmt\x86\Loadstate.exe" \\intserv01\usmt\%maskinnavn% /ui:* /i:"\\Intserv01\usmt\x86\migdocs.xml" /i:"\\Intserv01\usmt
\x86\miguser.xml" /i:"\\Intserv01\usmt\x86\migapp.xml" /l:C:\Users\Public\Documents\USMTLOG\USMTlog.txt
the user is not migrated back when typing the "brugernavn" (Danish for "username") like "\"
I guess that typing the SID would work (even though I have not tried it yet), but I would prefer typing the username instead.
What would be the best approach to accomplish this?