Additions and Subtractions The primary design goal was for simplicity of scale, hardware utilization, and failure isolation. Microsoft Exchange Team Exchange Version Exchange Server 2003 and earlier versions Exchange 2007 Exchange 2010 Hosted / Cloud / Hybrid Exchange Organization Coexistence Not supported Supported Supported Not supported with Exchange 2013 Preview. Coexistence with Exchange 2007 and Exchange 2010 will be supported with Exchange 2013 RTM Exchange 2013 Deployment Assistant Website: http://technet.microsoft.com/en-us/exdeploy2013/checklist?state=1119-w-aabkaqaaqaaicq%7e%7e 1
Exchange Administration Center Exchange Architecture Revisions A New Managed Store Modern Public Folders Lots of PowerShell cmdlets DLP (data loss prevention) Outlook Web App enhancements Built-in antimalware Architecture Hub transport; Unified Messaging; Edge Management Interfaces ExBPA; Mail Flow Troubleshooter; Routing Log Viewer; Exchange Management Console; Exchange Control Panel Client Access Outlook 2003 (must have Outlook Anywhere -- all clients connect RPC/HTTP) Outlook Web App Spell Check (now dependent on Browser s spell check) Anti-Spam and Anti-Malware GUI Admin Exchange Management Shell only (*You can't enable the antispam agents on an Exchange 2013 Client Access server. Therefore, the only way to get the Connection Filtering agent is to install an Exchange 2010 or Exchange 2007 Edge Transport server in the perimeter network) Web-based management tool that s optimized for on-premises, online, and hybrid Exchange deployments Replaces Exchange Management Console and Exchange Control Panel Can be accessed internally and externally (or external access can be shut off or restricted) 2
Server roles in Exchange Server 2013: Client Access Server Mailbox Server Client Access Server provides: Client authentication Redirection and proxy services Support for client protocols (HTTP,POP,IMAP,SMTP) Mailbox Server provides: Mailbox and public-folder database Transport services Unified Messaging Client connectivity is only established using RPC over HTTPS Client Firewall Edge Transport Server (SMTP only) Firewall or Reverse Proxy Hub Transport Server Client Access Server (Array) Customer s Email Server Unified Messaging Mailbox Servers (DAG) Domain Controller 3
E C M Exchange 2010 C M How Does a Client Access Server Work? Outlook Web App Outlook EAS PowerShell EAC POP/IMAP SMTP SIP Client Access IIS HTTP Proxy POP, IMAP Firewall SMTP UM SIP + RTP Redirect HTTP POP, IMAP SMTP Mailbox IIS RPS IIS RpcProxy RPC MDB OWA, EAS, EWS, ECP, OAB POP, IMAP Transport MailQ UM Microsoft Exchange Active Directory Topology if not running most exchange services will not start Default Receive Connector allows Anonymous users Transport Service 1)The Client Access server role hosts the Front End Transport service Provides filtering of email traffic (eg antispam agents), and routing of email between the internal Exchange servers and the outside world The Mailbox server role hosts two additional services: 2) Hub Transport service performs email routing within the organization, and between the Front End transport service and the Mailbox Transport service (Only one with Local Queue) 3) Mailbox Transport service passes email messages between the Hub Transport service and the mailbox database 4
The store service has been completely rewritten in managed code (C#). Exchange 2013 continues to use ESE as the database engine. But now each database runs in its own dedicated worker process, so a hung process in one database will not cause problems in other databases. Fast Search(an add-on to SharePoint 2010) is also integrated into the managed store for improved search and indexing. With a single content indexing engine, no additional resources are used to crawl and index mailbox databases for In-Place ediscovery Exchange 2013 allows SharePoint 2013 to search Exchange mailbox content using Federated search API In-Place ediscovery uses Keyword Query Language (KQL) Supports many file formats natively (Office, TXT, PDF) No need to install Office Filter Packs on Exchange servers Can leverage ifilters Includes robust error handling 5
Modernized to take advantage of the existing high availability and storage technologies of the mailbox database No more public folder databases Uses specially designed mailboxes to store both the hierarchy and the public folder content Hierarchy mailbox Contains writable copy of public folder hierarchy Content mailbox Contains writable copy of public folders and their contents Contains read-only copy of public folder hierarchy High availability for the hierarchy and content mailboxes are provided via a database availability group Although 13 cmdlets have been removed (many having to do with the old public folder management) Exchange 2013 brims with 187 new PowerShell cmdlets. So go Learn Powershell You can use the ISE to run commands and to design, write, test, and debug scripts in a Windows GUI Windows PowerShell tabs IntelliSense suggestions Script pane Console pane Add-in Tools pane 6
Identify, monitor, and protect sensitive information in your organization through deep content analysis Based on Transport Rules Test DLP policies before fully enforcing them DLP policies contain sets of conditions, which are made up of transport rules, actions, and exceptions Inform email senders that they may be about to violate one of your policies even before they send an offending message (MailTips) Offline access, which lets users write messages in their browser when offline, OWA supports this feature in Microsoft's Internet Explorer 10, Apple's Safari 5, and Google's Chrome 16 (or later), all of which support the HTML5 local data storage feature. Manage inbox rules; mobile devices; text messaging Message tracking Manage site mailboxes Group memberships Recover deleted messages Block and allow lists Change password Manage apps Exchange has had antispam capabilities for quite some time As of Exchange 2007 you could even choose whether to turn on antispam in the Edge role or in the Hub Transport role. Exchange 2013 extends antispam to a broader set of antimalware capabilities, such as to block phishing attempts. Exchange Management Shell only (*You can't enable the anti-spam agents on an Exchange 2013 Client Access server. Therefore, the only way to get the Connection Filtering agent is to install an Exchange 2010 or Exchange 2007 Edge Transport server in the perimeter network) 7
Exchange Server 2013 Mailbox server Sender Filtering Internet Recipient Filtering Sender ID Filtering Content Filtering Outlook Safe Senders List Exceed SCL Threshold Below SCL Threshold 8