• Save
Exchange 2003 / 2010 Notes from the Field
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Exchange 2003 / 2010 Notes from the Field

  • 3,815 views
Uploaded on

This was the presentation that I gave at Techdays Canada 2010 on Exchange 2003/2007 - 2010 -- Notes from the field.

This was the presentation that I gave at Techdays Canada 2010 on Exchange 2003/2007 - 2010 -- Notes from the field.

More in: Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,815
On Slideshare
3,815
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • What’s New / Different Since Exchange Server 2003 and 2007Notes from the field: Backpressure and general tweaks to exchange pre-migration Client Support (Outlook, Web, Mobile) to Exchange 2010 Exchange 2010 Pre-Reqs and Exchange 2003 CoExistence (Cool Pre-Requisite Scripts that will save your life) Preparation Tools (Troublshooting Asst, LoadGen, Best Practice Analyzer)Exchange Transitions and Certificates!Exchange CAS 2010 ImplicationSMTP Transport UpgradesUnified Messaging UpgradesPublic Folders and Exchange 2010Retiring Exchange 2003 / Exchange 2007
  • Front-End / Back-End ->Client Access / Mailbox / Hub Transport / Edge Transport / Unified Messaging64-bit servers supportActive Directory Sites replace Routing GroupsAutodiscover to automatically configure clientsRemoves Outlook 2007+ need for Public FoldersAvailability Service: Free/Busy information read direct from mailboxes, not from Public FoldersOffline Address Book download from Client Access ServerNew admin toolsExchange Management Console (EMC) and PowerShell 1.0Unified Messaging: Get voice mail in your inboxNew Developer API: Exchange Web Services (EWS)
  • Run Exchange Server on-premises, use Exchange Online or mix and match?High Availability solution for mailboxes isDatabase Availability Groups (DAG)Provides site resilience and disaster recovery30-second fail-over with simplified admin experienceFlexibility in storage choices (SATA disks, JBOD configs, etc.)Replaces SCR, LCR, SCC and CCR from E2007Simplified Prerequisite Installation using input files from the DVDOnly 64-bit Management tools or Remote PowerShellRPC Client Access and Address Book serviceImproved High Availability solutionOutlook MAPI connects directly to Client Access ServersExOLEDB, WebDAV and CDOEx are gone“Entourage Web Services Edition” uses EWS
  • Fully functional, although…Outlook 2003 by default does not encrypt client to Exchange communicationsOutlook 2007 / 2010 by default DOES encrypt client to Exchange communicationsOption 1: Make Exchange 2010 NOT communicated encrypted with clientSimple to do (PowerShell on all CAS servers)Set-rpcClientAccess –server {servername} –encryptionRequired $falseAlthough “dumbs down” the client to Exchange 2010 securityOption 2: Enable encryption in Outlook 2003 to communicated with Exchange 2010 in an encrypted mannerCan be done through Group Policy Object (KB Article# 2006508)
  • Option 1: Make Exchange 2010 NOT communicated encrypted with clientSimple to do (PowerShell on all CAS servers)Set-rpcClientAccess –server {servername} –encryptionRequired $falseAlthough “dumbs down” the client to Exchange 2010 securityOption 2: Enable encryption in Outlook 2003 to communicated with Exchange 2010 in an encrypted mannerCan be done through Group Policy Object (KB Article# 2006508)
  • Outlook 2003 in Online ModeAn issue exists where Outlook 2003 clients are slow when configured in Online mode. Users will notice things like moving items between folders and deleting items are slow (the item doesn’t move immediately). Cached mode resolves this issue or alternatively you can follow these steps. Note that this fix does not completely resolve the issue, but it does improve performance of Outlook 2003 online mode a lot.On the server with the Client Access RoleInstall Exchange 2010 Update Rollup 1 and restart the server. Now make the following registry change. HKLMCurrentControlSetServicesMSExchangeRPCParametersSystemCreate a DWORD called ”Maximum Polling Frequency” (without quotes) Make the value 10000Note that this change is dynamic and clients will need to close and open Outlook again for the change to take affect.Another things you can do to reduce the user impact include:turning off the preview pane. advising users to open the message and delete the open message, rather than deleting from the Inbox.
  • In this demo you will install the Exchange 2010 Pre-Requisites on a Windows 2008 R2 Server.This Script will go out to the internet and download things like the Filter Pack etc.Your lead in for this should be – you need to ensure you manually have the following:Active DirectoryWindows 2003 SP2 global catalog serversWindows Server 2003 forest & domain functional levelExchangeService Pack 2 (Exchange 2003/2007)No Exchange 2000To install Exchange 2010 on a machineWindows Server 2008 SP2 or R2 64-bit editions (Std/Ent)Windows Management Framework.NET Framework 3.5 SP1 Internet Information Services (IIS)Why not just Script it all !!
  • If you are about to install Exchange 2010, one of the checks in your checklist should be Update Rollup 1 for Exchange 2010. This would come after you have installed Exchange 2010 on your server. But what if I tell you that you can slipstream RU1 with your Exchange setup?All you have to do is populate a folder with RU installer and use /UpdatesDir switch with setup.com. The example would be setup.com /role:mailbox /UpdatesDir:”C:ExchangeSourcesRUs”. Once this command successfully completes, you will see that the exchange install is complete and your determined patches from the UpdatesDir are applied to the server in single step! Isn’t that a thing of beauty?Exchange Server Update Rollups are cumulative so you don’t need to have RU1 installer if you build a new server with RU2 in future. All you need is RU2 installer file in UpdatesDir and exchange source to install from.There are many other useful switches to automate Exchange 2010 setup. you can find the reference on Technet.
  • You will want to talk through what Backpressure is:It turns out that Exchange 2010 back pressure handling has a major difference from Exchange 2007. In 2007, if disk space or CPU become a bottleneck, the transport will stop accepting SMTP connections. In Exchange 2010, it will still accept the connections, it just won't accept the messages. There are also some nuances (explained here), too. For example, the transport will attempt to keep accepting messages from other Exchange servers unless resources get really, really tight; the first thing it stops doing is accepting messages from external servers.Reference KB201658 for more info.
  • Talk to the calculation this switch uses – Exchange 2010 writes in 32KB Pages thus / 32KBExchange 2007 writes in 8KB pages thus / 8KBIf you don’t use this setting and have consolidated your roles – For example – Typical – HUB/CAS/MBX on one server.Then they will be competing for resources with the CAS Server – Which is also set to optimize memory.Database count Exchange 2010 minimum required physical memory 1-10 2 GB 11-20 4 GB21-30 6 GB31-40 8 GB41-50 10 GB51-60 12 GB61-70 14 GB71-80 16 GB81-90 18 GB91-100 20 GB
  • To Disable BackpressureTo disable Back Pressure:Go to C:Program FilesMicrosoftExchange ServerBin directory and open the EdgeTransport.exe.config file using notepad.Change the value of EnableResourceMonitoring from True to False:To:Save file and Restart Microsoft Exchange Transport Service.To modify the maximum size of the store.exe – You must use ADSI Edit
  • Use “Subject Alternative Name” (SAN) certificate which can cover multiple hostnamesMinimize the number of certificates1 certificate for all CAS servers + reverse proxy + Edge/HubMinimize number of hostnamesUse “Split DNS” for Exchange hostnamesmail.contoso.com for Exchange connectivity on intranet and Internetmail.contoso.com has different IP addresses in intranet/Internet DNSDon’t list machine hostnames in certificate hostname listUse Load Balance (LB) arrays for intranet and Internet access to servers
  • In this demo we will use Digicert’s universal Powershell script creator to built our Powershell script.Then we will use an internal Microsoft CA to install and assign the certificate to EX2010
  • OWA and EWS load balancing require ClientServer affinityClient-IP based Windows NLB or LB device using cookie-based affinityTell Autodiscover where to send clients: Configure internalURL and externalURL parameters and virtual directoriesExample: Set-WebServicesVirtualDirectory cas2010ews* -ExternalURL https://mail.contoso.com/ews/exchange.asmxTell Outlook clients where to go for intranet MAPI accessUse New-ClientAccessArray and Set-MailboxDatabase
  • Obtain and deploy a new certificate that includes the required host name valuesmail.contoso.comautodiscover.contoso.comlegacy.contoso.com (for coexistence)Upgrade all Exchange servers to Service Pack 2Enable Integrated Windows Authentication on Exchange 2003 MSAS virtual directory (KB 937031)Install and configure CAS2010 serversConfigure InternalURLs and ExternalURLsEnable Outlook AnywhereConfigure the Exchange2003URL parameter to be https://legacy.contoso.com/exchange
  • Join CAS2010 to a load balanced arrayCreate CAS2010 RPC Client Access Service arrayEnsure MAPI RPC and HTTPS ports are load balancedInstall HUB2010 and MBX2010 serversConfigure routing coexistenceCreate Legacy hostname in internal DNSCreate Legacy publishing rules in your reverse proxy/firewall solution pointed to FE2003 / CAS2007 arrayUse ExRCA to verify connectivity for Legacy hostname against E2003/E2007
  • The switchover involves a minor service interruptionUpdate/Create Autodiscover publishing ruleUpdate Mail publishing rulesUpdate paths with new Exchange 2010 specific virtual directoriesSwitch: Move Mail… and Autodiscover… hostnames to point to CAS2010 arrayReconfigure CAS2007 internalURLs and externalURLs to now utilize Legacy namespaceDisable Outlook Anywhere on legacy ExchangeTest that CAS2010 is redirecting/ proxying to CAS2007 (externally and internally)
  • IP PBXes and GWsConfigure to send all traffic to E2010 UME2010 UM will redirect to E2007 UM when necessaryOffice Communications Server (OCS)With E2010 RTM, create new dial plan for E2010 UM usersSoon: OCS will automatically talk to E2010 UM, which will redirect to E2007 UM when necessary
  • Co-existence support between mailbox server 2010 and mailbox server 2003/2007Outlook can read mailbox from one Exchange version (such as 2010) and public folder from another (such as 2003/2007)OWA 2010 will allow access to public folders with replica in mailbox server 2010Get-PublicFolderStatistics help take actionMoveDeleteMigrate to SharePoint
  • Users remain online while their mailboxes are moved between serversSending messagesReceiving messagesAccessing entire mailboxAdministrators can perform migration and maintenance during regular hoursAlso can be used to migrate users from on-premises server to Exchange Online1GB mailbox could take 90 minutes or more to movePain: User is disconnected for the durationPain: Your SLA for availability is not met
  • DO NOT REMOVE THIS SLIDE
  • DO NOT REMOVE THIS SLIDE
  • DO NOT REMOVE THIS SLIDE

Transcript

  • 1. Upgrading from Microsoft Exchange Server 2003/2007 to Exchange Server 2010:Tips, Tricks, and Lessons Learned
    Required Slide
    Dave Kawula
    Principal Consultant
    TriCon Technical Services Inc.
    dkawula@triconts.com
    www.triconts.com
    BLOG – www.insidetheregistry.com
  • 2. Consultant Summary
    Dave Kawula
    Principal Consultant
    Calgary , Alberta
    TriCon Technical Services Inc.
    dkawula@triconts.com
    www.triconts.com
    www.insidetheregistry.com
    We specialize in building and integrating  fully redundant systems - Hyper-V Clusters, ESX Farms, Xen Server Farms, Dual Core Networks, Operational Teams, MPIO, High Availability Exchange, High Availability SharePoint and High Availability SQL Solutions, OCS Mastery and a state-of-the-art training center to name a few.”
  • 3. Session Objectives and Takeaways
    Best Practices – Upgrading to Exchange 2010
    TIPS / Tricks -- Successful upgrades, including lessons learned
    Minimal Downtime - no significant user downtime
    Use the Deployment Assistant!
  • 4. Session Agenda
    What’s New and Different
    Exchange 2003 Co-Existence
    Notes from the field – Tips & Tricks
    Exchange Transitions and Certificates!
    Exchange CAS 2010 Implication
    SMTP Transport Upgrades
    Unified Messaging Upgrades
    Public Folders and Exchange 2010
  • 5. New since Exchange Server 2003
    More Granular Roles
    64-bit servers required
    Routing Groups Depricated
    Autodiscover
    Schedule Free+Busy / OAB
    Outlook 2003 use Public Folders
    Outlook 2007/2010 use Availability and Exchange Web Services
    New admin tools
    Unified Messaging Integration
    New Developer API
  • 6. New since Exchange Server 2007
    On-premises and Exchange Online
    Database Availability Groups (DAG)
    Simplified Installation
    Only 64-bit Management tools or Remote PowerShell
    RPC Client Access and Address Book service
    ExOLEDB, WebDAV and CDOEx are gone
  • 7. Upgrading to Exchange 2010
    Internet Facing AD Site
    2
    Deploy E2010 Servers
    Upgrade Internet-facing sites FIRST
    • Start small
    • 8. Gradually add more servers to support scale
    Internal AD Site
    4
    Move Infra Pointers
    • Internet hostname switch
    • 9. Unified Messaging switch
    • 10. SMTP switch
    Proxy
    https://autodiscover.contoso.com
    https://mail.contoso.com
    5
    Internet
    Move Mailboxes
    https://legacy.contoso.com
    E200x Servers
    https://autodiscover.contoso.com
    https://mail.contoso.com
    Legacy hostnames for old FE/CAS
    3
    1
    Upgrade servers to SP2
    • SSL cert purchase
    • 11. End users don’t see this hostname
    • 12. Used when new CAS tell clients to talk to legacy environments
    E200x Servers
    Upgrade Internal sites NEXT
    Decommission old servers
  • 13. Namespaces and URLs
    Exchange 2007
    Exchange 2010
    Exchange 2003
    mail.contoso.com
    mail.contoso.com
    mail.contoso.com
    Outlook Web Access
    /exchange, /exchweb, /public
    Exchange ActiveSync
    /microsoft-server-activesync
    Outlook Anywhere
    /rpc
    POP/IMAP
    Outlook Mobile Access
    /oma
    Outlook Web Access
    /owa
    Exchange Web Services
    /ews
    Offline Address Book
    /oab
    Unified Messaging
    /unifiedmessaging
    Outlook Mobile Access
    /oma
    Exchange Control Panel
    /ecp
    Unified Messaging
    /unifiedmessaging
    Note: the /exchange and /public vdirs will provide a 301 redirect experience to /owa
    Autodiscover.contoso.com
    smtp.contoso.com
    legacy.contoso.com
    E2003/E2007 services
    Autodiscover
    /autodiscover
    Clients and SMTP servers
  • 14. Notes from the field
    Ensure your new Exchange Farm is tuned up
  • 15. TIP # 1 – Outlook 2003 & Encryption
    Fully functional, although…
    Does not encrypt MAPI by default
    Online Performance Issues
    Must be at Service Pack 3 (Outlook)
  • 16. TIP # 1 – Outlook 2003 & Encryption – Con’t
    Set-rpcClientAccess –server {servername} –encryptionRequired $false
  • 17. Tip #2 – Slow Outlook 2003
    HKLMCurrentControlSetServicesMSExchangeRPCParametersSystem
    New DWORD = Maximum Polling Frequency
    Value = 10000
    For more information – KB 2009942
  • 18. Tip # 3 – Custom Pre-Requisite Script
  • 19. Tip # 4 - Slipstream Installations
    Download & Copy updates to c:ExchangeSourcesRU
    setup.com /role:mailbox /UpdatesDir:”C:ExchangeSourcesRUs”
  • 20. Tip # 5 – Tune Backpressure
    220 TESTEXC1.testing.local Microsoft ESMTP MAIL Service ready atTue, 24 Jul 2007 13:47:21 +1000helo250 TESTEXC1.testing.local Hello [10.1.1.11]mail from: test@test.com
    452 4.3.1 Insufficient system resources
    Reference – KB201658
    By default it is enabled on every Exchange 2007/2010 Hub Transport Server
  • 21. Tip # 6 – Tune Store.exe
    msExchESEparamCacheSizeMax
    Example – to Set 4 GB max size for Store.exe
    Exchange 2010
    4194304 KB / 32KB = 131072
    Exchange 2007
    4194304 KB / 8KB = 524288
    http://technet.microsoft.com/en-us/library/ee832793.aspx
  • 22. Tuning Store.exe & Backpressure
  • 23. Preparation Tools
    Troubleshooting Assistant
    Help determine the cause of performance, mail flow, and database issues
    Load Generator
    Simulate and test how a server responds to e-mail loads
    Best Practice Analyzer
    Remote Connectivity Analyzer
    Determine overall health of Exchange system and topology
    Test external connectivity to Exchange messaging communications resources
  • 24. Tip # 7 Remote Connectivity Analyzer
    https://www.testexchangeconnectivity.com/
  • 25. Tip # 8 Deployment Assistant
    http://technet.microsoft.com/exdeploy2010
  • 26. Deploying SSL Certificates
    Use “Subject Alternative Name” (SAN) certificate which can cover multiple hostnames
    Minimize the number of certificates
    Minimize number of hostnames
    Don’t list machine hostnames in certificate hostname list
  • 27. Tip # 9 – Certificates the easy way
  • 28. Deploying Exchange 2010
    Internal URL
    External URL
    Example: Set-WebServicesVirtualDirectory cas2010ews* -ExternalURL https://mail.contoso.com/ews/exchange.asmx
    Intranet MAPI Access
    Use New-ClientAccessArray and Set-MailboxDatabase
  • 29. Switching to CAS2010
    Deploy New Certificate
    mail.contoso.com
    autodiscover.contoso.com
    legacy.contoso.com (for coexistence)
    Upgrade all Exchange servers to Service Pack 2
    Enable Integrated Windows Authentication on Exchange 2003 MSAS virtual directory (KB 937031)
    Install and configure CAS2010 servers
    Configure InternalURLs and ExternalURLs
    Enable Outlook Anywhere
    Configure the Exchange2003URL parameter to be https://legacy.contoso.com/exchange
  • 30. Switching to CAS2010
    If Required - CAS2010 to a load balanced array
    Install HUB2010 and MBX2010 servers
    Configure routing coexistence
    Create Legacy hostname in internal DNS
    Create Legacy publishing rules in your reverse proxy/firewall solution pointed to FE2003 / CAS2007 array
    Use ExRCA to verify connectivity for Legacy hostname against E2003/E2007
  • 31. Switching to CAS2010
    autodiscover…
    mail…
    legacy…
    The switchover involves a minor service interruption
    Update/Create Autodiscover publishing rule
    Update Mail publishing rules
    Update paths with new Exchange 2010 specific virtual directories
    Switch: Move Mail… and Autodiscover… hostnames to point to CAS2010 array
    Reconfigure CAS2007 internalURLs and externalURLs to now utilize Legacy namespace
    Disable Outlook Anywhere on legacy Exchange
    Test that CAS2010 is redirecting/ proxying to CAS2007 (externally and internally)
    ISA
    1
    2
    2
    E2010 CAS+HUB+MBX
    E200x SP2
    Clients access E2010 through Autodiscover… and mail…
    1
    Redirection (legacy…), proxying, and direct access to E2003/E2007
    2
  • 32. Switching to CAS 2010
  • 33. Client Access Upgrade
    Clients access CAS2010 first
    Four different things happen for E2003/ E2007 mailboxes
    Autodiscover tells clients to talk to CAS2007
    HTTP redirect to FE2003 or CAS2007
    Proxyingof requests from CAS2010 to CAS2007
    Direct CAS2010 support for the service against BE2003 and MBX2007
  • 34. SMTP Transport Upgrade
    Follow this flow for each physical location
    Edge servers are optional
    Edge 2007 SP2 can be used with HUB 2010
    Internet SMTP Servers
    Step 5:
    Switch Internet e-mail submission to Edge 2010
    Step 4:
    Install Edge 2010
    E2010 Edge
    E2007 Edge
    Step 3:
    Switch Edgesync +SMTP to go to HUB2010
    E2010 HUB
    E2007 HUB
    E2003 Bridgehead
    E2003 Back-End
    E2010 MBX
    E2007 MBX
    Step 1:
    Upgrade existing E2003 and E2007 servers to SP2
    Step 2:
    Install HUB and MBX 2010
  • 35. Unified Messaging Upgrade
    IP PBXes and GWs
    Office Communications Server (OCS)
  • 36. Public Folders
    Co-existence support
    OWA 2010
    Get-PublicFolderStatistics
    Move
    Delete
    Migrate to SharePoint
  • 37. Online Move Mailbox
    Minimal disruption
    E-mail Client
    Client Access Server
    Exchange 2010 and Exchange 2007 SP2 Online
    Exchange 2003 Offline
    Mailbox Server 1
    Mailbox Server 2
  • 38. Evaluations and Feedback
    Please fill out your evaluations!
    Remember: 9 = Good; 1 = Bad
    Let us know what you liked and disliked!
    Have your voice heard!
    Send us an email! td_can@microsoft.com