Over the weekend I was given the Microsoft MVP award for a second time!
Thanks to everyone who follows this blog and attends my Exchange Connections sessions; its because of you I am able to wear this badge of honor for another year.
Needless to say:
The EHLO blog posted an important announcement today regarding Exchange 2010 in hosted environments. Previously, for Microsoft to support your multi-tenant deployment of Exchange 2010, you had to build a whole new forest and use a special setup.com /hosting installation process. There were other significant limitations as well.
The strict support statement, combined with Microsoft’s release of Office 365 really came as a one-two punch to some of the smaller companies who wished to host Exchange but could not afford to employ developers and/or take the risk of forfeiting support from Microsoft. It seemed like Microsoft may have lost some love for their hosting partners.
With the Exchange 2010 SP2 update (scheduled to launch later this year), you will be able to host a multi-tenant environment with a regular deployment of Exchange. This is made possible by the new Address Book Policies and specific configurations to be documented with the SP2 release.
Personally, I’d look at this very carefully before deploying any new /hosting environments. This (SP2) seems like a much simpler deployment to maintain.
Exchange Microsoft Remote Connectivity Analyzer has been an essential tool for Exchange administrators since it’s initial release. This site will attempt to connect to your environment through a variety of methods to help you ensure all is well, or troubleshoot issues related to client connectivity.
If you haven’t seen this tool, you should definitely check it out:
http://www.TestExchangeConnectivity.com (or the short link: http://exrca.com)
Last week, Microsoft updated this tool to include support for Office 365. While you wouldn’t actually be troubleshooting Microsoft’s Exchange environment, this new tab allows you to validate your URLs and configurations related to the “Rich-Coexistence” scenario.
Another interesting fact: Microsoft announced plans to incorporate other products into this tool, beyond Exchange Server.
For a complete list of changes in this version, see the release notes.
In case you’ve been living under a rock with the Geico guy:
This is not just another product announcement. If your work is to support Microsoft technologies, this is something you must learn about…
Recently, I had a chance to chat with Richard Campbell and Greg Hughes on the popular RunAS Radio Show. The topic was Information Rights Management and how it relates to Exchange Server. This was also a feature I demonstrated on stage at the Exchange Connections event in Orlando earlier this year.
If you’re not sure what IRM is or does, or if you wish to learn more about it, be sure to tune in on May 4th to listen to show #210!
Exchange Connections is an event held twice a year for the purpose of learning about Exchange Server and meeting other professionals working with the technology. It is held alongside several other “Connections” events and has always been a lot of fun!
For a list of sessions checkout this link:
If you’re planning on attending, please come say hello. I will be delivering the following sessions:
|EXC13: Forefront TMG Client Access Publication and Edge Transport Integration
During this session, Mike will cover two aspects of Exchange and TMG integration. In the beginning, he’ll discuss the installation procedures and configuration requirements of TMG and Edge’s residence on the same server. In the second half, he’ll demonstrate the steps of publishing Exchange client access through TMG.
|EXC14: Information Rights Management Explored
During this session, we will discuss and then demo IRM and S/MIME, the infrastructure requirements for both, the pros and cons, and configuration.
|EXC15: Office 365
This session will cover capabilities, migration, and administration of the Office 365 and Live@EDU environments. It will include demonstrations and best practices.
A while back, I complained about the difficulty in obtaining the necessary hotfixes for Exchange 2010’s Service Pack 1. I just took a peek at the “Hotfixes and Security Updates included in Windows 7 and Windows 2008 R2 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=194725)” article and verified all necessary hotfixes are within.
So if you’re planning on Installing Exchange 2010 SP1, it may save you time to install Windows 2008 R2 Service Pack 1 first.