Exchange Server 2010 Designing & Deploying Messaging Solutions (70-663)

Microsoft Exam 70-663 Training Course: Exchange Server 2010: Designing & Deploying Messaging Solutions

PACKAGE INCLUDES:

 •  Instructor Led Video Training on DVD or Online
 •  Demos and Lab Learning
 •  Multimedia Presentations and Self-Paced Navigation
 •  Practice Exam and Test Simulator 
 •  Online & Telephone Tutor Support

Compatible with:
Windows NT , 95 , 98 , 2000 , ME , XP , 2003 , Vista , Windows 7

 

COURSE DESCRIPTION

GET IN THE LEAD - Get Certified Today! Experience the benefits of classroom learning - anytime, anywhere! Our expert instruction and multi-media courses are to get you certified - or your money back!

Our MCTS 70-663 Pro: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010 course teaches students planning and deployment of the Exchange servers in an enterprise environment.

Credit toward Certification
Exam 70-663: Pro: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010: counts as credit toward the following certification(s): Microsoft Certified IT Professional (MCITP): Enterprise Messaging Administrator 2010.

Skills Being Measured
This exam measures your ability to accomplish the technical tasks listed below. The percentages indicate the relative weight of each major topic area on the exam.

Planning the Exchange Server 2010 Infrastructure (20 percent)

• Design the Exchange Server 2010 installation.
  • This objective may include but is not limited to: define Exchange server physical locations; Exchange DNS requirements; plan for common namespaces; SLA requirements; Active Directory site topologies; network topology; Exchange federation; multi-domain; multi-forest; resource forest; analysis and design of ongoing infrastructure improvements due to increased capacity, performance, and requested features
• Design message routing.
  • This objective may include but is not limited to: inter-site and intra-site hub routing; connectors; coordinate messaging topics between Exchange departments, CIO, security, and LOB providers within the enterprise; develop connectors between Exchange and other messaging applications; design and deploy hub mail flow; design and deploy Edge connectors/scoping; design message transport; reverse zone (PTR records); scale hub transport server performance; storage requirements (shadow redundancy); multi-domain; multi-forest; resource forest; accepted domains; remote domains; send connector configuration; analysis and design of ongoing infrastructure improvements due to increased capacity, performance, and requested features
• Design the mailbox server role.
  • This objective may include but is not limited to: plan database sizing; storage performance requirements - I/O and disk latency requirements; multi-domain; multi-forest; resource forest; public folders; design recipient, distribution group, and mailbox provisioning and deprovisioning policies; analysis and design of ongoing infrastructure improvements due to increased capacity, performance, and requested features
• Design client access.
  • This objective may include but is not limited to: local vs. remote access; mobile access policies; identify and plan for supported messaging clients such as IMAP, POP, Exchange ActiveSync; Outlook Anywhere; Web services; OWA; MAPI (RPC Client Access); MAPI on the Middle Tier (MOMT); scale CAS server performance; storage requirements; multi-domain; multi-forest; resource forest; analysis and design of ongoing infrastructure improvements due to increased capacity, performance, and requested features; plan the location and configuration of Client Access servers; plan the AutoDiscover implementation; plan for Federated Sharing
• Plan for transition and coexistence.
  • This objective may include but is not limited to: plan and investigate consolidation of Exchange servers; plan intra-org and inter-org migration; decommission legacy environment; free/busy; inter-org message routing; how to preserve the ability to reply to a message (x500, SMTP, and legacyExchangeDN); public folders (free/busy lookup, replication); identify when to use a transition rather than a migration

Deploying the Exchange Server 2010 Infrastructure (20 percent)

• Prepare the infrastructure for Exchange Server 2010 deployment.
  • This objective may include but is not limited to: requirements to prepare schema, prepare domain, and prepare Active Directory; legacy permissions; prepare forest; forest functional level; domain controller versions, roles (excluding RODC/ROGC) and placement; prepare DNS (MX, sender ID, federation, PTR records)
• Deploy Edge transport server role.
  • This objective may include but is not limited to: validate Exchange deployment; EdgeSync; configure transport agents; replace perimeter e-mail gateway; configure address rewriting
• Deploy client access server role.
  • This objective may include but is not limited to: deploy CAS hardware and protocols; deploy mobile messaging services and connectivity; validate client connectivity; validate client functionality; autodiscover; multi site/domain/forest
• Deploy hub transport server role.
  • This objective may include but is not limited to: validate Exchange deployment; multi site/domain/forest; configure transport rules; accepted domains; remote domains; send connector configuration; message and recipient limits; deploy message flow to and from the Internet; deploy e-mail relay; configure the accepted domain; validate message transport
• Deploy mailbox server role.
  • This objective may include but is not limited to: database configuration and placement quota enforcement policies; deploy the mailbox server and storage; deploy the hardware configuration for mailbox servers; deploy the mailbox database; deploy address lists and offline address books; validate mailbox server performance; validate mailbox server access; deploy public folders; configure public folder replication; configure client access to public folders; configure public folder permissions
• Deploy server roles for coexistence and migration.
  • This objective may include but is not limited to: coexistence with and migration from Exchange 2003, 2007, and 2010 and third-party mail systems; coexistence with namespaces; validate Exchange deployment; server transition process; transport rule coexistence; conversion from LDAP to OPATH filtering; routing group connector (RGC) configuration

Designing and Deploying Security for the Exchange Organization (20 percent)

• Design and deploy messaging security.
  • This objective may include but is not limited to: secure relaying; S/MIME; certificates; MTLS; RMS (security related to using transport rules); define message security requirements; planning SMTP connector security; planning secure routing between partner organizations; planning client-based message security; planning the integration of Active Directory Rights Management Services (AD RMS) and Exchange Server 2010; planning ControlPoint Encryption; planning Outlook Protection Rules
• Design and deploy Exchange permissions model.
  • This objective may include but is not limited to: role-based access control (RBAC) assignments, scopes, and roles; Exchange Control Panel (ECP); modification of default RBAC roles; creation of custom RBAC roles; planning administrative permissions using the built-in management roles; planning administrative permissions using custom management roles; planning remote administration of Exchange servers
• Design and deploy message hygiene.
  • This objective may include but is not limited to: design and deploy Edge security; design anti-spam and anti-virus solution for the messaging deployment; SPA/sender ID; define connection, attachment, recipient, sender, and content filtering rules; safe list aggregation; block lists; phishing confidence level (PCL); spam confidence level (SCL); sender reputation level (SRL); identify the requirements for an anti-virus and anti-spam solution; plan an anti-spam solution deployment; plan for ongoing management of the anti-spam deployment; plan an anti-virus solution deployment; plan for ongoing management of the anti-virus deployment; plan user communication plans
• Design and deploy client access security.
  • This objective may include but is not limited to: design and deploy ActiveSync policies; plan certificates for Exchange CAS; alternate authentication (smart cards, client certificates, time-based two-factor authentication tokens); authentication protocols (plain text, NTLM, forms based, Kerberos); OWA segmentation
• Design and deploy Exchange object permissions.
  • This objective may include but is not limited to: design and deploy public folder security; mailbox (send as, full access, delegation, mail flow); resource security; distribution groups; design and deploy mailbox client access security (POP, IMAP, ActiveSync, OWA, MAPI)

Designing and Deploying Exchange Server 2010 Availability and Recovery (21 percent)

• Design and deploy high availability and disaster recovery for Exchange dependencies.
  • This objective may include but is not limited to: directory resiliency, network resiliency, DNS resiliency, storage hardware resiliency, site resiliency, datacenter resiliency; plan for updates and change management
• Design and deploy high availability and disaster recovery for CAS role.
  • This objective may include but is not limited to: backup and recovery; designing and deploying CAS array; multi-site CAS deployment; DNS updates for client access during site failover
• Design and deploy high availability and disaster recovery for mailbox server role.
  • This objective may include but is not limited to: design and deploy database scoping; design DAG; design and deploy public folder replication; backup and recovery; DNS record TTL; file share witness resiliency; activation preference and auto-activation; lag copies; designing and deploying continuous replication; designing and deploying DAGs distributed across multiple locations
• Design and deploy high availability and disaster recovery for hub transport role.
  • This objective may include but is not limited to: backup and recovery; receive connector resiliency; send connector scoping; design and deploy high availability for Hub Transport Servers; design and deploy Exchange Server configurations to mitigate the effect of a disaster; choose an Exchange Server backup solution; design and deploy Exchange Server backups; design and deploy Exchange Server data restores; restore Exchange Server role
• Design and deploy high availability and disaster recovery for Edge transport server role.
  • This objective may include but is not limited to: backup and recovery; server placement; DNS load balancing; MX records; namespace changes; designing and deploying high availability for Edge Transport Servers; designing and deploying Exchange Server configurations to mitigate the effect of a disaster; choosing an Exchange Server backup solution; designing and deploying Exchange Server backups; designing and deploying Exchange Server data restores; designing and deploying Exchange Server server restores

Designing and Deploying Messaging Compliance, System Monitoring, and Reporting (19 percent)

• Design and deploy auditing and discovery.
  • This objective may include but is not limited to: audit logging; admin audit logging; permissions auditing; message tracking; protocol logging; RBAC (compliance role and scope); identify requirements for discovery or auditing; plan journaling or message record management (MRM) for discovery; plan access permissions for discovery searches
• Design and deploy message archival.
  • This objective may include but is not limited to: dumpster 2.0; legal hold; retention policies (MRM); retention tags; long-term backup; design and deploy managed folders; design and deploy alternate mailboxes; plan for managing messages in default Outlook folders; plan for managing messages in custom managed folders; plan a retention policy implementation; plan an AutoTagging implementation
• Design and deploy transport rules for message compliance.
  • This objective may include but is not limited to: RMS; ethical firewall; message journaling; disclaimers; mail tips, such as notification for external recipients and recipient limits
• Design and deploy for monitoring and reporting.
  • This objective may include but is not limited to: design and deploy message flow monitoring; client accessibility; SLA requirements, such as percent of email delivered in a certain amount of time within the organization; analyze message usage, number of messages, and message size; analysis and design of ongoing infrastructure improvements due to increased capacity, performance, and requested features; monitoring client access services; troubleshooting client access services