I had to setup a new Windows 10 machine for someone this week. It took 4hrs to install the updates, on a high speed ethernet connection. That was not the download time, no, it was all the rebooting and getting to 100% and the starting at 1% again.
Finally got it sorted and hit the next problem, they wanted Outlook (Office 365) migrated, including their eight email accounts, grrr.
Microsoft's official line is "You cannot transfer account settings only data files", but digging deeper there was a rumour. The rumour stated that Microsoft did not want to support people transferring settings as it was non-trivial. Finally I found that the key to transferring settings from one machine to another was to ensure it was with the same version of Outlook
. Easy it was all Office 365.
You have to export and import a specific set of Registry keys, but that is just
export keys to file
import keys from file
The keys you need are everything from
The slight problem I had was the old machine had the keys in
and the new install had created
A quick Search and Replace in the .reg file fixed that. And the crossing of fingers, still, Microsoft will never know!
Now the final (OK, second to last) piece of the puzzle. The process of exporting and importing your Outlook settings does not
include your passwords. Annoyingly it does include the setting "Remember my password" so, Outlook then fails to ask you for your password because the nothing it has is deemed correct.
The passwords mush be somewhere on the system ...
bit more Googling and bit of luck and recognised the domain name http://www.nirsoft.net
Digging around a bit, there is a lot
of great free
tools on that site, and found this
It is incredibly simple. Download and run, no install necessary. Then select the defaults and let it run a for a minute or so. The result is every piece of encrypted data in your registry is decrypted and displayed!
Now, you might think L33t Hakorz, but, this utility simply uses the API Microsoft created for this job. The clever bit is it knows how to find the keys to decrypt, which is detailed on the site as a specific HEX signature. If you are logged in, I was, then it just gets the data.
There were 300 keys found, but, I recognised the passwords pretty quickly. The problem now was I had a list of eight passwords but did not know which accounts they linked to. The output does list the registry keys so I just went in to the registry found each one in turn, they had GUID type names, expanded each one and read the "Account Name" key!
The final, final steps was to copy the .PST files, and .OST for IMAP accounts and place them in exactly the same path
as the old machine.
I do not think Outlook on the new machine had any idea it had been hoodwinked.