• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content







Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • When installing Exchange you can put down just the bits on a server that are relevant for its role. For example in the case of the Edge Transport role only the bits required for transport and hygiene are installed; this reduces the overall surface area of attack. Where the Hub Transport, Client Access, and Unified Messaging servers are scale out (redundant servers for load balancing and failover), the Mailbox server is a scale up role (larger servers for performance and cluster for failover) It is important to note that all the server roles (minus Edge Transport) can be installed on a single server Client Access Server (CAS) is required per AD site where there are Mailbox Servers Enables : Outlook 12 & E12 “ AutoConnect ” Outlook Web Access Calendaring (Availability) Exchange ActiveSync (EAS) POP3/IMAP4
  • Through the Exchange Management Shell you can install a single server or create a script to install multiple servers and even create storage groups, databases, and users in those databases.
  • Hub in the middle Hub needed for EdgeSync and to deliver messages to Mailbox Edge Message Level Security Hub needs Edge to deliver to the Internet CAS needs Hub to provide Availability information
  • More IO tuning Larger but fewer IOs Made possible by large cache
  • In Exchange 2003 we extensively used tree navigation to display all object hierarchy and depended upon right mouse click to take action on these objects. For new or infrequent users it was difficult to find where in the tree you needed to be to perform a task. Are frequent administrators were forced to learn all of the nuances of the tool. The multiple pane approach allows us to move more of the hierarchy out of the tree and into the available white space. This and organizing administration by the server roles makes it easy to find the objects you need to take action on. Once you have a set of objects to work with, administrators can utilize the filters to find only the object or set of objects that they need to work with. Once selected actions can be discovered by the action pane or via right clicking. One recurring theme throughout the administration experience is keeping the look and feel consistent no matter what server role or set of objects you are managing. This consistency can be readily seen in the wizard structure. Lastly, Exchange is meant to act as the single management tool for Exchange. It includes a toolbox that all of the valuable web release tools that you utilize can be placed.
  • E2kx – up to 8 levels deep of navigation to find objects to configure E12 makes smart use of work pane and results pane to make it easier to identify objects that can be actioned. E2kx relies heavily on right click to discover actions that can be taken on objects. E12 makes use of both right click and the action pane to take action on objects.
  • What is “MONAD”? An extensible scripting technology which is interactive, programmable, secure and production-oriented. Improves the developer experience by making it easier to add command-line management capabilities using .NET Improves the administrative experience by enabling IT Pros to write secure automation scripts that can run locally or remotely “ MONAD” Components : A scripting language (Monad) An interactive shell (MSH) A way to produce task-oriented commands A set of domain-independent utility commands Administration in Exchange is built on the Windows “Monad” technology. The “Monad” Engine is used to run Exchange specific tasks against a number of sources including the Exchange store, registry files and active directory. These commandlets can be run directly from the Exchange Management Console, or can be used in a set of scripts that can be run directly in the console. The Monad Data Provider and WinForms allow commandlets and sripts to be manipulated as .NET objects. This allows applications written in managed code to execute the Exchange commandlets and scripts. Because of this model everything in the Exchange Management Console only executes Exchange commandlets that could be run in the Exchange Management Shell. In other words there is no additional business logic built into the Exchange Management Console. This allows customers and partners to create their own applications that execute administration tasks.
  • Set-mailbox -ID domainusername –parameter argument (-parameter argument – parameter argument)
  • Decommission any Exchange 5.5 servers Prepare Active Directory Deploy Edge Server Deploy Client Access Server Deploy Hub Transport Server Deploy Mailbox Server Move resources from Exchange Server 2000 or Exchange Server 2003 Uninstall or decommission Exchange Server 2000 or Exchange Server 2003 from the Exchange organization Remove connectors between Routing Groups and remove Routing Groups

Inf204 Inf204 Presentation Transcript

  • INF204 - Exchange “12” - Part 1: The New Architecture Efi Bregman, Uzi Hefetz Microsoft
  • Goals and Agenda
    • What’s New in Exchange Server “12”?
    • Part 1:
      • E12 New Architecture
      • E12 Administration
      • Co-existence and Upgrade
      • E12 Programmability changes
    • Part 2:
      • INF310 : Exchange “12” Advanced Features
  • Exchange 2000/3 Challenges
    • Backup/Restore
    • Disaster Recovery
    • Performance
    • Security
    • Routing
    • Search
    • Calendar
    • Spam mail
    • Resource Management
    • Management & Delegation
    • Automation/Scripting
    • E-mail Lifecycle Management
    • Planning & Deployment
    • Audit
    • Archiving
  • Control Simplify Deployment and Management
    • New Architecture
    • Flexible Installation Wizard
    • Intuitive console GUI
    • Scriptable command line UI
  • E12 Server Roles DMZ Intranet E12 Edge Server E12 Server
  • E12 Enterprise Topology Enterprise network Mailbox Mailbox Edge Transport Other SMTP Servers Hub Transport Routing Hygiene Routing Policy Voice Messaging Unified Messaging Applications: OWA Protocols: ActiveSync, POP, IMAP, RPC / HTTP … Programmability: Web services, Web parts PBX or VoIP I N T E R N E T Public Folders Fax Client Access
  • Role Base Setup Simple GUI Install
  • Role Base Setup Integrated BPA Prerequisites validation
  • Role Base Setup Fully customizable unattended install
  • E12 Routing
  • E12 Routing Life without Linkstate
    • Exchange now depends on Active Directory topology
    • Full mesh connection
      • No reroutes, by default!
    • One Connector for E2K/E2K3 servers
  • E12 Routing Other transport related highlights
    • No IIS dependency
    • Greatly improved “agent” (event sink)
    • New rules engine for controlling mail flow
    • Can be administered through “Monad”
    • Improved logging
    • Simplified queuing - fully JET-based
  • Administrative Groups Life Without Administration Groups
    • E12 permission scope
      • Organization Wide
      • Single Server delegation
      • Sorting / filtering based on server attributes
    • Exchange 200x will simply see the E12 servers as belonging to a different AG
  • Improved Performance Reduced I/O by 70% !!
    • How is it possible?
      • More RAM => More database buffer cache
      • More Storage Groups => more checkpoint depth per user
      • 8K page size, and other physical schema optimizations
      • More IO tuning
  • More Scalable
    • More Stores
      • 50 Storage Groups & 50 Databases!
    • No services rely on Public Folders
      • OAB
      • Free/Busy
  • Control 64-bit Imperative
    • Increase in traffic
    • Increase in message sizes
    • Larger and more attachments
    • More unique clients per user
    • Growing use of calendaring
    • More granular security rights
    • Larger number of users per server
    32-bit Exchange 2003 Exchange 2000 Exchange 5.5 Exchange 4.0 64-bit Exchange 12
  • Additional Enhancements
    • Customizable Quota messages
    • 32k Rules limit has been increased
    • The ability to disable / enable MAPI access on a per mailbox basis
    • No more streaming (STM) file
    • More Log files
  • Search
    • Index as items stored
    • Improved Performance
    • Reduced index size
      • 5% of the DB size
    • Used by outlook online mode & OWA
  • E12 Search
  • E12 System Manager
  • E12 System Manager Simplified Navigation
    • Multiple panes
    • Object Filtering
    • Consistent User Interface
    • Single tool for managing Exchange
      • Toolbox includes web release tools (ExBPA …)
  • E12 System Manager
  • Demo Screen Shot: E12 System Manager
    • 1. Tree: Segmented into 4 work centers: (Recipients, Servers, Organization, Toolbox)
    • Result pane : rich list of objects
    • 3. Work Pane: child objects of result pane object, only used by Servers & Organization nodes
    • 4. Action Pane: tasks for selected object(s) and node (work center)
    1 2 3 4
  • Demo Screen Shot: Tree Navigation improvement
  • Demo Screen Shot: Filtering
  • Demo Screen Shot: “Right Click” Action Pane
  • Exchange Management Shell How to do something that took 2 hours in 1 minute?
  • E12 Management Model AD Registry Files E12 Store Windows PowerShell (“Monad”) Engine IIS Metabase
  • E12 Management Shell
    • Set the send quota for ALL mail enabled users in the DL called “RemoteUsers” to 1000 KB
    • Delete all messages in queue where sender is Bob
    • Move ALL users from server PORTLAND to the TUCSON server, database “DB1”
        • Get-Mailbox –server PORTLAND | move-mailbox –targetDatabase “TUCSONDB1”
        • Get-DistributionGroup “RemoteUsers” | Get-DistributionGroupMember |
        • Set-Mailbox –ProhibitSendQuota 1000
        • Get-Message | where { $_.From -ilike *bob* } | remove-message
  • E12 Management Shell
  • Demo Screen Shots: Move Mailbox
  • Demo Screen Shot: Provision-server.msh Provision-server.msh Newuser.csv
  • Demo Screen Shot: Provision-server.msh
  • Demo Screen Shot: Reporting in Management Shell
  • How do I upgrade to E12?
  • Coexistence & Migration
    • No in-place upgrades (x64 …)
    • Coexistence
      • New E12 Administrative group
      • New E12 Routing group
    • New schema updates
    • No upgrades from Exchange 5.5
      • Must first migrate to Exchange 200x
  • Migration Process E12 Administrative Group Administrative Group 1 Administrative Group 2
  • Extensibility for Developers
    • Web services API
    • Exchange command line shell scripts
    • Managed code transport agents
    • OWA Web Parts for SharePoint Portal apps
  • Cut from E12
    • IT Pro
    • Admin groups
    • Routing groups
    • Active-Active clustering
    • X.400
    • Co-existence with Ex5.5
    • GroupWise Connector/Mig.
    • End-User
    • OWA/IMAP/NNTP access to Public Folders
    • Outlook Mobile Access (WAP)
    • OWA rule creation/editing
    • Developer
    • Transport Event Sinks
    • CDO 1.2
    • CDO for Workflow
    • CDOExm
    • Exchange WMI classes
    • IFS (M:)
    • Event Service
    • Exchange Web Forms
    • Workflow Designer
  • Challenges Addressed
    • Backup/Restore
    • Disaster Recovery
    • Performance
    • Security
    • Routing
    • Search
    • Calendar
    • Spam mail
    • Resource Management
    • Management & Delegation
    • Automation/Scripting
    • E-mail Lifecycle Management
    • Planning & Deployment
    • Audit
    • Archiving
  • Tune in to Part 2 to hear about
    • INF310 : Exchange “12” Part 2
    • - E12 Advanced Features
      • 15:45-17:00, C המלך , הרודס
    • Local Continuous Replication (LCR)
    • Cluster Continuous Replication (CCR)
    • Calendar Improvements
    • Transport Security
    • And more …
  • References
    • Windows PowerShell (“Monad”) RC1 x86 http://www.microsoft.com/downloads/ details.aspx?familyid =2B0BBFCD-0797-4083-A817-5E6A054A85C9&displaylang=en