[SOLVED] Cannot migrate Outlook 2010 Autocomplete cache

[drjones]

NEVERMIND, I think seriously the 6th time I tried it, it finally "took"

Why did microsoft make this process so crappy???



. .
.

I've dealt with Outlook 2010 before and migrating the funky new autocomplete cache.....here's the deal that has me stumped:

I migrated a client (single user) from one exchange service to another.

I exported his mailbox to PST, imported it into the new exchange profile, then went to copy the name of the newly created autocomplete, and paste it into the old one, which is almost 1mb in size.

Once I do this and launch outlook, it deletes everything and resets the cache size back to 2kb, down from 938kb.

I've tried it several times, have quit & re-launched outlook....no dice....what am I missing??

Thanks!

 

[Frick]

An easy outlook auto complete solution after migration is to disable the network adapter, then create a new email and address it to everyone in their contact list, and send it. Since there is no network connection it will be put in the outbox. Delete the email and enable the network and you are done. Test the auto complete and it should work fine.

 

[JustInspired]

An easy outlook auto complete solution after migration is to disable the network adapter, then create a new email and address it to everyone in their contact list, and send it. Since there is no network connection it will be put in the outbox. Delete the email and enable the network and you are done. Test the auto complete and it should work fine.

Most of the missing autocomplete complaints I've had are about entries that are NOT in the Contacts.
FABS usually does a perfect job for us when it comes to PST and nk2 file migration.

 

[dipper]

I had heaps of problems but now use NKEdit fro Nirsoft - http://www.nirsoft.net/utils/outlook_nk2_edit.html

Just create the autocomplete cache (.dat) file and then use this program to import the old .dat or nk2 file and then export it to the message store (under the file menu).

 

[YeOldeStonecat]

I just copy the old NK2 from the old computer (or old profile) to the correct location for it in the new computers operating system....and if Outlook already has been configured to the new Exchange server...launch Outlook once...let it sit for a minute or three...and it automatically imports the NK2 and builds it into the mailbox store on the Exchange server (new default setting since Office 2010). Don't need to manually go through steps importing it.

When you setup Outlook for the first time to an existing mailbox on Exchange...and it's busy building that OST file (offline cache) for the first time...it may take a few minutes (at least) to complete that process...before it moves onto importing the NK2 automatically. I think a lot of people shut down Outlook before it's been fully synced..and assume the nickname cache didn't auto import....but they just didn't give it a chance yet. With big mailboxes..that first time local cache (OST) creation and sync can take a while...NK2 comes after that.

 

[drjones]

I'm fully familiar with Nk2 - those are super easy.

Why MS did this "roamAutocomplete" garbage for 2010 is beyond me.

"Oh, you want your autocomplete cache? Sure, thats' asdkjhfq928374 dsy90a987"



Seems that in 2013 they updated it at least so that it's somehow integrated into the .PST.

I have also seen that outlook doesn't even create the autocomplete / .nk2, until you open a new email & type a few characters into the "to" field.

In any case, thanks for the help.

 

[Altster]

NEVERMIND, I think seriously the 6th time I tried it, it finally "took"

Why did microsoft make this process so crappy???

Simply "because they can!"

 

[drjones]

....brought to you by the same mental midgets who created windows 8, I'm sure!