What s New in. Exchange Server 2010

Transcription

1 What s New in Microsoft Exchange Server 2010

2

3

4 Microsoft Exchange 2010 In development since 2006 Public Beta on April 15th, 2009 Shipped 2 nd half 2009 SP1 August 2010 SP2 December 2011

5 You can combine all server roles, except the Edge Transport server role, on one server Component Processor cores Memory Minimum: 2 Recommended: 8 Maximum: 16 Recommendation Plan on using half the processor cores for the mailbox server role Recommended: 4 GB plus 2-6 MB per mailbox Maximum: 64 GB Mailboxes Reduce maximum number of mailboxes by 20% You can combine server roles with Mailbox servers that are DAG members

6 Resource Processor Memory Disk File System Requirements Intel 64-bit architecture AMD64 architecture 2 gigabytes (GB) minimum Additional memory required based on server role and load 1.2 GB free disk space for Exchange Server files 200 megabytes (MB) free on the system drive NTFS file system for all drives Software requirements: 64-bit edition of Windows Server 2008, Windows Server 2008 R2 Standard, or Enterprise Edition AD DS management tools Microsoft.NET Framework 3.5 Windows Remote Management 2.0 Windows PowerShell version 2.0 Additional components based on server roles

7 You can deploy all Exchange server roles, except Unified Messaging servers, on virtual machines running on a supported virtualization platform Design the Exchange server deployment to fully utilize the server resources Consider the high-availability features in Exchange Server 2010 as an alternative to highly available virtual machines Virtualization high availability options are not recommended for Mailbox servers Design virtual hardware using the same criteria as physical hardware

8 In Exchange Server 2010, servers are installed with specific functional roles: Hub Transport Server role Mailbox Server role Edge Transport Server role Client Access Server role Unified Messaging Server role

9 Small Organization Medium-Size Organization Large Organization

10 In Exchange Server 2007 and Exchange Server 2010, the Client Access server role provides access to Exchange mailboxes for: Outlook Web Access clients Exchange ActiveSync clients POP3 and IMAP4 clients The Client Access server role also provides: Autodiscover service Exchange Web Services

11 Client Access Changes

12 The Exchange Control Panel in Exchange Server 2010 provides: User self-management of their mailbox options An administration tool for distribution group management Cross-mailbox search functionality Exchange Server 2010 provides MailTips warning messages before you send an The Conversation view in Exchange Server 2010 provides new options for grouping and managing e- mail

13 New Role based administration for compliance, HR, Help Desk Staff All clients now connect to CAS. Only CAS connects to mailbox via RPC. Federated Sharing of Free Busy and other EWS New OW OWA Browser Agnostic User Self Service for message tracking Conversation View Mail Tips OCS R2 presence enabled

14 Domain Controller Client Access Server 3 Mailbox Server 4 RPC 1 2 MAPI HTTPS IMAP4 POP3

15 Outlook Web Access in Exchange Server 2010 provides: Third-party Web browsers support Conversation view Mailbox search Multiple calendars Integration with OCS Integration with SMS Outlook Web Access mailbox policies Shared contacts WebReady Document viewing

16 ECP provides Web-based user access to self-manage: Outlook Web Access features (signature, message options, etc.) Inbox rules Automatic replies Report delivery Call Answering Rules Deleted item recovery Public groups ActiveSync (report wipes, logs) Text message configuration Account information (location, phone numbers, etc.)

17 Scenario Using Public Folders? New to Public Folders? Document Sharing SharePoint may be a better option SharePoint is a better option Calendar Sharing No need to move Use either* Contact Sharing No need to move Use either* Discussion Forum No need to move Use either* Distribution Group Archive No need to move Use either* Custom Applications SharePoint may be a better option Organizational Forms No need to move Use InfoPath SharePoint may be a better option**

18 Further transport rule development Information Leakage Protection and Control (IPC) Shadow Messaging for transport redundancy RMS integrated Transport Rules Business to Business RMS (federated)

19 Transport Changes

20 Exchange Server 2010 enables the option of using HTML disclaimers Exchange Server 2010 enables moderators to: Configure transport rules Configure recipients Shadow redundancy provides resilience for messages sent between Transport servers

21 Component Submission queue Store driver Microsoft Exchange Mail Submission service Categorizer Pickup directory Description Stores all messages on disk until processed Retrieves messages from sender s Outbox Notifies a Hub Transport server in the local Active Directory site when a message is available for retrieval from a sender s Outbox Processes one message at a time from the Submission queue Submits messages to the Submission Queue

22 Client Access server Mailbox server Outlook client Hub Transport server Internet 6 5

23 Retention Tags and managed content settings provide options for users to tag messages in their mailboxes Retention policies can be used to group multiple Retention Tags and assign them to users Cross-mailbox searches are enabled through the Exchange Management Console Mailbox archiving requires an alternate mailbox for the user account

24 Transport rules are applied to messages sent through the Transport servers Transport rules include: Conditions the message criteria that will trigger the rule Actions the action applied when the rule is triggered Exceptions criteria that will prevent the application of the rule

25 Messaging Records Management enables the management of messages in user mailboxes Exchange Server 2010 improves the user experience by providing: Retention polices Auto-tagging

26 Moderated transport: Requires the approval of a moderator before messages are delivered Can be enabled for distribution groups or mailboxes

27 Shadow redundancy: Provides resilience for messages in transit through Transport servers Ensures that copies of messages are retained on multiple Transport servers until the messages are delivered to the destination

28 Hub Transport Server Role Edge Transport Server Role Mailbox Server Role

29 Hub Transport Server Transport Dumpster MailDB1 Copy of MailDB1 Mailbox server Mailbox Server Messages in the transport dumpster are deleted when they have been applied to all mailbox database

30 Edge Transport servers: Provide anti-spam and anti-virus filtering Can use AD DS information to filter messages Require an Edge Subscription to replicate information from Hub Transport servers Edge Transport server in Exchange Server 2010 enables incremental edge synchronization updates

31 New storage technologies (cheaper SATA) New HA/DR planning with Database Availability Groups Optimized for large mailboxes (10+ GB) Archive mailboxes Online mailbox moves Dumpster is a mailbox folder not a feature of the store 100K items per folder

32 Mailbox Store/ESE Changes

33 Mailbox archiving: Requires a secondary mailbox for each user Enables users to move the contents of PST files into a managed mailbox Enables indexing and searches of all user messages

34 A DAG is a collection of servers that provides the infrastructure for replicating and activating database copies. DAGs: Require the failover clustering feature, although all installation and configuration is done with the Exchange Server management tools Use Active Manager to control failover Use an enhanced version of the continuous replication technology that Exchange Server 2007 introduced Can be created after the Mailbox server is installed Allow a single database to be activated on another server in the group without affecting other databases Allow up to 16 copies of a single database on separate servers Define the boundary for replication

35 In Exchange Server 2010: Storage groups have been removed Mailbox databases are not associated with Exchange Server objects Input/output for mailbox database access has been reduced Automatic page patching can recover from database corruption

36 In Exchange Server 2010: Database availability groups combine features from CCR and SCR Failover clustering configuration is transparent to Exchange administrators Mailbox servers can host 100 databases Each mailbox database can have 16 copies Mailbox servers that are part of a DAG can also host other Exchange Server roles Shadow redundancy provides transport-level redundancy

37 Continuous replication uses log shipping to replicate mailbox databases between Mailbox servers New features in Exchange Server 2010 include: Continuous replication operates at the database level Log shipping uses a configurable port number Only mailbox databases can be replicated Transaction log replay can be delayed

38 DAGs require the failover clustering feature in Windows Server 2008 When creating a DAG: Failover clustering feature is installed Failover cluster components are transparently configured Failover cluster quorum mode is automatically configured

39 In Exchange Server 2010, the Active Manager: Manages all DAG components Receives notifications from the Microsoft Exchange Replication service Determines which mailbox database copy to mount when the active copy of the database is not available Informs the Client Access servers about which databases are mounted

40 Mailbox High Availability Changes *Over = Failover or Switchover

41 DB1 DB2 DB2 DB2 DB3 DB3 DB4 DB4 DB4 Continuous replication protects databases across servers in the DAG

42 Point of Failure Exchange Server 2007 Exchange Server 2010 LCR CCR SCR SCC DAG Server None None Storage None VSS Backup Supported Supported Not supported Replication Copies Single copy on server Single copy on passive node Log Replay Delay Data Loss Protection Multiple targets None None Up to 24 hours or 50 log files Transport dumpster Transport dumpster Failover Manual Automatic failover Can Run with Multiple Roles Not available Manual Yes No Target Only Supported None None None Automatic failover No Supported Up to 16 targets Up to 14 days Transport dumpster Automatic switchover by database Yes

43 Unified Messaging in Exchange Server 2007 provides: Call answering Fax receiving Office Outlook Voice Access Play on Phone Feature Auto attendant

44 Exchange Server 2010 enables: Personal Auto Attendant to personalize the call answering experience Automatic speech recognition for 16 languages More options for resolving caller ID Exchange Server 2010 provides: Voice mail displayed as text in the Inbox Message waiting indicators on supported phones and in Office Communicator Protected voice mail cannot be forwarded Enhanced integration with OCS 2007 R2

45 Active Directory requirements: Windows Server 2003 Service Pack 2 global catalog servers Windows Server 2003 forest-functional level Exchange Server version Exchange 2000 Server Exchange Server 2003 Service Pack 2 or later Exchange 2007 Service Pack 2 or later Mixed Exchange 2007 and Exchange Server 2003 organization Exchange Server Organization Transition Not supported Supported Supported Supported

46 To deploy Exchange Server 2010 server roles: 1. Client Access servers 2. Hub Transport servers 3. Unified Messaging servers 4. Mailbox servers To remove previous Exchange Server versions: 1. Mailbox servers 2. Unified Messaging servers 3. Transport servers 4. Client Access servers

47 Questions?