170 likes | 357 Views
Exchange 2013: Notes from the Field. Damian Scoles | Project Leadership Associates Microsoft Exchange Server MVP dscoles@projectleadership.net (312) 258-5378. Agenda. Before Installing Exchange Feature changes Tips and Best Practices for Different Features BES Installation issues
E N D
Exchange 2013:Notes from the Field Damian Scoles | Project Leadership Associates Microsoft Exchange Server MVP dscoles@projectleadership.net (312) 258-5378
Agenda • Before Installing Exchange • Feature changes • Tips and Best Practices for Different Features • BES • Installation issues • Coexistence • Public Folders
Exchange 2013 – Pre Installation • Exchange and Active Directory servers are up to date • Exchange 2007 SP3 RU10 or Exchange 2010 SP3 • Active Directory forest 2003 native or higher, but not 2012 R2 (not supported) • Active Directory Health Check • Exchange Best Practices Analyzer • Exchange Health Check Scripts • Get-DagHeath- http://exchangeserverpro.com (MVP Blog) • Test-ExchangeServerHealth - http://exchangeserverpro.com (MVP Blog) • Get-ExchangeEnvironmentReport - http://www.stevieg.org (MVP Blog) • Review Event Logs on your Active Directory and Exchange Servers • Review Third Party Software and Interaction with Exchange • BES • AntiVirus • Backup • … and more
Exchange 2013 – Planning • How many servers? • What kind of transition – staged/cutover? • Client expectations • Executive expectations • Pilot • Migration – timing and support
Exchange 2013 – Feature Changes • MRM and Retention Policy Transition • PowerShell Only • Diagnostic Logging • Detailed Active Sync Policies • Message Tracking Logs
Exchange 2013 –Miscellaneous Notes • Exchange 2013 Server Role Requirements Calculator • Storage – SAN vs local disk vs NAS • Personal Archives – Where to Put It? (SAS / SATA) • New Maximum database limit – 50 went to 100 (CPU and RAM req,) • Limit for Standard – 5 databases (Public Folders are included) • Outlook Up To Date • Outlook 2013 (15.0.4420.1017) • Outlook 2010 Service Pack 1 with the Outlook 2010 November 2012 • Outlook 2007 Service Pack 3 with the Outlook 2007 November 2012 • Entourage 2008 for Mac, Web Services Edition • Outlook for Mac 2011 • CAS Role Permanency with Mailbox Role • Exchange Server Deployment Assistant http://technet.microsoft.com/en-us/exchange/jj657516.aspx • Fix any client related issues • Microsoft Outlook Configuration Analyzer Tool 2.0 • Office Configuration Analyzer Tool • MAPI connections - CRM software
Exchange 2013 – BES Coexistence and Migration • Must configure MAPI manually using the latest MAPI/CDO released earlier this year • Installation guide by RIM is not complete • Missing steps • Some details are inaccurate • Harder MAPI configuration • Recommendation • Create a BES mailbox on Exchange 2013 • Install a second BES – configure for Exchange 2013 • Use the migration toolkit to move users • RIM Articles on BES with Exchange 2013 • KB24470 • KB16118
Exchange 2013 – Proxy Decisions` • TMG is dead, or is it? • If you have it, keep it as it is supported • Still can be purchased – appliance vendors • UAG is TMG+ • More features • More expensive • IIS AAR • Web proxy • No pre-authentication • HLB come with reverse proxies now • Kemp • F5 • Or nothing at all --> Exchange 2013 managed code http://blogs.technet.com/b/exchange/archive/2013/07/17/life-in-a-post-tmg-world-is-it-as-scary-as-you-think.aspx
Exchange 2013 – SMTP Relays • Considerations • What relays though Exchange? • What can be changed to a new server easily – IP or DNS name • How to configure new connectors • FrontEndvsHubTransport • How to migrate existing ranges to new server • PowerShell – RemoteIP Ranges • What not to do
Exchange 2013 – Public Folder Migrations • Do you need to migrate this data? • SharePoint option • Shared Mailbox option – if calendar • Know how much data you have • This will impact migration timing • How many mailboxes are needed • Cutover to 2013 • All users need to be migrated • Test users need to check: • Permissions • Content • Bad Characters • Bad / Corrupt Items • Failback to previous version and then move back to 2013\ • If migration fails, what other options?
Exchange 2013 – CAS Coexistence • Exchange 2007 to 2013 • Legacy namespace • Certificate change • URL changes needed • Exchange 2010 to 2013 • No certificate changes • No Legacy Namespace • Legacy needs to be inside and outside • Inside for OWA and ActiveSync (redirection) • Outside for OWA. OWA will change the URL in your browser to Legacy if it detects your mailbox is on a older server (Exchange 2007)
Exchange 2013 - Installation Tips / Issues • Prerequisite Scripts Instead of Manual • Script for URL configuration • To prevent certificate pop-ups – after any Exchange 2013 CAS installation • Set the AutoDiscoverServiceInternalUri to $null until coexistence (2013) • Configure to the proper URI for CAS coexistence (2013) • Manage Exchange 2013 before pilot? • Move one user over otherwise EAC is inaccessible. • Must be done from Exchange 2013 due to MRS. Must be done in PowerShell. • AutoDiscover and Pop-ups • Disable AutoDiscoverInternalServiceURI --> Set it to $null
Exchange 2013 & O365 • Single Sign On? Federation? Seamless • Recommend ADFS and DirSync • DirSync • No HA • Easy to rebuild • High Availability Option • Attachment Limits – 25 MB • Export or delete • Then Migrate Mailbox (Archive Too) Microsoft Confidential
Q & A Damian Scoles | Project Leadership Associates Microsoft Exchange Server MVP dscoles@projectleadership.net (312) 258-5378