My first upgrade a Windows Vista to Windows Seven was relatively quiet, While it took several hours. The ideal is to always do a clean install instead of upgrading, but I did not have time and patience for it, so I opted for the upgrade. A few problems occurred, Daemon Tools needed to be reinstalled, the program you login with fingerprint stopped working, some drivers needed to be updated, but it was only.
A second attempt to update occurred on a desktop with Windows Vista x64 and was far less quiet, several problems interrupted the update in half and made the system be restored to Vista. After many attempts the update has completed but the result was a Windows 7 x64 totally unstable, showing blue screens of death (blue screen of death, BSOD) Frequent. So I opted to do a clean install, but would like to migrate data from the old system (user accounts, documents, program settings, etc.) to avoid having to do it all again. For that went behind the USMT (Windows User State Migration Tool), which I 've talked in an article here on Skooter Blog.
When searching on the USMT, I realized that he is now at version 4.0 (I had that was still the 3.1), but Microsoft decided to complicate things a bit more and not available to download separately tool, you must download the Windows Automated Installation Kit (Windows AIK, or Automated Installation Kit for Windows, in Portuguese), containing the USMT 4.0 among other tools that facilitate upgrading from Windows (especially in companies or other environments with large number of machines). It is interesting, but download an ISO of up to 1GB can be tricky for those who do not have a decent broadband (in other words, 99,9% of Brazilian).
Downloaded and installed the Windows AIK, I noticed the major changes of the new USMT 4.0: before it was necessary to use scanstate still with the old operating system to save the settings in a separate location, upgrade the system and then use the loadstate settings to migrate to the new system. Now it's much easier, you can install Windows Seven before recording settings, he should keep the old files in a folder called Windows.old, of course this will only happen if you do not choose to format the partition during installation. Inside the folder Windows.old folders are stored Windows, the Program Files (from 32 and 64 bits), user profiles, users' folders and everything else you had on your old Windows. Then you can use the scanstate pointing it to that folder and it will prepare the migration, then just use the loadstate upload them to the new system. The intermediate location can now store only hardlinks the files to be migrated, in other words, process saves you a read / write many migrating files directly from Windows.old to new location, and this makes the whole process much faster. Note that there are two versions of the program: e x86 amd64. If your system is 64 bits you vai amd64, even if your processor is Intel.
But not everything was perfect, in the middle of execution loadstate I saw seemed to be standing ele, using processor and HD, but without leaving your seat. Looking LOG operation realized he was trying to create something in a temporary folder in my user (what was logged by running the program), could not and kept retrying indefinitely. I have checked the folder and just saw that it was over 65.000 files. I do not know if I was running into some limit number of files per folder NTFS (there?) or some other limit any, but just in case I decided to delete all temporary (that did not share error) and aí or process continuou. The folder just refilling and had to delete everything again even before you finish running loadstate, and then finally everything went right.
Note that you must specify what will be migrated through XML files. Fortunately the system brings 3 standards files: MigUser.xml, MigDocs.xml e MigApp.xml, configurations containing a good amount of software (especially Microsoft). Some unfortunately are left out, the administrator can create their own XML files, but this should be quite laborious and only worth it for system administrators who will migrate many machines with the same script. For the average user will probably work less manually migrate what was missing. Just to cite one example: Mozilla Firefox migrated seamlessly with USMT 4.0, with their plugins and everything else, Mozilla Thunderbird but I had to manually migrate. Fortunately this is simple, just copy pastes as C:\UsersNome_do_usuarioAppDataLocalThunderbird and C:\UsersNome_do_usuarioAppDataRoamingThunderbird the old system to the new (or Windows.old to the local quoted).
Conclude that the use of USMT 4.0 vale a pena. It is half-way between an upgrade and a clean install, Then remembering that the installation of data migration with USMT is still considered a new installation brings the same benefits and the same: registry cleaner, System lightest, etc.