Transcript EXL305: Best Practices for Successfully Transitioning to

EXL305
More Tips / Fewer Clicks
Section 1
What’s the Same / What’s New /
What’s Different in Exchange 2010
(background on where things will trip you
up during the transition process)
Reduce IO/ sec req’d by 70%
 ¼ the disk
 4x more users
 Large inboxes
 Still uses EDB database structure (not SQL as
once rumored)
 No more .STM files (that were in Exchange 2003)
 2 billion log files  E0012345678.log (similar to
Exchange 2007)

64-bit E2010
When working with x64-bit
 Need to closely review add-ins to make sure they support 64-bit (anti-virus, fax
utils, gateway products, etc)
 RAM is critical (lots works better on mailbox servers, but diminishing return on
CAS and Hub Transport…)
Enterprise Network
Edge Transport
Routing & AV/AS
Phone system
(PBX or VOIP)
Hub Transport
Routing & Policy
External SMTP
servers
Mobile phone
Web browser
Mailbox
Storage of
mailbox items
Unified Messaging
Voice mail &
voice access
Client Access
Client connectivity
Web services
Outlook
(remote user)
Line of business
application
Outlook (local user)
Outlook
OWA, ActiveSync, or
Outlook Anywhere
San Jose
Front End Server
NodeA
(active)
Complex site resilience
and recovery
Dallas
DB1
DB2
Clustered Mailbox
Server had to be
created manually
NodeB
(passive)
Standby
Cluster
DB3
Third-party data
replication needed
for site resilience
Clustering knowledge
required
DB1
DB4
DB2
DB5
DB3
DB6
Failover at Mailbox
server level
Outlook
OWA, ActiveSync, or
Outlook Anywhere
SCR
Client Access
Server
DB3
No GUI to
manage SCR
NodeB
(passive)
CCR
DB1
DB2
Standby
Cluster
Clustered Mailbox
Server can’t co-exist
with other roles
San Jose
NodeA
(active)
Dallas
Complex activation for
remote server /
datacenter
Clustering knowledge
required
DB1
DB4
DB1
DB4
DB2
DB5
DB2
DB5
DB6
DB3
DB6
DB3
Failover at Mailbox
server level
Dallas
All clients connect via
CAS servers
DB1
DB2
DB3
San Jose
Mailbox Server 6
Easy to extend
across sites
Client Access Server
Failover managed
by/with Exchange
Mailbox Server 1
Mailbox Server 2
Mailbox Server 3
Mailbox Server 4
Mailbox Server 5
DB1
DB4
DB2
DB5
DB3
DB2
DB5
DB3
DB1
DB4
DB3
DB1
DB4
DB2
DB5
Database
level failover
“Integrating Apple Macs, iPads, iPhones into a Windows / Active Directory based environment” –
http://www.cco.com/online.htm (May 11, 2011 posted content)
“Authoritative Guide to Exchange Calendaring” – http://www.networkworld.com/community/morimoto
(July 20, 2010 posted content)
Section 2
Migration Process
Best Practices
Exchange 2007 Decommission Order:
Exchange 2003 Decommission Order:
1.
2.
3.
4.
5.
1. Mailbox server
2. SMTP
3. Front End
Mailbox server
Unified Messaging server
Hub Transport server
Client Access server
Edge Transport server
TIP!
Internet Facing AD Site
2
Deploy E2010 Servers
• Start small
• Gradually add more servers to
support scale
Upgrade Internet-facing
sites FIRST
4 Move Infra Pointers
• Internet hostname switch
• Unified Messaging switch
• SMTP switch
Internal AD Site
Internet
Proxy
5
Move Mailboxes
E200x Servers
hostnames for
3 Legacy
old FE/CAS
• SSL cert purchase
• End users don’t see this
hostname
• Used when new CAS tell clients
to talk to legacy environments
1
Upgrade servers to SP2
E200x Servers
Decommission old servers
Upgrade Internal sites NEXT
Simplify deployment and upgrades
Generates custom instructions on how to install or upgrade
to Exchange 2010
Help determine the cause of performance, mail flow, and
database issues
Verify Internet-facing services are set up
and configured properly
Determine overall health of Exchange system and topology
Directory Replication
Directory objects (users, computers, etc.)
File Replication Service
Domain
Controller
SYSVOL (logon scripts, policies, etc.)
Domain
Controller
Use ReplMon (in the Windows Support Tools on Windows CD) to validate
replication
Also use frsdiag.exe to confirm FRS replication
FRS replicates the SYSVOL, contains NETLOGON share, stores logon scripts and
system policies, contains Group Policies in separate folders
http://www.microsoft.com/windowsserver2003/downloads/featurepacks/default.aspx
AD Health Check Guide ($9.95 / 104-pages / step-by-step guide):
http://www.samspublishing.com/bookstore/product.asp?isbn=0768668425
Setup /PrepareLegacyExchangePermissions
Setup /PrepareSchema, /PrepareAD, /PrepareDomain
Add E2010 CAS server(s) in addition to existing E2003 FE /
E2007 CAS servers
Clients and SMTP servers
Autodiscover
/autodiscover
E2003/E2007 services
Preparatory steps
https://legacy.contoso.com/exchange
Preparatory steps, continued
Deploying SSL Certificates
Note
Note
New-ExchangeCertificate
-GenerateRequest
ImportExchangeCertificate
EnableExchangeCertificate
-Path c:\certificates\request.req
-SubjectName “c=US, o=contoso Inc,
cn=mail1.contoso.com”
-DomainName mail.contoso.com,
autodiscover.contoso.com,
legacy.contoso.com
-PrivateKeyExportable $true
Deploying Exchange 2010
Topology decisions—CAS load balancing
Note
Transition Planning
ActiveSync – 2003/2007
Activesync Error 85010014
Transition Planning
Offline Address Book (OAB)
http://blogs.msdn.com/b/dgoldman/archive/2009/02/23/a-new-build-of-oabinteg-has-been-posted-tothe-web.aspx
Transport Roles
Exchange 2010 resiliency improvements
Migration of Bridgehead / Hub Transport
Add Exchange 2010 Hub Transport servers in addition
to existing E2003 Bridgehead / E2007 HT servers
Transition Planning
Disabling Link State (for Exchange 2003 > 2010 Transitions)
HKLM\System\CurrentControlSet\Services\RESvc\Parameters
DWORD: SuppressStateChanges
Value: 1
More Details: http://technet.microsoft.com/en-us/library/aa996728.aspx
SMTP Transport Upgrade
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
E2003 Bridgehead
Step 1:
Upgrade existing E2003 and
E2007 servers to SP2
E2010 HUB
E2007 HUB
E2010 MBX
E2007 MBX
Step 2:
Install HUB and MBX 2010
E2003 Back-End
All-In-One Server Configuration
Branch office or smaller deployment
8 processor cores
recommended with a
maximum of 64GB
RAM
UM role not
recommended for colocation
CAS / HUB /
MAILBOX 1
CAS / HUB /
MAILBOX 2
Member servers of DAG can
host other server roles
DB2
2 server DAGs, with server
roles combined or not,
should use RAID
Migration of Mailboxes to E2010
Build Exchange 2010 Mailbox Server Role Systems
(including DAG replica servers (if desired))
Transition Planning
Upgrade LDAP to OPATH
Built-in Exchange 2010 Management Shell functions (see TechNet article below)
Ad
http://technet.microsoft.com/en-us/library/dd335105.aspx
http://blogs.technet.com/b/ilvancri/archive/2010/06/15/don-t-forget-to-update-your-ldap-filters-toopath-filters-when-transitioning-from-exchange-2003-to-exchange-2010.aspx
Online Move Mailbox
Minimal User Disruption
E-Mail Client
Client Access
Server
Mailbox Server 1
Mailbox Server 2
Unified Messaging / Unified Communications
Step 1:
Introduce UM 2010 to
existing dial plan
Step 2:
Route IP GW/PBX calls to
UM 2010 for dial plan
Step 3:
Remove UM 2007 after
mailboxes have been
moved
Integrating Exchange 2010 to Lync 2010: http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/
Integrating Exchange 2010 SP1 to OCS 2007: http://msundis.wordpress.com/2010/06/21/integrate-ocs-2007-r2-withexchange-server-2010-sp1-owa/
Public Folders
Retiring Exchange 2003 / 2007
Transition Planning
Removing the Last Exchange 2003 / 2007 Server from Org
http://technet.microsoft.com/en-us/library/gg576862.aspx
Mail Tips
Luciana Ramos;
SharePoint 2010 User Profile Sync Service: http://www.networkworld.com/community/morimoto “outlook pictures”
Things to Remember
My Schedule!
http://northamerica.msteched.com
www.microsoft.com/teched
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn