Exchange 2003 / 2010 Notes from the Field


Published on

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

Published in: Education
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

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 The example would be /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:<add key=”EnableResourceMonitoring” value=”true” />To:<add key=”EnableResourceMonitoring” value=”false” />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 for Exchange connectivity on intranet and 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 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 (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
  • 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
  • Exchange 2003 / 2010 Notes from the Field

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