Presentation is loading. Please wait.

Presentation is loading. Please wait.

Nathan Winters – MVP – Exchange Server Consultant – Dimension Data.

Similar presentations

Presentation on theme: "Nathan Winters – MVP – Exchange Server Consultant – Dimension Data."— Presentation transcript:

1 Nathan Winters – MVP – Exchange Server Consultant – Dimension Data

2 Agenda  Exchange 2007 – A Quick Intro  Planning for Exchange 2007  Designing Exchange 2007  Migrating to Exchange 2007  Documentation  Summary

3 Server Roles Forest Edge Transport server role Hub Transport server role Directory Server Mailbox server role Client Access server role Internet UM Server

4 Agenda  Exchange 2007 – A quick intro  Planning for Exchange 2007  Designing Exchange 2007  Migrating to Exchange 2007  Documentation  Summary

5 Planning Considerations  Active Directory Schema update Permission changes (Split Permissions Model) Some data exported/sync’d with Edge Transport server Windows Server 2003 SP1 or later required for; ○ At least one DC in each Site containing Exchange ○ Schema Master Windows 2000 Native or higher domain functional level  DNS Edge Transport resolution of Hub Transport server Autodiscover Single, unified internal namespace DNS Suffix for Edge Transport server

6 Planning Considerations  Hardware 64 Bit  Mailbox server role Standalone or clustered (CCR or SCC) Replication (LCR, CCR, SCR, 3 rd Party) Storage (DAS, SAN, iSCSI) Public Folders  Hub Transport server role Using Active Directory Sites for routing Exchange costs can override Site routing Built-in resilience/failover with multiple servers in Site

7 Planning Considerations  Client Access server role Protocols: EAS, HTTPS, POP3, IMAP4 Services: Availability, Autodiscover, Web Services Very different from Front-End servers in earlier versions ○ Optimize performance for Mailbox server role ○ Never put in a perimeter network ○ Internal, well-connected network (100 Mbps – 1 Gbps)  Unified Messaging server role Integrates telephony systems with Exchange ○ PBX, IP/PBX, VoIP Many new terms and technologies to learn

8 Planning Considerations  Edge Transport server role Designed for a perimeter network deployment Not a member of internal Active Directory forest/domain Can be a member of perimeter network forest/domain ○ Useful for management purposes (group policy, etc.) ○ MSIT does this Stores configuration data in local file and Active Directory Application Mode (ADAM) ○ Uses EdgeSync for one-way transfer of data from Active Directory to ADAM Minimal attack surface ○ TCP port 25, 50636, optional RDP port

9 Base Software Requirements for Exchange 2007  Windows Server 2003 x64 w/SP1 or R2, or SP2 Allows OWA users to browse the GAL  Microsoft.NET Framework 2.0  Windows PowerShell 1.0  Microsoft Management Console (MMC) 3.0  Hotfixes / Updates 272618_intl_x64_zip.exe (Edge) NDP20-KB926776-X64.exe (.NET update) WindowsServerver2003.WindowsXP-KB918980-x64- ENU.exe (Windows Server Update) Windowsmedia10-kb917312-x64-intl.exe (UM).NET Framework 2.0 Service Pack 1 or hotfix from 942027

10 Windows 2008 Exchange Support  WS08 writeable DC’s are supported in environments that have the following Exchange Servers Exchange 2003 SP2 Exchange 2007 RTM Exchange 2007 SP1 WS08 RODC/ROGC's. No Exchange servers are RO aware  Exchange 2007 RTM and previous versions of Exchange are not supported for installation on a Windows 2008 server.  Exchange 2007 SP1 can be installed on a Windows 2008 server.

11 Functional Dependencies  Retain Exchange 2003 for: X400 Connector GroupWise Connector and Migration Tools Event Service NNTP OWA ○ PF Access ○ Outlook Mobile Access ○ SMIME Control

12 Agenda  Exchange 2007 – A quick intro  Planning for Exchange 2007  Designing Exchange 2007  Migrating to Exchange 2007  Documentation  Summary

13 Starting Off Right...  Getting real customer requirements is essential  Prioritise and validate those requirements  Write a Vision and Scope document – and get it agreed  Deal with changes through a change control process  If you don’t... It WILL creep

14 Architecture  Keep It Simple at all times  Forget empty forest roots  Carefully consider delegated admin models – they rarely work  Clustering is not the only answer  Make sure it is supportable!  Do some discovery - Measure existing systems – measure peak IOPS, mailflow, mailbox profile etc.  Know how to use Perfmon  Use ExBPA

15 Design Considerations  Sizing  Compliance  Archiving  WAN – Cached mode etc (Optimisation)  Client access methods  Existing IPT and Unified Messaging  Management and Reporting  Disaster Recovery – High Availability

16 Server Placement Considerations  Sites  CAS  Name space  Method of access  WAN links

17 Public Folders  Public Folders are widely used for sharing and DL archiving  SharePoint 2007 is another solution for sharing and DL archiving  All previous versions of Outlook and Exchange required Public Folders to be deployed.  Public Folders are required within an organization until: All Outlook clients are upgraded to Outlook 2007 All mailboxes have been migrated to Exchange 2007 No Public Folder applications are still used 07/07/26/migration-tools-from-kimmo- forss.aspx

18 Key Sizing Elements  Size for “peak average” not “peak peak” Monday morning Repeatable Busiest servers Not “average average”, either  Take a visual average  Know when to use percentiles Average active connections: 1441 Peak average connections: ~2100

19 Sizing Methodology Know thyself What is your definition of a “User” How do your users behave? Use the published resources Apply sizing best practices Utilize tools and help file resources Test, test and re-test Aim to achieve repeatable results

20 Sizing Resources and Testing Tools  Sizing Tools Microsoft’s Exchange Server 2007 Mailbox Server Role Storage Requirements Calculator  DiY Load Generator ESP JetStress  Info on MSIT’s deployment IT Showcase  Blogs, TechNet  White papers  System Center Capacity Planner 2007

21 Mailbox Server Sizing  CPU Up to 8 cores ~500 – 1,000 mailboxes / core All other roles have a ratio based on this number  Memory 2 – 5MB/mailbox + 2GB Also SG-dependent 32GB cost effective at RTM but no real maximum  Network Min Gbit With CCR use separate NICs for public and private networks Rules of Thumb

22 Mailbox Server Sizing  Disk Balance I/O and Capacity Content Indexing (online mode, OWA users) ○ +5% capacity onto database LUN size Overhead / white space ○ Target database size + 10% SLA factored into sizing ○ Max database size ○ Recovery Storage Group ○ Backup to Disk ○ Delete items retention default is 14 days (15 – 30% increase) CCR Considerations Cold State / Cache Warming impact Rules of Thumb

23 CAS Server Sizing  CPU Up to 4 cores 1:4 CAS:Mailbox cores  Memory 2 GB/core new! Heavy Outlook Anywhere access: 2GB+/core (16GB max new!)  Disk – sure, why not  Network Gbit recommended  64k connection limit Rules of Thumb Processor Memory Usage

24 Hub Transport Server Sizing  CPU  Memory 1GB/core; 16GB max Large queue scenarios ○ Per message overhead: 3K, per recipient overhead: 1K Edgesync (enterprise deployments) ○ 4K per mail-enabled object  Disk Separate mail.que and logs from system disks (RAID 10) Transport dumpster impact 4GB minimum free space or Back Pressure kicks in…. VM testing - bewareVM testing - beware  Network Gbit recommended Rules of Thumb With A/V and A/SWithout A/V and A/S Recommended max cores / server 84 Hub Cores / mailbox server cores 1:51:7

25 UM Server Sizing  CPU Up to 4 cores Multiple cores recommended if converting from.wav to.wma  Memory 1GB/core (2GB minimum) 4GB maximum  Disk Based on codec  Network Gbit recommended  Concurrency 60 users (WMA) 75 users (GSM) Equates to 2K – 10K user population per server Rules of Thumb CodecE2K7 RTME2K7 SP1 (W2K3) E2K7 SP1 (W2K8) WMA 60 70 80 GSM 75100+ Tests were conducted on a system with 4 GB RAM and 2 x 2-core, 4 Ghz processors

26 Agenda  Exchange 2007 – A quick intro  Planning for Exchange 2007  Designing Exchange 2007  Migrating to Exchange 2007  Documentation  Summary

27 Exchange Migration Methods Org A b. Inter Organisational a. Intra Organisational Org A Org B

28 Preparation  Base build server and install prerequisites  Patch server  Create OUs for server objects in AD  Move server machine accounts in to correct OUs  Create Exchange Full Administrator Service Account  Grant Domain, Ent and Schema Admins and Make Exchange 2003 Full admin  Copy the install files to each server - c:\software\Exchange2007  Create updates dir on each server - c:\software\Exchange2007Patches  Copy rollup 1 to updates dir (Note Error - currently manual)  Create binaries install location (New-Item -Type directory -Path "D:\Program Files\Microsoft\Exchange Server")  If not already in existence create Certificate Authority  Implement Link State suppression  Clean up accepted domains and recipient policies before deployment  Verify Server Build: Network config, Patching, IE version, Prerequisites

29 Exchange 2007 Setup Prepare AD Overview  /PrepareLegacyExchangePermissions For every Ex 200x ‘domainpreped’ domain For a specified domain  /PrepareSchema Apply legacy permissions if required Extend schema  /PrepareAD Apply legacy permissions if required Extend schema if required Create Exchange global objects Prepare local domain  /PrepareDomain For local domain For all domains For a specified domain

30 Verify the Schema Has Been Extended Exchange 2007 Service Pack 1 Schema Version 11116

31 Verify Prepare AD Exchange 2007 Security Groups  Setup creates five Exchange USG in the root domain  Exchange Administrative Group (FYDIBOHF23SPDLT)  Exchange Routing Group (DWBGZMFD01QNBJR)

32 Order of Deployment  Install server roles in this order: Client Access server role Hub Transport server role Mailbox server role Unified Messaging server role Edge Transport server role can be introduced at any time ○ Full functionality requires Hub Transport server and EdgeSync

33 Unattended Setup  /r:”c,m,u,h” /roles: ○ Hub Transport (H); Client Access (C); Edge (E); Mailbox (M); Unified Messaging (U); Management Tools (T) /mode: ○ Install, Uninstall, Upgrade, RecoverServer /TargetDir: /DomainController /prepareAD /prepareSchema /prepareLegacyExchangePermissions /NewProvisionedServer /OrganizationName /EnableLegacyOutlook /LegacyRoutingServer

34 Check Straight After Setup  Check the Application Event Log  Run the Get-ExchangeServer cmdlet  Parse through setup logs Get-SetupLog c:\exchangesetuplogs\ exchangesetup.log -error –tree  Enter Product Key  Run ExBPA

35 Exchange Setup Log Locations Log Files Located at… \ExchangeSetupLogs\... Contents \ExchangeSetup.logPrerequisite and system-readiness checks \ExchangeSetup.msilogContains extraction of the Exchange 2007 code from the installer file \Install-ServerRole-yymmdd-hhmmss.txtConfiguration of Exchange for each role. Each role will generate a separate log file. \Install-ExchangeOrganization- InternalTaskLogyymmddhhmmss.txt Creation of default containers and setting of default permissions \SetupLogs\ldif.logSchema installation for Active Directory Application Mode (ADAM) \Prereqs\...ExBPAyymmddhhmmss.logResults of ExBPA pre-req scan

36 Understanding success or failure Learning to trust setup  Simple return codes 0 for success 1 for failure  The right data in the log ExchangeSetup.log, found in the ExchangeSetupLogs directory of your system drive Errors and Warnings are uniformly annotated Success/Failure messages are unambiguous [5/25/2006 3:32:05 PM] [0] The Microsoft Exchange Server setup operation completed successfully. [5/25/2006 3:32:05 PM] [0] End of Setup  get-setuplog.msh used to parse log

37 Role Specific Post Setup Tasks CASMailboxHubEdgeUM Configure Certificates for SSL Configure OAB distribution Create postmaster mailboxSubscribe the Edge Transport Server Configure Dial Plan Configure Outlook Anywhere Configure / upgrade Address Lists Configure Transport and Journaling Rules Configure Anti-Spam/Anti- Virus Configure UM IP Gateway Configure ActiveSync and ActiveSync policies Configure Managed Folder Mailbox Policy Start EdgeSync Configure DisclaimersConfigure UM Mailbox Policy Create AutoDiscover DNS Record Configure OOFConfigure backpressure settingsConfigure quarantine mailboxConfigure UM Auto Attendant Set Ext URLs where required Configure BackupConfigure connectors & accepted domains Enable Users for UM Split logs and databasesConfigure Anti-Spam Agents if not using Edge Replicate public FoldersConsider connection logging Setup SGs and DBsSet mail size limits Setup Replication (SCR, CCR, LCR) Set how the server identifies itself when sending mail Migrate Mailboxes and Resource mailboxes Allow internal servers to send mail Configure or Migrate email address policies

38 Non Role Specific Tasks  Baseline Performance  Security – SCW  Create and Test your DR plan  Ensure DNS Reverse lookup and Sender ID records are setup correctly  Monitor the Basics  Permission/Role Delegation  Training  Documentation! Regularly perform documentation updates  Regularly run ExBPA  Administration delegation  Deploy Outlook 2007

39 Move Mailbox Preparation  Required permissions Exchange Recipient Administrator Exchange Server Administrator Member of Local Administrators group  Transaction logs increase  Single instance storage loss (potential)  User mailbox cleanup

40 Bulk Migration Options  User  Database  Server Move-mailbox –identity bond –targetdatabase “007E2K7\first storage group\mailbox database” Get-mailbox –database “009E2K3dc1\First Storage Group\Mailbox Store (009E2K3dc1)” | move-mailbox – targetdatabase “007E2K7\first storage group\mailbox database” Get-mailbox –server “009E2K3dc1” | move-mailbox – targetdatabase “007E2K7\first storage group\mailbox database”

41 Post-Mailbox Migration Confirmation: Event Viewer  Event IDs 1006 9354 1007

42 Decommissioning Things to consider…  Reroute mail to target environment  Ensure all mail has been moved  Ensure all public folders have been re-homed.

43 Agenda  Exchange 2007 – A quick intro  Planning for Exchange 2007  Designing Exchange 2007  Migrating to Exchange 2007  Documentation  Summary

44 Script It!  Let’s take a look at some scripts…….

45 Agenda  Exchange 2007 – A quick intro  Planning for Exchange 2007  Designing Exchange 2007  Migrating to Exchange 2007  Documentation  Summary

46 Summary  Prepare!  Planning  Discovery  Requirements  Testing  Sizing  Server Placement  Communication


Download ppt "Nathan Winters – MVP – Exchange Server Consultant – Dimension Data."

Similar presentations

Ads by Google