Outlook client profile updating utility
As the usual disclaimer goes, I will not be held responsible if anything goes wrong with your computer or hardware or software, or causes you to suffer any loss of any sorts, so do backup your data if you want to go ahead.
Ok, now that we have got the disclaimer out of the way: First step you would need to tackle would be the secure boot that is offered on the newer hardware and Windows 8.
The reason for this is simple: Outlook profiles are coded to look for a mailbox in a certain group and on a certain server.
To deal with this issue, Microsoft has written a command-line tool called Ex Profre -- the Exchange Profile Update Tool, which Updates Outlook profiles after you move mailboxes across Exchange organizations or administrative groups.
Yet, for some reasons, there are still users (like myself) who are not able to use the newer Cisco Any Connect, as it might not be supported by their existing VPN infrastructure or some other reasons.
Faced with similar issue, I searched for possible solutions online and tried different ways of overcoming the issues, which is often a hit and miss affair.
The Priasoft Profile Update Manager, a core component of the Priasoft Migration Suite for Exchange, is a powerful Migration and Monitoring application used to automate Outlook client profile migration.
Running mixed versions of Outlook, Windows, and service packs is no problem!
The tool gleans information from both Active Directory and the current default Outlook profile to determine where a current user's mailbox is being hosted (via an X.500 e-mail address lookup), backs up a user's current profile, and then attempts to modify it with the newly-researched information.
In the event the changes fail, a user can restore the old profile (the backup is saved under the name " Ex Profre runs only on Windows Server 2000/2003 and XP.
Exprofre also cannot be run on a Terminal Server with multiple users; the user profile must be deleted and recreated from scratch to work there.
Don’t fall victim to an unsuccessful Exchange migration using inferior solutions or native tools.
In today’s Microsoft Windows network we almost always seem to find a mix of Windows XP, 2000, 2003, 7, 10, and 2012 to support, perhaps all with various levels of service packs, and generally to make matters worse we have mixed versions of Outlook 97, 98, 2000, 2003, 2010, 2013, and 2016.