Published on

Mail Server Sistemlərinə ilkin baxış.
Exchange Server 2010 yeniliklər.
Exchange Server 2010 sazlanması
Forefront Protection 2010 sazlanması

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. EXCHANGE SERVER 2010 Elgüc YusifbəyliTexniki Dəstək MCTMİLLİBYTE TƏDRİS MƏRKƏZİ elguc@yusifbeyli.comMİLLİBYTE.AZ TECHNET.AZ
  2. 2. Mövzular  Mail Server Sistemlərinə ilkin baxış.  Exchange Server 2010 yeniliklər.  Exchange Server 2010 sazlanması  Forefront Protection 2010 sazlanması
  3. 3. Exchange Server 2010 Server Role 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 Outlook Web App Exchange ActiveSync Unified Messaging
  4. 4. Client Access Services Mailbox Server Role MAPI MAPI Client Access Server Role
  5. 5. New Features in Outlook Web App Outlook Web App in Exchange Server 2010 provides: Third-party Web browsers support Conversation view Mailbox search Multiple calendars Integration with OCS Integration with SMS Outlook Web App mailbox policies Shared contacts WebReady Document viewing
  6. 6. New Unified Messaging Features in Exchange Server 2010 Exchange Server 2010 enables: Personal Auto Attendant to personalize the call answering experience Automatic speech recognition for 26 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 Lync Server
  7. 7. Shadow Redundancy Shadow redundancy benefits: Transport servers are not single points of failure Transport servers can be removed or upgraded without concern for messages in transport queues Redundant storage is not required for transport servers Network traffic is reduced
  8. 8. How Shadow Redundancy Works Hub Transport Server Role Edge Transport Server Role Mailbox Server Role
  9. 9. Message Journaling Message journaling in Exchange Server 2010: Stores journal reports for all messages based on: • Message sender or recipient • Mailbox database Reduces journal storage requirements by storing single copies of messages
  10. 10. Multi-Mailbox Search Multi-Mailbox Search: Enables searches of user mailboxes based on specific criteria Is implemented by using Multi-Mailbox Search in Exchange Control Panel Requires membership in the Discovery Management role group or delegated Mailbox Search management role
  11. 11. Personal Archives: Personal Archives: Require an archive 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
  12. 12. High Availability in Exchange Server 2007/2010 Exchange Server 2007 enables high availability for mailbox servers through: Local continuous replication (LCR) Cluster continuous replication (CCR) Standby continuous replication (SCR) Single copy clusters (SCC)
  13. 13. High Availability Features in Exchange Server 2010 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
  14. 14. Database Availability Groups MailDB3 Copy MailDB3 Copy MailDB2 Copy MailDB4 Copy MailDB1 MailDB1 Copy Mailbox1 Mailbox3 MailDB4 Copy MailDB3 MailDB2 Copy MailDB2 MailDB4 Mailbox2 Mailbox4
  15. 15. Creating a New DAG 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
  16. 16. What Is Role Based Access Control? RBAC is used to define all Exchange Server 2010 permissions RBAC: Defines which Exchange Management Shell cmdlets a user can run and which objects the user can modify Is applied by all Exchange Server management tools RBAC options include: Using management role groups to assign administrative permissions Management role assignment policies to assign permissions that users can perform on their own mailbox or distribution groups
  17. 17. Supported Transition Scenarios Active Directory requirements: Schema master and at least one global catalog server in each site running Windows Server 2003 SP2 or later Windows Server 2003 forest and domain functional level Exchange Server version Exchange Server Organization Exchange 2000 Server Transition Not supported Exchange Server 2003 Service Pack 2 Supported or later Exchange 2007 Service Pack 2 or later Supported Mixed Exchange 2007 and Exchange Supported Server 2003 organization
  18. 18. Upgrade Setup parameter Description /PrepareAD • Prepares the global Exchange objects /OrganizationName: • Creates the Exchange universal security groups ”organizationname” in the root domain • Prepares the current domain /PrepareLegacy • Required for upgrades from Exchange Server ExchangePermissions 2003 /PrepareSchema • Prepares the schema for the Exchange Server 2010 installation /PrepareDomain • Prepares the domain by creating a new global group called Exchange Install Domain Servers /PrepareDomain domainname /PrepareAllDomains
  19. 19. Hardware Requirements for Exchange Server 2010 Resource Requirements Processor • Intel 64-bit architecture • AMD64 architecture • Processor cores: minimum 2 Memory • 4 GB supported minimum • 8 GB recommended • Additional memory required based on server role and load Disk • 1.2 GB free disk space for Exchange Server files • 200 MB free on the system drive • Additional space for mailbox storage File System • NTFS file system for all drives
  20. 20. Bizi dinlədiyiniz üçünTƏŞƏKKÜRLƏR