Categories Networking Windows Virtualization Security Hardware Storage

Categories Networking Windows Virtualization Security Hardware Storage & Backup Mobile Cloud Programming Databases Software DevOps More... Resources How-Tos Scripts Videos Jobs IT Service Providers Vendor Pages SpiceCorps ice cream cabinet Voice of IT Blog Help New Discussion
Categories Networking Windows Virtualization Security Hardware Storage & Backup Mobile Cloud Programming Databases Software DevOps More... Resources How-Tos Scripts Videos Jobs IT Service Providers Vendor Pages SpiceCorps Voice of IT Blog Help New Discussion Start Inventory Help Desk Product Reviews App Center
See more RELATED PROJECTS
Here's my problem: When in cached mode, I am unable to see new users/DLs in the global address book. I know that it takes 24 hours or more to update the address book while in cached mode, but it's been almost a week now. When I disable cached mode, I see the updated address book. If I enable it - once again, the updates are gone. This happens on more than one computer/user account.
I had the same issue, I don't handle the exchange server, I ended up leaving the "cached mode" checkmark box unchecked and have had no issues. Unless ice cream cabinet you have a need for it I would uncheck it.
-Jay
Closing Outlook and deleting the client's OAB (Offline Address Book) files (located in either \%AppData%\Local\Microsoft\Outlook\Offline Address ice cream cabinet Books for Outlook 2010 or the *.OAB files in \%AppData%\Local\Microsoft\Outlook\ for Outlook 2007) will fix this for the client. Restart Outlook and that will pull a fresh set of contacts from the GAL to effectively rebuild the OAB on the client.
The "Download Full Address Book" option in the Send/Receive drop down menu in Outlook is meant to force the client to update the local address book from exchange too - but I've never had any great success ice cream cabinet with that function.
Sushi, In discussing this, let me say that I am talking about Exchange 2k3. We are moving to 2010 in a few months ice cream cabinet but we've encountered similar ice cream cabinet issues and if I'm not mistaken, the best solution I've discovered comes in two parts: first part is client side (Outlook) and that is to disable cached mode. That is typically intended for users that do not have a constant network connection and do not receive GAL updates frequently (presumably on the every 12-24 hour default schedule set by the Exchange server). We have found a few other benefits from disabling cached mode as well. The second part is on your Exchange server, right-click and run "Update Now" on the Recipient Update Service (you should have two entries there-one for the 'enterprise' and one for your actual domain name) on the right-hand pane of each item. That forces the RUS to poll your AD servers (global catalog servers) for changes and publishes them to the GAL, then that is pushed down to the clients (Outlook) automagically since they are not in cached mode and voila, all the new changes should ice cream cabinet be represented. However, if you are having issues with certains things NOT showing in cached mode, Matt is right: your best bet is to blow away the existing OAB and force a fresh d'load of the OAB. But I strongly discourage cached mode for any system ice cream cabinet that has a constant or relatively constant network connection (MS supports this as well). It is intended only for certain circumstances. Hope this helps!
Just ice cream cabinet to clarify, the address book does get updated both automatically and manually with no errors. The problem is that the resulting updates aren't displayed in cached mode, they only show with cached mode disabled. I will try deleting the local OAB file, and I have a suspicion that it will work. Unfortunately, this isn't a practical solution when dealing with hundreds of users :(
Well, I found the root cause of my issue. It turns out that earlier this month the Microsoft Exchange File Distribution service stopped running on our CAS server. I restarted ice cream cabinet it and ran the following command to initiate the update: Update-FileDistributionService - Identify <insert your CAS server hostname>.
Text
Bottleneck issues on wireless network Networking
We are having some issues with client ice cream cabinet devices slowing down to a crawl when they access the Internet. Should we be thinking about putting an AP in every classroom ice cream cabinet (as opposed to hallways) to alleviate ice cream cabinet some of these issues?
First Name