1. Module 3 Planning and Deploying Mailbox Services

2. Module Overview Overview of Mailbox Services in Exchange Server 2010 Designing Mailbox Servers Designing Recipient Management Designing Public Folder Architecture

3. Lesson 1: Overview of Mailbox Services in Exchange Server 2010 New Mailbox Services Features in Exchange Server 2010 Storage Changes in Exchange Server 2010 Information Required for Designing Mailbox Services

4. New Mailbox Services Features in Exchange Server 2010 New mailbox services features include: Archive mailboxes Calendar repair Resource configuration Live mailbox moves User-managed distribution groups Bulk management

5. Storage Changes in Exchange Server 2010 Changes in storage include: Storage groups are no longer available Single instance storage has been removed Compression has been added to databases Database is now a peer to the server object Disk I/O is optimized for commodity storage Reduced by 70% from Exchange Server 2007

6. Information Required for Designing Mailbox Services Mailbox information: Number of users Frequency of usage Size of mailboxes SLAs Public folder information: Frequency of usage Size of public folders Replications requirements Type of client

7. Lesson 2: Designing Mailbox Servers Designing Mailbox Sizing Designing Mailbox Server Database Configuration Designing Mailbox Disk Storage Designing a Test Plan for Server Performance Designing Mailbox Server Processor and Memory Requirements Designing Mailbox Servers for High Availability

8. Designing Mailbox Sizing To design mailbox sizes, evaluate: Business requirements Cached mode for performance Archive mailboxes Quota versus actual size Database only shrinks with offline defragmentation Deleted item retention Deleted mailbox retention POP3 may remove messages immediately

9. Designing Mailbox Server Database Configuration When designing Mailbox server configuration : Split log files and database storage to enhance recoverability Allocate space for indexes Allocate space for single item recovery Considerations for selecting an Exchange Server edition: Standard edition allows 5 databases Enterprise edition allows 100 databases Allocate space for personal archives Allocate space for a recovery database

10. Designing Mailbox Disk Storage Options for Mailbox storage include: SCSI versus SATA DAS versus SAN Fibre Channel versus iSCSI RAID JBOD

11. Designing a Test Plan for Server Performance To evaluate server performance : Gather usage information Create a test environment Measure hardware capacity Virtualization should not be used unless the production environment will be virtualized

12. Designing Mailbox Server Processor and Memory Requirements Processor: Memory: Minimum 4 GB per Mailbox server 3 MB per mailbox for average users Must be 64-bit Multicore recommended One core per 1,000 mailboxes

13. Designing Mailbox Servers for High Availability You can implement high availability for Mailbox servers by using DAGs Considerations for implementing DAGs: Mailbox database names must be unique in the organization Storage path must be identical for all copies of a database Requires failover clustering feature in Windows Server 2008 Can be managed completely with Exchange Server 2010 tools Does not protect public folder databases

14. Lesson 3: Designing Recipient Management Designing Recipient Management Processes Designing Address Lists Designing E-Mail Address Policies Designing System Messages Designing Distribution Groups Designing Resource Mailboxes Designing Mailbox Moves

15. Designing Recipient Management Processes To design recipient management processes: Define which users will perform management tasks Delegate management to selected users Select an appropriate management tool  Exchange Management Shell  Exchange Management Console  Exchange Control Panel

16. Designing Address Lists Considerations for designing address lists: In large organizations, you should create additional address lists for: Workgroups Regions When an Outlook client runs in cached mode, it uses offline address books In hosted scenarios, you can create multiple GALs

17. Designing E-Mail Address Policies The default e-mail address policy applies to all users Create new policies for: Different address formats Different domains Set the primary address when changing e-mail domains Schedule application of new policies

18. Designing System Messages Customizing DSN messages: Most circumstances will not require DSN message customization Customize to describe the special features of your anti- spam software Customize to provide contact information You can customize quota messages by: Making the messages more user friendly Providing contact information

19. Designing Distribution Groups While designing distribution groups, you can: Designate expansion server to control processing load Designate a group manager Enable moderation Reuse security groups Dynamic groups: Reduce administrative load Require relevant data in AD DS Increase processing, if used frequently Newly created distribution groups are universal groups

20. You can use resource mailboxes for: Autoaccept: Delegates can: Designing Resource Mailboxes Arbitrate conflicting requests Ensure that resources are used only for appropriate purposes Can be used to automate the booking process Speeds up the booking process Needs appropriate rules for availability Booking rooms Booking equipment

21. Designing Mailbox Moves Reasons for moving mailboxes: Migration to new server Load balancing between servers Reducing database size Users moving between locations or departments Online mailbox moves to Exchange Server 2010: Are possible from Exchange Server 2010 or Exchange Server 2007 SP2 only Reduces user impact and speeds up the move process Must use the New-MoveRequest cmdlet

22. Lesson 4: Designing Public Folder Architecture Analyzing Business Requirements for Public Folders Designing Mailbox Servers for Storing Public Folders Designing Public Folder Replication Designing Client Access to Public Folders Planning the Public Folder Hierarchy Designing Public Folder Permissions Alternatives to Public Folders

23. Analyzing Business Requirements for Public Folders Purpose of using public folders: Collaboration Centralized location for messages Information required for designing public folders: Amount of data How often data changes Type of clients Location of clients

24. Designing Mailbox Servers for Storing Public Folders Size of the public folders determine: Size of the storage How long deleted messages are retained Amount of data change determines: Type of storage system (I/O requirements) Memory and processing requirements

25. Designing Public Folder Replication Benefits of public folder replication: Provides high availability Places content close to users Speeds up access Reduces network traffic between sites Considerations for designing public folders: Multiple copies can be a concern for data that changes frequently Referral order is based on Active Directory site links, but it can be modified

26. Designing Client Access to Public Folders For internal client access: Typically Office Outlook is used Outlook Web App can also be used For external client access: Typically Outlook Anywhere is used Outlook Web App can also be used Exchange Server 2010 does not support the NNTP and IMAP protocols for client access to public folders

27. Planning the Public Folder Hierarchy When planning the public folder hierarchy : Create logical and consistent groupings Use a consistent and logical naming scheme Consider delegation of administrative tasks Consider how to simplify administrative processes

28. Designing Public Folder Permissions When designing public folder permissions : Plan to delegate administration Plan for default and anonymous permissions Limit permissions at higher levels of the hierarchy When applying permissions: New folders inherit the permissions of the parent folder Permissions on the parent folder can be propagated to existing folders

29. Alternatives to Public Folders Features of Windows SharePoint Services: Document libraries Discussion groups Shared calendars Contacts Other public folders alternatives include: NNTP servers Web-based forum software

30. Lab: Planning and Deploying Mailbox Services Exercise 1: Designing the Mailbox Server Deployment Exercise 2: Designing Recipient Management Exercise 3: Designing a Public Folder Deployment Exercise 4: Implementing Mailbox Services Logon information Estimated time: 75 minutes

31. Lab Scenario You are a messaging engineer for A. Datum Corporation, an enterprise-level organization with multiple locations. A. Datum Corporation is an international organization involved in technology research and investment, and is planning to upgrade from Exchange Server 2003 to Exchange Server 2010. You have been tasked with reviewing the current messaging infrastructure and network topology, with a goal of planning the deployment and configuration of Mailbox services. You are required to make proposals about how best to address the needs of the various stakeholders in the organization. Finally, you are required to implement part of your proposed Mailbox services design.

32. Lab Review What is the difference between a distribution group owner and a distribution group moderator? Why do you not need to provide a password for the user account when creating a resource mailbox?

33. Module Review and Takeaways Review Questions Best Practices