Issue link: https://epubs.iltanet.org/i/27653
Fully hosted implementation of MS Exchange: office 365 admin@ user@ admin@ user@ domain controller MX Record • A directory synchronization server is placed on-location to facilitate AD sync and mailbox migrations • MX records will be pointed to the new 365 cloud, where ldap and Powershell are fully available • The communication TCP/UPD ports are available Pros: The benefit of such a configuration is that the systems run on the latest version of Microsoft Exchange, and migration of users’ mailboxes can be done with minimal downtime. In addition, upgrades to the OS version and Web-driven management tools allow Microsoft servers to do the heavy-duty I/O — like mail queuing and delivery, content indexing, and e-discovery searches — instead of putting that load on inhouse servers. Other features include voicemail with unified 40 Exchange 2010 ILTA White Paper messaging, retention policies and legal hold, Exchange Control Panel, Free/Busy coexistence, cross-premises management and, of course, hardware cost savings for IT budgets. The Microsoft Office 365 staff will also do patches, monitoring, replication/backups and archiving. Cons: With this implementation, you lose control of your data security and privacy. Another potential risk is that third-party application integration becomes more complicated for IT, and it does not include the BlackBerry piece (although Microsoft has started communication with Research In Motion to host BlackBerry servers for customers on the Cloud). We are also no clearer on how e-discovery data will impact the legal search for litigation cases. Also, troubleshooting of e-mail problems becomes more complicated since you have to involve Microsoft support in order to address inbound/outbound