Microsoft Exchange 2010

So we have had Exchange 2010 for a little over a month and so far hasn’t given us too many problems. Migration was an experience I don’t want to repeat in a hurry but the EDA or Exchange Deployment Assistant greased the wheels a bit.

Here are some of our findings so far. Bearing in mind we have only had the system live a few weeks and we’re bound to have plenty yet to discover. So far our time with the platform has been positive.

• OWA interoperability – Outlook Web Access now plays nicely with others. Not only does it offer almost everything Outlook 2010 is supposed to, you can now also use it with other browsers. Microsoft have opened it up so it works well in Opera, Firefox and even Safari. A very good development in a platform, especially for an organization who uses multiple operating systems.
• No client necessary – While we’re waiting for Office 2010 for Outlook, we found we don’t actually need it yet. We will to enjoy the other features, but for now we can use it happily without it. Even down to the sounds for calendar alerts.
• Availability – With the death of local replication, the new Database Availability Grouping is a godsend. Multiple versions of databases on multiple machines allows our availability to hit 99.99%. It took a while to get right, but when we did there were sighs of relief all round.
• Self Service - The bane of our lives is slowly easing. The new Exchange Control Panel means the users can manage their own groups, addresses, holiday messages, rules, virus protection and much more. They can use it through a web page and manage many of the tasks that used to take up the majority of our time.
• Exchange Test Tool – So simple yet so effective. This is a network or internet tool that allows us to test different facets of a rollout before making them live. From it we can test SMTP messaging, ActiveSync and Outlook Anywhere. Useful.
• Improved views – Not only do we now have the conversation view, which allows for message threading for longer conversations but we no longer have the annoying previous and next buttons. Now we have scroll bars, which makes the whole message navigation thing a breeze. If we have long running support cases, this view makes it easy to see who said what, and when. That way we don’t repeat what someone has just said, or ask the user to try something twice. Happier user, happier us.

We won’t get to fully utilize the system until Outlook 2010 arrives, but what we have seen so far is positive. The Outlook Web Access is a good alternative for message management, and offers much more than the old version. The fact that we don’t have to use it with Internet Explorer is a definite bonus.

With the release somewhere on the horizon, it would be a good time to discuss the prerequisites for deployment. Those companies who are planning to be early adopters are probably already well aware of the list of requirements in order to launch it successfully.

There are two main categories of requirements for the new system. Active directory and the ones needed for Exchange itself.

For the active directory part, all the domain controllers in the organization will need to run 64 bit versions of Windows, preferably Server 2003 SP2 and above. If you use a forest, that should also be at least the same level. Exchange will only work with 64 bit architecture and has been built from the ground up to only use it. This may mean operating system upgrades before you even open the Exchange package.

The Exchange site of the migration also has its own prerequisites. The entire platform must be at a level higher than Exchange 2003 SP2. If they are running Exchange 2007, that also must have Service Pack 2 installed to work properly.

To transition effectively to Exchange 2010 it is best to build the new infrastructure beside the existing one. It is also best to start at the internet facing side, with a Client Access Server (CAS). To use Exchange 2010 you need to build new CAS servers, you can’t upgrade existing ones. The new CAS has to live alongside the existing one while the business still has mailboxes on the old system. The old CAS can be retired once the migration has completed.

To get them working, the certificate has to be propagated from the old CAS to the new one, then a new one has to be acquired for the new on and shared with the old. This will allow mail to be redirected between the two CAS servers depending on where the destination mailbox is housed. If a client connected to the Exchange 2010 CAS contacts a mailbox on the old CAS, the new CAS will redirect the data to the old to complete the transaction, and vice versa.

Next the new mailbox servers should be built and configured to sit alongside the legacy ones. Both servers will need to be running in order to move mailboxes between them. Once the mailbox transition is complete, the old mailbox server can be retired. Fortunately this once laborious task can now be automated with the new Online Move Mailbox tool. This process means the absolute minimum downtime for users as the data is replicated between servers and the active directory replication takes place.

The only server you can really replace at the outset is the edge server. Once you have subscribed it to the Exchange 2010 Hub Server it should work normally.

This is only an overview of what it to be a time consuming and complicated migration process. Proper planning should always be done before even removing the wrapping from the new hardware.

Microsoft unveiled Exchange Server 2010, which has been in beta testing since April, at its TechEd conference in Berlin today, and showed it working with Outlook 2010.  Exchange 2010 is the company’s latest server technology for on-premise software deployments, but it also incorporates many features aimed at web and online services. It has a new, integrated email archive designed to help companies increase compliance and respond quickly to legal and e-discovery concerns, and there are now previews of voice mails in Microsoft Outlook. It’s also very apparent that Microsoft officials are aware of the new kinds of competition that Exchange is facing.

It was clear from the product positioning that Microsoft is feeling the heat (GigaOm Pro, sub. req’d) from enterprise adoption of tools from Google, such as Gmail, many of which are free or available in low-cost versions for business use. Cisco — a long-time Microsoft partner — is also taking aim at Microsoft Exchange with a new enterprise email service, WebEx Email. Steve Elop, president of Microsoft’s business solutions division, made numerous mentions of cost savings that enterprises can purportedly reap with Exchange 2010, and there was much focus on the email archiving and legal compliance features to be found in both it and Outlook 2010. Among cost-saving citations, Elop noted that companies can now run Exchange Server on lower-cost storage platforms than SANs.

Indeed, Google CEO Eric Schmidt has been very vocal recently about that company’s “next billion-dollar opportunities” when it comes to delivering web-hosted applications and other tools that can serve as alternatives to Microsoft’s solutions — and its licensing fees. In fact, many of Schmidt’s recent comments are decidedly anti-Microsoft.

No doubt with Google’s focus on online-hosted applications in mind, many new features in Exchange and Outlook are designed to allow email inboxes and archives to migrate easily between on-premise deployments and online-hosted ones. For example, a demonstration at the Berlin event included taking an existing on-premise email inbox and transferring it to a web-hosted implementation. Exchange Server is available now for trial use, here (Microsoft Silverlight req’d.).

Microsoft officials also announced that the company is acquiring SourceGear’s Teamprise technology. Teamprise allows Java and Eclipse developers to create applications with Microsoft’s Visual Studio. We’ll be on the lookout for more announcements slated to arrive at TechEd this week and will update you as they come in. Stay tuned.