I’m doing a little cross-pollination today. Chris Lehr, one of my colleagues at ExtraTeam, worked up a Log Parser script that produces a report showing all the clients versions connecting to Exchange. This is very helpful to show which clients are running Office versions in your organization that should be updated prior to migration. Check out his blog post here.
Clients will always get the best experience using the latest version of Office, currently Office 2013 SP1. The best practice is to always update your clients with the latest cumulative update prior to migration. this is especially true when you’re migrating to Office 365, since most updates pertain to Office 365, Exchange Online, and Exchange 2013 compatibility.
If you find that you need to upgrade clients to a new version of Office, I recommend that you install the x86 version of Office to provide the best compatibility with add-ons and third-party products. Some customers think they need to install Office x64 on Windows x64 operating systems, but that’s not the case. See 64-bit editions of Office 2013 for details on when it makes sense to install Office x64.
If you’re an Office 365 customer, I strongly recommend checking out using the Office 2013 ProPlus software deployment that’s most likely part of your Enterprise license. This version of Office 2013 can be installed on up to 5 PCs, iPads, tablets, etc. and is always up-to-date since it’s a cloud-managed service.
It’s about time…
The Office 2007 Cumulative Update for December 2010 finally includes Exchange 2010 archive support, as well as a bunch of bug fixes. Strangely, the website for the update doesn’t list anything about this support.
Take a look at the article, “Yes Virginia, there is Exchange 2010 archive support in Outlook 2007” on the Exchange Team’s blog for details about Exchange 2010 archive support. The site also explains what Exchange archiving is and how it works with Outlook 2007.
With the release of this update, organizations with Office 2007/Outlook 2007 deployed can benefit from Exchange 2010’s archiving and retention features.
In an earlier article, I discussed how Outlook startup performance suffers when Outlook Anywhere is configured on the corporate network.
I received an email from a reader, Bruce Lane from Microsoft, who mentioned that he ran across a configuration that was causing slow Outlook startup, as well.
New to Outlook 2007 is calendar caching. This allows users to see other peoples’ calendars even if they are working offline.
The problem is that this causes a tremendous amount of client<->server traffic. The problem is especially bad if the user has many other users calendars open (more than 5 or 6). The people that were experiencing the worst problems were the admin assistants for the most senior people in the organization. They often have many calendars open.
We saw horrible start up times (3 to 4 minutes) and big lags to change views caused by the calendar caching. Luckily there is a setting in the Outlook profile to disable this feature.
Thanks very much for the tip, Bruce!