Visit some of the different stages of a
deployment and avoid speed bumps.
Help you build a list of relevant sessions
over the next few days.
Envision: Establish a project vision, define & analyze requirements, and develop a solution
architecture & high level design
Plan: Develop the detailed design and create the functional specification
Build: Test environment build, validation of solution, develop the detailed build guide.
Stabilize: Production pilot to remediate any issues and establish approved processes before full
deployment.
Deploy: Complete the overall deployment and transition to day to day operations.
From an existing Exchange Server 2010 environment
E2010 Servers
E2010 CAS
E2010 HUB
autodiscover.contoso.com
mail.contoso.com
E2010 MBX
Intranet site
Internet facing site
Non-Internet facing site
From an existing Exchange Server 2010 environment
E2010 Servers
E2013 CAS
E2013 CAS
E2010 CAS
E2010 HUB
autodiscover.contoso.com
mail.contoso.com
Internet facing site
E2013 MBX
E2013 MBX
E2010 MBX
Intranet site
Non-Internet facing site
Speaker: Boris Lokhvitsky
Date: Wednesday, April 2
Time: 10:15 AM - 11:30 AM
Room: L4: Ballroom G
Session Type: Interactive
Session Code: ARC.IN.302
Don’t mount that horse just yet, cowboy!
Have you gathered your tools yet?
Exchange Server Deployment Assistant
Exchange Best Practices Analyzer
Remote Connectivity Analyzer (aka ExRCA)
“
Where does he get such wonderful toys?
–Joker
”
Current Exchange 2013 & Cloud Scenarios
 On-premises deployments



New installation of Exchange Server 2013
Upgrade from Exchange 2007 or 2010 to Exchange 2013
Upgrade from mixed Exchange 2007 and Exchange 2010 to
Exchange 2013
 Hybrid deployments (On-premises + Office 365)

Exchange 2013 on-premises with Exchange Online
 Cloud-only Scenarios




Exchange Cut-over
Exchange Staged
Exchange IMAP
Third-party IMAP
Access it here:
http://aka.ms/ExDeploy
Future Scenarios
 Multi-forest
Session
Best Practices Analyzer Next Generation
Speaker: Mark Heneen
Date: Tuesday, April 1
Time: 1:30 PM - 2:45 PM
Room: MR 11a
Session Type: Interactive
Session Code: MNG.IN.201
Start healthy!
Are we even working today?
Autodiscover
Download the MSI
to run locally!
ActiveSync
Exchange Web Services
Outlook Anywhere
Inbound/Outbound SMTP
Run it here:POP/IMAP
http://testconnectivity.microsoft.com
Server Profile Analyzer (For Exchange 2007 migrations only)
Exchange 2013 Server Role Requirements Calculator
Also touching on:
MessageStats.ps1
GetLogFileUsage.ps1
Processor Query Tool
Session
Session
Plan it the right way Exchange Server 2013 sizing
scenarios
Tame the beast Exchange server calculator tips
and tricks
Wizard: Jeff Mealiffe
Speaker: Brian Day
Date: Tuesday, April 1
Time: 1:30 PM - 2:45 PM
Room: Ballroom E
Session Type: Breakout
Session Code: ARC.308
Date: Wednesday, April 2
Time: 1:00 PM - 2:15 PM
Room: MR 11a
Session Type: Interactive
Session Code: ARC.IN.305
LoadGen
JetStress
Session
Session
Jetstress Notes From the Field
How to uncover the secrets
of Disk Latency
Speaker: Neil Johnson
Speaker: Alessandro Goncalves
Date: Tuesday, April 1
Time: 3:00 PM - 4:15 PM
Room: MR 19ab
Session Type: Breakout
Session Code: DMI.314
Date: Wednesday, April 2
Time: 4:45 PM – 6:00 PM
Room: MR 19ab
Session Type: Breakout
Session Code: MNG.302
Client network connectivity bandwidth calculator v2
Session
Exchange Client Network
Bandwidth calculator v2
Speaker: Neil Johnson
Date: Wednesday, April 2
Time: 2:45 PM – 4:00 PM
Room: MR 19ab
Session Type: Breakout
Session Code: DMI.303
Preparing for Exchange Server 2013
Active Directory Minimum Requirements
At least one Windows Server 2003 SP2 or higher* Global Catalog in each AD site with Exchange installed
*Use of Windows Server 2012 R2 requires a supported Exchange version
At least one writable Domain Controller in each AD site with Exchange Servers installed
AD Forest Functional Level must be Windows Server 2003 or higher
For the latest information see:
http://aka.ms/exchangesupportmatrix
Preparing for Exchange Server 2013
Operating Systems Prerequisites for Exchange Installs
Windows Server 2008 R2 SP1 64-bit Standard or Enterprise editions
Standard edition ok for CAS-only & non-DAG MBX
Enterprise edition necessary for DAG joined MBX
Windows Server 2012 or 2012 R2 64-bit Standard or Datacenter editions
2012 R2 is only supported with 2013 Service Pack 1 or later
.NET framework 4.5 (4.5.1 strongly recommended, may even be come a requirement)
Windows Management Framework 3.0
Unified Communications Managed API (UCMA) 4.0
Other expected OS roles/features (IIS etc…)
Preparing for Exchange Server 2013
Recent Windows Server 2012 R2 Support Updates
2013 SP1 or later
Install on 2012 R2
2012 R2 DCs and a 2012 or lower
DFL/FFL
2012 R2 DCs and a 2012 R2 DFL/FFL
2013 CU3 or earlier
2010 SP3 RU5
or later
2007 SP3 RU13
or later
Preparing for Exchange Server 2013
Outlook Recommendations
Office 365 ProPlus
Outlook 2013
Outlook 2010
Outlook 2007
Outlook 2003
– Current bits
– SP1 & latest public update recommended
– SP2 & latest public update recommended
– SP3 & latest public update recommended
– Not supported
WebDAV based clients must be upgraded to Exchange Web Services compatible versions:
Outlook for Mac 2011 or Entourage 2008 for Mac Web Services Edition
Browser recommendations (not minimums)
Internet Explorer: IE11 or IE10
Firefox: Latest or N-1
Chrome: Latest or N-1
Safari: Latest or N-1
Support Expires
Extended
Support
April
Expires
8th 2014
April 8th 2014
Exchangeto
Upgrade
2013
Service
cannot
Pack
coexist
3
with 2003
Preparing for Exchange Server 2013
Ready the existing Exchange organization
Patch existing Exchange servers to…
Exchange 2010 SP3 RU5 or later recommended
Exchange 2007 SP3 RU13 or later recommended
This includes Edge Transport servers
Extend the AD schema for Exchange Server 2013 setup /PrepareSchema
Prepare the Exchange organization and local domain for Exchange Server 2013 setup /PrepareAD
Prepare any remaining domains that will have mail enabled objects, Exchange servers, or Global
Catalog servers Exchange will utilize
Local domain setup /PrepareDomain
Remote domains one at a time setup /PrepareDomain:FQDN.of.domain
Or do them all at once setup /PrepareAllDomains
Preparing for Exchange Server 2013
An OAB modification before installing the first Exchange 2013 servers.
Exchange 2013 creates a new default OAB for the org.
[PS] C:\>Get-OfflineAddressBook | FT Name,IsDefault,ExchangeVersion -AutoSize
IsDefault Exchange Version
Name
----
Default Offline Address Book
Default Offline Address Book (Ex2013)
--------- --------------False 0.1 (8.0.535.0)
True 0.20 (15.0.0.0)
Avoid clients downloading the new default OAB by specifying the existing OAB on all legacy DBs
prior to installing Exchange 2013
[PS] C:\Windows\system32>Get-MailboxDatabase | FT NAME, *offline*,exchangeversion -AutoSize
Name
----
OfflineAddressBook
------------------
Exchange Version
---------------
Mailbox Database 2128912305 \Default Offline Address Book 0.10 (14.0.100.0)
Exchange Server 2013 SP1 Setup
Install both MBX and CAS Servers
CAS is auth/proxy only
MBX executes the PowerShell commands
Use the latest CU package
No more SP then RU install
Exchange 2013 Setup
GUI or command line
Updated to reflect Exchange 2013 roles
Command line parameters
New required parameter for license terms acceptance
After the Fact
You cannot remove individual roles in Exchange 2013
Setup.exe /mode:install /roles:c,m,mt /IAcceptExchangeServerLicenseTerms
Exchange Server 2013 Setup
What may show up after setup completes if you are not careful? Any guesses?
Exchange Server 2013 Setup
How do I prevent certificate pop-ups?
[PS] C:\>Get-ClientAccessServer | Sort-Object WhenCreated | FT Identity,WhenCreated,*SiteScope,*uri -AutoSize
Identity
-------CON-E2K7-001
WhenCreated
----------1/7/2014 1:21:15 PM
AutoDiscoverSiteScope
AutodiscoverServiceInternalUri
-------------------------------------------------{Boston}
https://bos.mail.corp.contoso.com/Autodiscover/Autodiscover.xml
CON-E2K10-001
1/8/2014 5:27:49 PM
{Boston}
https://bos.mail.corp.contoso.com/Autodiscover/Autodiscover.xml
CON-E2K13-001
1/16/2014 3:21:32 PM
{Boston}
https://bos.mail.corp.contoso.com/Autodiscover/Autodiscover.xml
CON-E2K13-101
1/16/2014 8:41:46 PM
{Seattle}
https://autodiscover.corp.contoso.com/Autodiscover/Autodiscover.xml
CON-E2K13-102
1/16/2014 9:22:43 PM
{Seattle}
https://autodiscover.corp.contoso.com/Autodiscover/Autodiscover.xml
CON-E2K13-002
1/17/2014 11:21:35 AM {Boston}
https://bos.mail.corp.contoso.com/Autodiscover/Autodiscover.xml
What other unexpected thing may happen after setup completes if you are not careful?
E2010 HUB
E2010 HUB
E2010 MBX
E2010 HUB
E2010 HUB
E2013 MBX
E2013 CAS
E2010 MBX
Cross-site lookie
mail flow…
many
paths…
manyoptions!
options.
Ooohhhh
someso
new
2013
boxes!soMore
Boston AD Site
Austin AD Site
Certificates
End to end certificate wizard in the Exchange Administration Center (EAC)
Export and import with private key to all other CAS right from the UI
Assign services right from the UI
EAC notifications when a certificate is about to expire
First notification will be shown 30 days prior to expiration
Subsequent notifications will be provided every 24 hours
Certificates - Best Practices
Minimize the number of certificates
A unified namespace means the same cert should be used on all CAS in the site resilient
datacenter pair
Use a “Subject Alternative Name” (SAN) certificate
Minimize number of hostnames
Use “Split DNS” for Exchange hostnames if using the same auth type inside and out
This is not a requirement, some customers may have unique environments where different names
would be helpful.
Don’t list machine hostnames in certificate hostname list*
*The UM service may be your exception to this rule due to telephony systems having to talk
direct to it, but you can easily use an internally issued certificate here.
Use Load Balanced (LB) CAS arrays for intranet and Internet access to servers
Certificates - Best Practices
Using a wildcard certificate
Did your Outlook Providers look like this previously when using a wildcard cert?
Name CertPrincipalName
---- -----------------
EXCH
EXPR msstd:*.contoso.com
WEB
Outlook Anywhere settings are now dynamically generated off of both the EXCH and EXPR Outlook
Providers for separate internal and external settings for clients to utilize. As a result of this update
both of the EXCH and EXPR Outlook providers must be wildcard ready in order to use a wildcard
certificate.
Name CertPrincipalName
---- -----------------
EXCH msstd:*.contoso.com
EXPR msstd:*.contoso.com
WEB
E2010 Servers
E2013 CAS
E2013 CAS
E2010 CAS
E2010 HUB
autodiscover.contoso.com
mail.contoso.com
Internet facing site
E2013 MBX
E2013 MBX
E2010 MBX
Intranet site
Non-Internet facing site
Legacy URL considerations for the following
OWA
EWS
OAB
Switching to CAS 2013
Drop TTL of any DNS records you will be changing in advance
Re-test via Remote Connectivity Analyzer one last time
Reconfigure Virtual Directory Settings of Legacy Systems if necessary
Reconfigure Outlook Anywhere on Legacy Systems if necessary
Move systems into the production AD sites if necessary
Update Publishing methods (Load Balancer, Reverse Proxy, etc…) if necessary
Update DNS records
Test via Remote Connectivity Analyzer once DNS updates propagate
You did this in your lab already, right?
Script it as much as you can.
Prepare your virtual directory change scripts in advance.
Huemans ah errar prone.
Prepare a back-out script just…. in…. case.
Switching to CAS 2013
Outlook Anywhere
1. Enable Outlook Anywhere on all legacy CAS
Utilize the ‘mail.contoso.com’ namespace for all
CAS so traffic flows through 2013 in all cases.
mail.contoso.com
RPC/HTTP
Layer 7 LB
Layer 4 LB
RPC/HTTP
2. IIS Authentication Methods
RPC
E2013 MBX
E2007/
E2010 MBX
RPC
3. DNS Cutover if an IP change takes place
Use a low TTL on the existing records a few
days in advance of the cutover.
OA Disabled
Enabled
Client Auth: Basic
IIS Auth: NTLM
RPC
2007/
E2010 MBX
OA Enabled
Client Auth: Basic
IIS Auth: NTLM
OA Enabled
Client Auth: Basic
IIS Auth: Basic
NTLM
Internet facing site
HTTP
PROXY
E2007/
E2010 CAS
E2007/
E2010 CAS
HTTP
PROXY
E2013 CAS
IIS Auth must have NTLM enabled on all legacy
CAS
Intranet facing site
Session
Outlook Connectivity: Current and Future
Speakers: Venkat Ayyadevara
Rafiq El Alami, and Guy Groeneveld
Date: Wednesday, April 2
Time: 10:15 AM – 11:30 AM
Room: Ballroom F
Session Type: Breakout
Session Code: USX.207
Session
Session
Publishing Exchange –
Which TLA Should You
Choose?
WAP and ARR – TMG
Alternatives?
Speaker: Greg Taylor
Speakers: Georg Hinterhofer,
Roop Sankar
Date: Tuesday, April 1
Time: 3:30 PM – 4:15 PM
Room: Ballroom F
Session Type: Breakout
Session Code: ARC.202
Date: Wednesday, April 2
Time: 8:30 AM – 9:45 AM
Room: MR 18bc
Session Type: Breakout
Session Code: USX.305
Edge Setup on Exchange 2013 SP1
One pre-req
Active Directory Lightweight
Directory Services (ADLDS)
Go no further!
Only install the ADLDS feature, Edge will take care of the rest during install.
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Users\Administrator> Install-WindowsFeature ADLDS
Success Restart Needed Exit Code
Feature Result
------- -------------- ---------------------Success
{Active Directory Lightweight Directory Se...
True
No
WARNING: To create a new AD LDS instance on server, log on to the destination server and then run the Active Directory
Lightweight Directory Services Setup Wizard. For more information, see http://go.microsoft.com/fwlink/?LinkId=224859
PS C:\Users\Administrator>
Edge Setup on Exchange 2013 SP1
The ‘other’ pre-req you may hit
Make sure your machine has a FQDN if it is not joined to a management domain.
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites
COMPLETED
FAILED
Prerequisite Analysis
The fully qualified domain name of the computer is missing or empty. Setup
cannot continue.
For more information, visit: http://technet.Microsoft.com/library<EXCHG.150
>/ms.exch.setupreadiness.FqdnMissing.aspx
Edge Setup on Exchange 2013 SP1
Adding a FQDN for non-domain joined
machines
Head on over to the Computer Name settings, it is
hidden under the ‘More…’ section.
Edge Setup on Exchange 2013 SP1
Create your Edge Subscription file
New-EdgeSubscription –File C:\EdgeServerSubscription.xml
[PS] C:\>New—EdgeSubscription -FileName c:\edgesubscription.xml
Confirm
If you create an Edge Subscription, this Edge Transport server will be managed via EdgeSync replication. As a result, any
of the following objects that were created manually will be deleted: accepted domains, message classifications, remote
domains, and Send connectors. After creating the Edge Subscription, you must manage these objects from inside the
organization and allow EdgeSync to update the Edge Transport server. Also, the InternalSMTPServers list of the
TransportConfig object will be overwritten during the synchronization process.
EdgeSync requires that this Edge Transport server is able to resolve the FQDN of the Mailbox servers in the Active
Directory site to which the Edge Transport server is being subscribed, and those Mailbox servers be able to resolve the
FQDN of this Edge Transport server. You should complete the Edge Subscription inside the organization in the next“1440”
minutes before the bootstrap account expires.
[Y] Yes
[A] Yes to All
[N] No
[L] No to All
[S] Suspend
[?] Help (default is "Y"): y
[PS] C:\>
Make sure the file is in a location your mailbox server can access for the next step.
Edge Setup on Exchange 2013 SP1
Import your Edge Subscription file (this would be a one-liner)
New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path “C:\EdgeServerSubscription.xml”
-Encoding Byte -ReadCount 0)) -Site “Seattle”
[PS] C:\Windows\system32> New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path "C:\EdgeServerSubscription.xml"Encoding Byte -ReadCount 0)) -Site "Seattle"
Name
Site
Domain
---------CON—E2K13—EDG01 corp.contoso.com/... corp.contoso.com
WARNING: EdgeSync requires that the Mailbox servers in Active Directory site Seattle be able to resolve the IP address
for CON—E2K13—EDG01.corp.contoso.com and be able to connect to that host on port 50636.
[PS] C:\Windows\system32>
Edge Setup on Exchange 2013 SP1
Edge is now known to the org
Edge server shows up in server list.
[PS] C:\>Get-ExchangeServer | Sort-Object Name | FT Name,ServerRole,AdminDisplayVersion -AutoSize
Name
ServerRole AdminDisplayVersion
------------- ------------------Mailbox, ClientAccess, UnifiedMessaging, HubTransport Version 14.3 (Build 123.4)
CON-E2K10-001
Mailbox, ClientAccessVersion 15.0 (Build 847.32)
CON-E2K13-001
Mailbox, ClientAccessVersion 15.0 (Build 847.32)
CON-E2K13-002
Mailbox, ClientAccessVersion 15.0 (Build 847.32)
CON-E2K13-101
Mailbox, ClientAccessVersion 15.0 (Build 847.32)
CON-E2K13-102
Edge 15.0 (Build 847.32)
CON-E2K13-EDG01
CON-E2K7-001
Mailbox, ClientAccess, UnifiedMessaging, HubTransport Version 8.3 (Build 83.6)
The two send connectors are generated
(Note: SourceTransportServers is the name of the edge subscription, which is the name of the first Edge server used when the connectors are created.)
[PS] C:\Windows\system32>Get-SendConnector | ft identity,sourcetrans* -AutoSize
Identity
SourceTransportServers
----------------------------EdgeSync – Seattle to Internet {CON-E2K13-EDG01}
EdgeSync – Inbound to Seattle {CON-E2K13-EDG01}
[PS] C:\Windows\system32>
Edge Support, and Mail Flow Transition
Edge Transport
Edge Transport 2007/2010 are compatible with Exchange 2013 CU1 or later
Edge Transport 2013 SP1 is compatible with 2013 SP1, 2010 SP3 RU5, and 2007 SP3 RU13
Legacy Edge Transport servers require the same 2010 SP3 or 2007 SP3 RU10 updates before deploying Exchange 2013.
An existing 2010 Edge Subscription must be re-created after SP3 is applied so the version number is seen by Exchange
2013 within the AD configuration partition or else setup will fail at the pre-req check.
Mail Flow Transition
Exchange Server 2013 can accept inbound anonymous mail from the Internet and re-route to the
correct 2013 or legacy mailbox(es)
Leave MX record(s) pointing to legacy Exchange early on, unless you deploy Edge 2013 first
Move MX record(s) to point to 2013 once approximately 50% of users are moved to 2013
Edge Transport with…
EOP standalone or Hybrid mail flow
Kerberos Authentication
Kerberos is preferred to help remove NTLM authentication bottlenecks in large Exchange environments.
Kerberos is not enabled by default in Exchange 2013 and requires manual configuration.
OAB virtual directories are already Applications within IIS in Exchange 2013, no need to convert them as
you did in Exchange 2010.
Enabling Kerberos in Exchange 2013 results in setting Negotiate as the authentication type for Outlook
Anywhere’s (/rpc) virtual directory InternalClientAuthenticationMethod and MAPI/HTTP’s (/mapi) virtual
directory IISAuthenticationMethod.
To Kerb or not to Kerb…
Are you pure 2013?
Yes.
No.
Do you have
legacy public
folders?
Enable Kerberos for
/rpc & /mapi vDirs
Yes.
Yes.
Do you have
CU5 deployed?*
No.
Migrate public folders to
Exchange 2013
* Tentative plan, plans may change.
Kerberos Authentication
A little bit of everything in a complex environment….
Kerberos Authentication
Exchange 2013 requires only http ServicePrincipalNames due to all client traffic being HTTP.
[PS] C:\>SetSpn –L EXASA213
Registered ServicePrincipalNames for CN=EXASA2013,CN=Users,DC=corp,DC=contoso,DC=com:
http/bos.mail.corp.contoso.com
http/aus.mail.corp.contoso.com
http/mail.corp.contoso.com
http/autodiscover.corp.contoso.com
[PS] C:\>
No longer necessary are exchangeAB, exchangeRFR, or exchangeMDB SPNs for a 2013-only ASA
Kerberos Authentication
What are our options?
Re-use the Exchange 2010 ASA (if one exists) with new human-known credentials
Pro: One ASA for both Exchange 2010 and Exchange 2013 in the org
Con: The credentials are now known to administrators instead of machine generated.
Create a new ASA for 2013
Pro: Can utilize RollAlternateServiceAccountPassword.ps1 against 2013 multi-role servers
Con: Service Principal Names must be moved from the 2010 ASA (if one exits) to the new ASA for
any hostname you will be moving from 2010 to 2013
Kerberos Authentication
A couple current caveats to be aware of as of SP1
RollAlternateServiceAccountPassword.ps1
Cannot be used to copy ASA credentials from 2010 CAS role to 2013 CAS role
Cannot be used to create a new ASA on CAS-only 2013 servers
Can be used to create a new ASA on multi-role 2013 servers
Set-ClientAccessServer -AlternateServiceAccountCredential only works on multi-role 2013 servers
Exchange Server 2013 Public Folders
The last thing you migrate.
2007/2010 users cannot access 2013 Public Folders
2013 users can access 2007/2010 Public Folders
Cutover migration, you cannot gradually move Public Folders from legacy to 2013
Session
Session
Modern Public Folder
Migration & Office 365
Experts Unplugged: Public
Folders & Site Mailboxes
Speakers: Kanika Ramji &
Siegfried Jagott
Speakers: Alfons Staerk, Kanika
Ramji, Shashi Singaravel,
Siegfried Jagott, Brian Day
Date: Monday, March 31
Time: 4:30 PM – 5:45 PM
Room: MR 19ab
Session Type: Breakout
Session Code: DMI.310
Date: Tuesday, April 1
Time: 9:00 AM – 10:15 AM
Room: MR 18d
Session Type: Unplugged
Session Code: USX.UN.303
OABs Downloads
Do you have or play to have multiple OABGen capable mailboxes?
Know that client OAB downloads from different OABGen mailboxes triggers a full download
even if it is the same OAB being downloaded.
How to find your OABGen mailbox(es)
[PS] C:\>Get-Mailbox –Arbitration | Where {$_.PersistedCapabilities –like "*OAB*"} | FL Name,Database,Persis*
Name
: SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
: 2013DB-001
Database
PersistedCapabilities : {OrganizationCapabilityUMGrammarReady, OrganizationCapabilityPstProvider,
: OrganizationCapabilityMessageTracking, OrganizationCapabilityMailRouting,
: OrganizationCapabilityClientExtensions, OrganizationCapabilityGMGen,
: OrganizationCapabilityOABGen, OrganizationCapabilityUMGrammar}
: OABGen02
Name
: 2013DB-003
Database
PersistedCapabilities : {OrganizationCapabilityOABGen}
OAB Downloads
How does this happen to clients? You may have OABGen mailboxes in different or same AD
sites.
[PS] C:\>Get-MailboxDatabase
Name
---2013DB-001
2013DB-002
2013DB-003
2013DB-004
2013DB-005
2013DB-006
Servers
-------{CON-E2K13-001}
{CON-E2K13-001}
{CON-E2K13-101}
{CON-E2K13-102}
{CON-E2K13-101}
{CON-E2K13-002}
[PS] C:\>Get-Mailbox –Arbitration | Where {$_.PersistedCapabilities
–AutoSize
Name
---OABGen02
SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
[PS] C:\>
[PS] C:\>Get-ExchangeServer | Where {$_.AdminDisplayVersion –like "*15*"} | Name,Site
Name
---CON-E2K13-001
CON-E2K13-002
CON-E2K13-101
CON-E2K13-102
CON-E2K13-EDG01
Site
---corp.contoso.com/Configuration/Sites/Boston
corp.contoso.com/Configuration/Sites/Boston
corp.contoso.com/Configuration/Sites/Seattle
corp.contoso.com/Configuration/Sites/Seattle
corp.contoso.com/Configuration/Sites/Seattle
Database
-------2013DB-003
2013DB-001
OAB Downloads
Could we place different OABGen mailboxes in DBs only replicated locally?
Site A
Site B
OABGen-02
OABGen-01
DAG-001
No, in this example the DAG spans two sites and user mailboxes will move between sites.
OAB Downloads
Recommendation: Keep one OABGen mailbox per organization.
Site B
OABGen-01
DAG-001
Site A
OABGen-01
or
Site B
DAG-001
OABGen-01
Site A
Recommended due to
site resiliency gains.
Quota Calculations
Mailbox and Public Folder data moved from legacy Exchange to Exchange 2013 will appear to
grow due to more accurate calculations within the DB.
Expectation is 30%-40% increase in quota hit, but will vary based on the content types
May want to increase the quotas of any user using ~75% or more of their quota prior to
moving them to 2013
The database size on disk does NOT increase
Coming in Exchange 2013 Cumulative Update 5