On April 2, 2013, Microsoft release Cumulative Update 1 for Exchange Server 2013. For details about this update visit Description of Cumulative Update 1 for Exchange Server 2013.
The RTM version of Exchange 2013 is Version 15.0 (Build 516.32). This CU will update the system to Version 15.0 (Build 620.29).
In my previous post on Upgrading from Exchange 2010 to Exchange 2013 on Windows 2012 (Part 1), we covered the prerequisites to installing Exchange 2013 in your Exchange 2010 environment. In this article we will cover installing Exchange 2013 and configuring it for coexistence. For simplicity’s sake, I will show screenshots from a single “all-in-one” server installation, since they do not vary much.
Microsoft announced the release of Exchange 2013 last fall, but this was not very useful to most of us, because there was no support for previous versions of Exchange until new Service Packs and Hotfixes were available. In other words, you could not install Exchange 2013 into your current Exchange organization. In February Microsoft finally released Exchange 2007 SP3 RU10 and Exchange 2010 SP3, to enable coexistence between the platforms. As is typical of Microsoft, they support an N-2 upgrade path. This means you can upgrade to 2013 from two versions back. Exchange 2003 (and prior) version will not allow upgrade to Exchange 2013. In-place upgrades of Exchange 2007 and 2010 versions are not supported either. This is typical and even if it was supported I would never recommend it. It’s nice to start from scratch and deploy a new Exchange environment and apply the things you’ve learned from previous installs.
Well, I’ve run into multiple issues with this task, so I might as well write a post on how to successfully update your Exchange 2010 Edge server to Service Pack 3. In my scenario, I’m running a single server with the following services:
Apparently, I was enjoying my birthday too much to notice that Microsoft released the New Office Visio Stencils. This stencil contains more than 300 icons to help you create visual representations of Microsoft Office or Microsoft Office 365 deployments including Microsoft Exchange Server 2013, Microsoft Lync Server 2013, and Microsoft SharePoint Server 2013.
The Exchange 2007/2010 Offline Address Book (OAB) can be a pain to manage in environments where users expect instant access to updates to the Global Address List. Outlook 2007/2010 clients running in Cached Mode use the Offline Address Book by default for all address lookups. This means when a new user is added to your domain and mailbox enabled they will not appear in the "GAL" for Outlook clients until the OAB generation and distribution process has run it’s course. The following article explains how the OABGen and Web-Distribution process works in Exchange 2007 and 2010.
The star of last year’s product roadmap was Office 365. Microsoft this year looks likely to pivot from the public cloud to the private cloud, while also shipping staples like SQL Server and releasing major betas — and possibly final versions — of blockbusters including Windows 8 tablet, client and server, and Office 15.