Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Exchange Server 2013: Not quite ready for the data center

Jonathan Hassell | Feb. 8, 2013
Thinking about upgrading? Hang back at least a year before implementing this release, our expert advises.

There has been a market for third-party tools that plug in to the mail flow of a company and inspect data going out. However, that has always been an additional expense and one that comes with some complexity in terms of deployment, because it is additional code that is riding on top of an already deployed system. Now, as of 2013, data loss protection (DLP) is a feature that is built into the Exchange platform.

This allows you to set up policies that do one or more of the following:

  • Enforce boundaries by preventing or limiting transmissions between groups of users, including between groups internal to a company
  • Apply different treatment to messages sent inside a company from messages sent outside of a company
  • Stop inappropriate content from coming into a company or leaving it
  • Strip out confidential or otherwise sensitive data from transmissions
  • Archive or journal messages that are sent to or received from users or a group of users
  • Catch inbound and outbound messages and route them to a manager or administrator for inspection and approval prior to final delivery
  • Add disclaimers to messages as they enter or leave the mail flow

Limitations of Exchange Server 2013

So far, the story on Exchange Server 2013 seems pretty good. But there are some gotchas that you should be aware of during your evaluation of whether the new release is right for you.

The first issue speaks to the quality of the software overall, and even puts into question what the word "release" means in this context. "Microsoft made a decision to release all of the 2013 versions of its Office desktop applications and servers at the same time, and it released Windows 8, Windows RT and Windows Server 2012 at the same time," says Michael B. Smith, an Exchange expert, Microsoft MVP and author of the blog The Essential Exchange. "I think this decision was seriously flawed."

If you've been in IT for any length of time -- and have witnessed the ability of Microsoft and other software vendors to promise certain dates and then slip them without much trouble -- you could be forgiven for wondering how the software giant was able to achieve shipment of multiple distinct server products, working with individual product groups, using their own codebases, on the same exact day. It is certainly a cause for skepticism regarding just what "release" means.

Smith believes that several products in this wave were released before they were ready. "Exchange 2013 RTM is not ready for prime time," says Smith. "It is obvious that the products were not complete" at RTM back in October 2012.

As proof, Smith says, both Windows Server 2012 and Windows 8 had 300MB worth of patches between RTM and general availability; however, Exchange Server 2013 doesn't support interoperability with prior versions of Exchange at either RTM or general availability (GA). It is "easy to conclude that the RTM dates were artificially imposed," says Smith.


Previous Page  1  2  3  4  5  Next Page 

Sign up for Computerworld eNewsletters.