Outlook cached exchange mode not updating
HOW TO FIX THIS First check that your databases are pointing to the correct 2010 server for Default public folder database and Offline address book.In EMC Organization Configuration Client Settings tab In Windows Explorer Delete all files/directories INSIDE but not the directories themselves: C:\Program Files\Microsoft\Exchange Server\V14\Exchange OAB C:\Program Files\Microsoft\Exchange Server\V14\Client Access\OAB In EMC Server Configuration select OAB (Default Web Site) and click OK.
One of the new features in Exchange 2010 is the ability to import contact photos, store them in Active Directory against each user, then show them in both Outlook and Lync.The easiest way to accomplish this is via Group Policy Preferences.I won’t go into too much details, but basically you can configure Group Policy Preferences by using Server 2008, 2008 R2, Vista or Windows 7 Group Policy Management tools.The client extensions can be deployed easily using WSUS to earlier clients like Windows XP.After migrating from Exchange 2007 to 2010 and running co-existance for a bit, users noticed that their GAL was missing new addresses.Trying to download the Address Book: Produces an Outlook client error 0x80200049 The operation failed.
You will notice that the OAB / GAL in cached mode is out of date, but the OAB / GAL in online mode is correct.
Note: This article assumes you have already created a Public folder database on Exchange 2010.
It’s great to help identify who you’re emailing and who has emailed you, and can avoid making embarrassing mistakes.
The process to enable the photos is fairly straightforward.
You need to update the AD schema to 2008 or higher (you can still use 2003-only domain controllers, though), enable Global Catalog replication for the relevant attribute, enable the photo to be distributed through the Offline Address List, and then import small ( After extracting, copy the files to a share that can be accessed by the computers on your network, as you would for normal computer-policy MSI GPO deployments: To deploy the Outlook Social Connector to clients, now create (or modify) a Group Policy and add the MSI as an assigned package: Now, that will get the OSC out to the clients.
To ensure your users don’t have to deal with the first-launch experience (where they have to press Next, choose from a blank list of networks, then press Finish before they can use Outlook), we need to configure a couple of Registry entries.