Microsoft Exchange 2010 is nearly here so I’ve just been going through some of the free e-learning that’s available (here) to see what’s new.
There have been many improvements around the Unified Messaging piece including:
SMS Notification of missed calls
Message waiting indicators
Personal Auto Attendant
Users can have voicemail transcribed into their chosen language
Voice mails are now protected from unauthorised forwarding, copying and extracting
These enhancements should lead to the UC aspects of Exchange gaining more traction. Previously they’ve been seen as quite superfluous and “nice to have” rather than a “need to have” (at least in my experience); now however the user productivity gains are apparent.
Another big one is Federated Calendar Sharing, allowing you to easily share info with 3rd party organisations, using Windows Live as the trust broker. You need an internet accessible Client Access Server (CAS) as calendar sharing is done via web services – thusno special ports need opening.
Microsoft Clustering Services are no longer needed to get High Availability (HA) with Exchange 2010.
Things to know for deployment:
Can upgrade from 2003 to 2010
AD must be at least in
Windows Server 2003 forest functionality mode
Also, you must have at least one Windows 2003 Service Pack 2 Global Catalog server in every Active Directory site that will have an Exchange 2010 server.
Note that Read-only domain controllers (RODC) and read-only global catalog (ROGC) servers are not supported.
Exchange 2010 does NOT support in place upgrades.
Read-only domain controllers (RODC) and read-only global catalog (ROGC) servers are not supported
Microsoft have made a number of changes in this area and, at least to me, they seem like great improvements. They’ve worked hard to reduce the I/O traffic and this is done via:
IOPS changed to write more data at fewer intervals
Merged I/O instances
Both of these reduce the number of operations and improving performance. Two more improvements include:
Larger cache size (32kb)
Sequential data storage reduces I/O
They have also removed the Database maintenance windows by pushing the defrag process into the background.
All that and more, along with moving diagrams and voiceovers can be found here: