1999 seems such a long time ago now, but that's when many of us first faced the need to deploy Active Directory (AD). For many companies, the need arose because Microsoft replaced the Exchange Directory Store (DS), used for Exchange 4.0 to 5.5, with Active Directory in Exchange 2000. The DS was very much like AD.
Tuesday’s EHLO post by Rob Whaley, a well-known Exchange guy who works on beta releases of the on-premises and cloud products, is all about how a remote PowerShell session connects to a mailbox on an Exchange server. Or, to use the term now popularized by the post, “mailbox anchoring”. I confess ignorance on the point as I was heretofore unaware of such a nautical reference in the context of Exchange.
Two years ago, I spoke with Perry Clarke, the development chief for Exchange (both on-premises and cloud) to discuss the current state of Exchange and how its technology was likely to evolve. We know how the influence of the cloud has affected the way that product development occurs and how quickly things now happen. I thought it would be interesting to look back on how Exchange has evolved in the period.
The ability to run searches across a mixture of Exchange mailboxes and SharePoint sites to uncover the deep and dark secrets of those who would prefer their work to go unnoticed is what, in some degree, eDiscovery is all about. Microsoft has invested heavily in the area of compliance over the last decade, with the initial work showing up in Exchange 2010 and SharePoint 2010. There was much to like in the first implementation, especially in Exchange 2010, if only because so many legal discovery actions center on email.
Some interesting discussion has flowed into my mailbox since Microsoft announced their decision to stop cleaning out the Deleted Items folder of user mailboxes in Office 365. The announcement appeared on February 20 and started a 28-day countdown to implementation.