1. Implementing Exchange Server 2013
April 2014

2. About the Presenters Jeff Mealiffe Brian Shiers
Senior Product Marketing Manager
Office Deployment, Adoption & Readiness Team
Microsoft Corporation
Jeff Mealiffe
Principal Program Manager Lead
Brian Shiers at Technet

3. Course Topics Planning for Exchange Server 2013
01 | Upgrade and Deploy Exchange Server 2013
02 | Plan it the right way: Exchange Server 2013 Sizing
03 | Exchange Server 2013 Virtualization Best Practices
04 | High Availability and Site Resilience
05 | Outlook Connectivity

4. Plan it the right way: Exchange Server 2013 Sizing
8/26/ :56 AM
Plan it the right way: Exchange Server 2013 Sizing
Brian Shiers – Sr. Product Marketing Mgr., Microsoft
Jeff Mealiffe – Principal Program Manager Lead, Microsoft
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

5. Agenda Impact of 2013 architecture How to size Exchange 2013 roles
Tech Ready 15
8/26/2019
Agenda
Impact of 2013 architecture
How to size Exchange 2013 roles
The sizing model: caveats
Trust, but verify
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

6. Impact of 2013 architecture

7. Exchange architecture overview
MEC 2014
8/26/ :56 AM
Exchange architecture overview
Exchange 2013 targets balanced use of hardware
Consider hardware platforms that provide the right balance of resources
3 roles for sizing: Mailbox, Client Access Server, Active Directory AD
Web
browser
Outlook
(remote user)
Mobile
phone
Line of
business
application
Outlook (local user)
External
SMTP servers
Exchange
Online Protection
Enterprise Network
Phone system (PBX or VOIP)
Edge Transport
Routing and AV/AS
Layer 4LB
CAS Array
DAG
CAS
MBX
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

8. Mailbox got a promotion in 2013
Hub & CAS are “spending more time with their families”
Mailbox takes over responsibility for the old Hub & CAS components
Benefits
“Considerations”
Simplified deployment & connectivity model
Increased resource usage (see managed availability, content indexing in particular)
Cache efficiencies
Everything interacts (and workload management mediates)
Hardware efficiencies (balanced resource utilization)
Unified Messaging on all Mailbox servers

9. MEC 2014
8/26/ :56 AM
Whoa! CAS is back. Sort of?
We reincarnated the Client Access Server as a proxy
Benefits
“Considerations”
Stateless
Net-new role in 2013, adds performance “cost” – can potentially mitigate by shifting some resources from LB to CAS
Load balancing optimizations
Low CPU & memory footprint
Connection scalability
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10. How to size Exchange 2013 roles

11. Luke, use the calculator
MEC 2014
8/26/ :56 AM
Luke, use the calculator
No really, use it.
Calculator turns published sizing guidance into a modeling tool
Try out various failure scenarios
Understand the impact of different hardware & storage choices
Provides scripts for DAG, database & copy creation
Many new features
CAS sizing
Transport storage sizing
Multiple databases per-volume (JBOD) support
High availability architecture improvements
Note: Baseline platform for CPU guidance changed in Don’t directly compare results from 2010 & 2013 calculators.
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. Demo Exchange 2013 Role Requirements Calculator
8/26/ :56 AM
Demo
Exchange 2013 Role Requirements Calculator
That flat out faaaaabulous certificate wizard.
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

13. Demo Exchange 2013 Role Requirements Calculator
Microsoft Office365
8/26/2019
Demo
Exchange 2013 Role Requirements Calculator
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14. MEC 2014
8/26/ :56 AM
Multi-role: just do it
Very few reasons not to consider multi-role (Mailbox+CAS) deployment
Multi-role simplifies deployment, can reduce server count
Benefit of increased availability at the CAS layer
Issues remain with Windows NLB + DAG (WSFC)
Certificate management may be a concern
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

15. MEC 2014
8/26/ :56 AM
How low can you go?
Memory requirements have increased in Exchange 2013
Minimum CPU requirements follow published OS guidelines
Disk space requirements on install drive increased dramatically (lots of new logging turned on by default)
Mailbox or multi-role (Mailbox+CAS)
8GB minimum RAM
CAS
4GB minimum RAM
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16. Storage capacity requirements
MEC 2014
8/26/ :56 AM
Storage capacity requirements
Size for mailbox size on disk, content indexes, log space
Method for computing space requirement similar to Exchange 2010, with some important changes
20% database overhead is now 0%
CI size is now 20% of EDB
Plus space for additional index set per volume (master merge)
Note that impact of space for master merge is reduced with multiple DBs per-volume
May find that .edb is smaller than sum of mailbox size
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

17. MEC 2014
8/26/ :56 AM
IOPS Requirements
As in previous releases, Exchange 2013 reduced IOPS requirements (~33% reduction compared to 2010)
We have seen higher reduction in various tests, guidance is conservative and based on production observations
No separate guidance for HA vs. non-HA databases
Checkpoint depth is now consistent for all scenarios, so IOPS requirements are the same
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

18. Transport storage requirements
MEC 2014
8/26/ :56 AM
Transport storage requirements
Transport capacity requirements include queue and Safety Net
Guidance demonstrates method for calculating capacity requirements
Transport queue database takes advantage of ESE IO improvements to reduce IOPS
Microsoft production observations show ~1 DB IO per 75KB message
Low IOPS suggest that placing transport queue on system/install volume is now feasible in many scenarios
Significant transport throughput benefit seen from a protected write cache disk controller, set to 100% write cache
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

19. Processor requirements
MEC 2014
8/26/ :56 AM
Processor requirements
SP1
Messages sent or received per mailbox per day
Mcycles per User, Active DB Copy or Standalone (MBX only)
Mcycles per User, Active DB Copy or Standalone (Multi-Role)
Mcycles per User, Passive DB Copy 50
2.13
2.93
0.69
100
4.25
5.84
1.37
150
6.38
8.77
2.06
200
8.50
11.69
2.74
250
10.63
14.62
3.43
300
12.75
17.53
4.11
350
14.88
20.46
4.80
400
17.00
23.38
5.48
450
19.13
26.30
6.17
500
21.25
29.22
6.85
As in Exchange 2010, mcycle requirements are per-user for active & passive copies
Per-passive multiplier on the active has been removed in 2013
Guidance includes a multi- role mcycle requirement for the active copy – simplifies sizing
Note: Baseline platform for CPU guidance changed in Mcycle requirements in 2010 and 2013 cannot be directly compared.
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

20. Hyperthreading & Exchange 2013
MEC 2014
8/26/ :56 AM
Hyperthreading & Exchange 2013
Turn off hyperthreading (SMT)!
SMT provides gain in processor throughput, but overall the gain is not worth the “cost” based on our lab measurements
Significant impact to some Exchange service memory footprints
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

21. Tuning .NET for store Best practice to install KB 2803754 or 2803755
(Windows Server 2008 R2)
(Windows Server 2012)
Reduces memory consumption in each store worker
No impact to sizing guidance
Memory is available for use by other processes
Decreases CPU spent in .NET garbage collector
Benefits Mailbox & multi-role
Enable by installing hotfix and setting regkey:
HKLM\Software\Microsoft\.NETFramework\DisableRetStructPinning (REG_DWORD) = 1

22. MEC 2014
8/26/ :56 AM
Memory requirements
Messages sent or received per mailbox per day
Mailbox role memory per active mailbox (MB) 50 12
100 24
150 36
200 48
250 60
300 72
350 84
400 96
450
108
500
120
Memory on the Mailbox role sized based on ESE cache requirements
Cache requirements have remained constant from 2010
Overall cache sized to 25% of RAM, so guidance (based on total system memory) is 4x of 2010 cache sizing recommendation
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

23. Minimum physical memory (GB)
MEC 2014
8/26/ :56 AM
Memory requirements
Multi-role servers require additional memory for CAS based on user concurrency during worst-case failure
Minimum memory requirements based on database count must be observed to ensure optimal ESE cache utilization
2GB + 2GB × worst−case active DBs per−server×users per−DB×mbx mcycles per−user × per−core mcycles
SP1
Per-server DB copies
Minimum physical memory (GB)
1-10 8
11-20 10
21-30 12
31-40 14
41-50 16
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

24. Pagefile guidance MIN(RAM+10MB,32778MB)
MEC 2014
8/26/ :56 AM
Pagefile guidance
SP1
I like big pagefiles and I cannot lie…
Old guidance was “size of RAM + 10MB”
Exchange servers typically have lots of RAM, resulting in ridiculous pagefile sizes
New guidance for Exchange 2013 is to continue to use a fixed pagefile size, but cap pagefile at MB if using > 32GB RAM
MIN(RAM+10MB,32778MB)
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

25. Unified messaging UM is sized using a concurrency model
MEC 2014
8/26/ :56 AM
Unified messaging
UM is sized using a concurrency model
Plan for a maximum of 100 concurrent calls per server
Note that UM in 2013 is a component of the Mailbox role, may need to adjust user distribution to optimize UM utilization/concurrency
Voic transcription is a heavy consumer of CPU
Plan for 1 CPU core per concurrent transcription
If server is CPU starved, voic transcription may be skipped (voic delivered without transcription)
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

26. CAS processor requirements
MEC 2014
8/26/ :56 AM
CAS processor requirements
CAS CPU is sized using a percentage of Mailbox CPU active user requirements
2013 CAS requires 37.5% of Mailbox active-user mcycles, down from 75% in 2010
Given significant reduction, ensure that enough CAS servers are deployed to handle failures and provide high availability (particularly in small sites)
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

27. Wait… there’s something different here
MEC 2014
8/26/ :56 AM
Wait… there’s something different here
Yes, CAS CPU requirements just increased by 50% for SP1
Increase due to MAPI/HTTP architectural change
MAPI/HTTP disabled by default, but plan to enable eventually
CAS handling higher request rate, requests have a cost
Impact minimized for multi-role deployment
Existing deployments should ensure enough capacity before enabling MAPI/HTTP (disabled by default)
Deploy .NET Framework on CAS - optimize MAPI/HTTP performance
SP1
Dedicated Role Deployment Example
Customer
RTM Guidance
SP1 Guidance
Customer 1
23 CAS / Site
33 CAS / Site
Multi-Role Deployment Examples
Customer
RTM Guidance
SP1 Guidance
Customer 2
94% CPU at peak
102% CPU at peak
Customer 3
82%
88%
Customer 4
74%
80%
Customer 5
44%
47%
Customer 6
42%
45%
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

28. CAS memory requirements
MEC 2014
8/26/ :56 AM
CAS memory requirements
CAS memory is sized using a simple formula of 2GB + 2GB per-CPU core.
The per-core value assumes utilized CPU cores at peak (worst case failure), so this can get a little complicated
Note no CAS memory reduction from 2010, but decreased CAS server count should result in overall memory reduction
SP1
Per−server CAS memory=2GB+2GB× total user count CAS server count in worst case ×Mailbox mcycles per−user×0.375 mcycles per−core
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

29. Active Directory requirements
MEC 2014
8/26/ :56 AM
Active Directory requirements
Recommend deploying 1 AD GC core for every 8 Mailbox cores handling active load (assuming 64-bit GCs
Size memory such that the entire NTDS.DIT can be contained within RAM for optimal query performance
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

30. Size does matter How big is too big?
MEC 2014
8/26/ :56 AM
Size does matter
How big is too big?
Design for scale-out, not scale-up
Better alignment with intentions & design points of PG
Ideally focus on “commodity” 2U servers as a platform to help minimize deployment risk
We don’t push the “top end” today – and don’t want you to either
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

31. The sizing model: caveats

32. We don’t cover everything
MEC 2014
8/26/ :56 AM
We don’t cover everything
Sizing data is limited to the deployments we use to build our models
Not all client types or versions are covered
3rd party solutions generally not included
LOB applications
Hardware variations
Ongoing product changes
Feature enablement/usage
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

33. Sizing without guidance & tools
MEC 2014
8/26/ :56 AM
Sizing without guidance & tools
Lab testing with simulated workloads may be an option
Be conservative: overdeploy!
Consider extra safety margins when targeting “max” CPU
Consider a pilot
Minimize overdeployment
Size for high availability requirements (failure domains!), then migrate slowly while monitoring
Add more hardware as necessary based on monitoring
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

34. Trust, but verify

35. Jetstress & Exchange Solution Reviewed Program
MEC 2014
8/26/ :56 AM
Jetstress & Exchange Solution Reviewed Program
Jetstress 2013 released March 2013
Event log captured
Errors associated with specific volumes
Threads controlled globally instead of per-DB, better automatic tuning
Use Jetstress to validate all Exchange capacity before service ready
Validates storage performance & reliability
ESRP Storage v4.0 released last May to storage partners
~30 solutions available on ESRP site for Exchange 2013
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

36. Loadgen 2013 Loadgen 2013 released October 2013 Continued updates
Support for protocol & connection changes in Exchange 2013
Stability
Many bug fixes
Continued updates

37. Summary Exchange 2013 requires more HW resources than prior releases
Plan to deploy multi-role
Use the calculator
Be careful w/3rd party products & “exceptional” user profiles
Scale out, not up
Run Jetstress

38. More details available on the blog

39. 8/26/ :56 AM
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.