Do you mean AutoComplete/nk2 cache? If so, that should now be part of the user mailbox, i.e. Outlook should no longer reference the nk2 file.
I set this up years ago, but I seem to recall that there was a condition case where the user's new profile coincided with the name of the old OST file and that caused some weirdness, so we just removed the entire folder. -Aakash Shah From: [email protected] [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Friday, March 6, 2015 5:03 PM To: [email protected] Subject: [NTSysADM] RE: OT Exchange issues. Outlook 2010. Do you think I can skip number 2? That would delete their auto suggest, they hate that. ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]] on behalf of Aakash Shah [[email protected]] Sent: Friday, March 06, 2015 7:58 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: OT Exchange issues. That's the approach we've taken in the past for a different situation. 1. This will delete the Mapi profiles: reg delete "HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem" /f 2. This will delete the cached items stored on the file system: rd "%USERPROFILE%\Local Settings\Application Data\Microsoft\Outlook " /s /q 3. This will make Outlook act like it is running for the first time: reg add "HKCU\Software\Microsoft\Office\%OutlookVer%\Outlook\Setup" /v First-Run /t REG_BINARY /d "00" /f %OutlookVer% needs to be your version number, i.e. Outlook 2013 would be "15.0" -Aakash Shah From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Friday, March 6, 2015 4:45 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: OT Exchange issues. Yeah, that's probably how I would handle it. Find the actual iMAPIprop in the profile in the registry and then yank the profile from the registry. You'll just have to search a registry for the relevant iMAPIprop, I sure don't remember it off the top of my head. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Friday, March 6, 2015 7:36 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: OT Exchange issues. Tips to nuke these profiles if I have to go that route? Logon script to delete it then let Outlook recreate on startup...my users are used to creating their own profile.... ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]] on behalf of Michael B. Smith [[email protected]] Sent: Friday, March 06, 2015 7:30 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: OT Exchange issues. Autodiscover is far more complicated than most people think it is. :P But this is happening because there is a hard reference to the old server in the user's MAPI profile. The RECOMMENDED way to do this process is to swap everything to the new server, but leave the old one up while clients are redirected and get sent to the new server. The clients MAPI profiles will automatically be updated. After a week (or what time is appropriate to your environment) then remove the old server. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Friday, March 6, 2015 7:18 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] RE: OT Exchange issues. Delete the Outlook profile and create a new one and all is well. Need to figure a better way, but it's a start. ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]] on behalf of Kennedy, Jim [[email protected]] Sent: Friday, March 06, 2015 7:13 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] OT Exchange issues. Exchange list is really quiet, struggling with an issue here. Sorry. I rolled up a new Exchange 2010 CAS/Hub and decommissioned the old one. Transferred all the URL's, and swapped IP's. Internal and external flow is great, OWA is fine, external OWA and Active Sync is fine. Internal existing Outlook users are broke. A regular user cannot find the new server when they start up, and domain admin with an email box can. Feels like permissions on Autodiscover.xml or auth on Autodiscover but I have check that a million times.
