1. Virtualisation in Microsoft Exchange Server 2013
12/4/ :43 AM
EXL326
Virtualisation in Microsoft Exchange Server 2013
Sandy Millar
Avanade Australia
© 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.

2. Session Outline
Who is in the room Why are we here History lesson Right Now What do you need to think about Avoiding issues Wrap up

3. Who Am I?
Sandy Millar I work for Avanade in Canberra Exchange MCM/MCA Designed and implemented Exchange solutions since v4.0 Currently working on a global Office 365 implementation

4. Who Are You?
Who manages Exchange platforms? Who designs Exchange solutions? Who has deployed Exchange 2013? Anyone passed MCSE: Messaging?

5. “So time to revisit our thinking”
TechEd 2013
12/4/ :43 AM
Why Are We Here?
To state the obvious, there is a new version of Exchange The architecture has changed Workload distribution has changed New virtual infrastructure options Increasing scalability requirements
“So time to revisit our thinking”
© 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.

6. History Lesson 8th version, 3rd generation April 1996 - Exchange 4.0
TechEd 2013
12/4/ :43 AM
History Lesson
8th version, 3rd generation
April Exchange 4.0
March 1997 – Exchange 5.0
November 1997 – Exchange 5.5
November 2000 – Exchange 2000
October 2003 – Exchange 2003
December 2006 – Exchange 2007
November 2009 – Exchange 2010
© 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.

7. Here we are today So what’s changed Fewer server roles
TechEd 2013
12/4/ :43 AM
Here we are today
So what’s changed
Fewer server roles
Relocated service functionality
Simplified data paths
Workload management
Improved administration tools
Public Folders architecture changed
Improved integration with Lync and SharePoint
Improved high availability and site resilience
© 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.

8. TechEd 2013
12/4/ :43 AM
© 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.

9. The First Question You Should Always Ask!
TechEd 2013
12/4/ :43 AM
The First Question You Should Always Ask!
“Why virtualise?”
There are some good reasons …
Improved hardware utilisation
Reduced hardware and software costs
Reduced power, cooling and data centre space
Server consolidation opportunities
Creates a homogenous infrastructure
© 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.

10. The Second Question Is ….
TechEd 2013
12/4/ :43 AM
The Second Question Is ….
“Why not?”
Equally there are some good reasons not too …
Increased complexity
Increased deployment steps
Performance impact
More management layers
Workload mismatch
Uncontrolled Virtual Sprawl
Cost
© 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.

11. TechEd 2013
12/4/ :43 AM
“Make sure you fully understand your options and objectives!” “Make sure you get something from virtualising!”
© 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.

12. What Do You Need To Think About?
TechEd 2013
12/4/ :43 AM
What Do You Need To Think About?
© 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. Solution Sizing

14. Sizing Considerations
TechEd 2013
12/4/ :43 AM
Sizing Considerations
Sizing methods for Exchange 2013 for physical and virtual hardware is the same
However you need to consider the impact of a shared virtual infrastructure
The tried and true method is using the “Role Requirements Calculator” …… IT WORKS!
Make sure you validate your assumptions and inputs
Make sure you correctly set the “Server Role Virtualisation” and “Hypervisor Adjustment Factor”
© 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.

15. Resource Impacts To Consider
TechEd 2013
12/4/ :43 AM
Resource Impacts To Consider
~10% for Hyper-V (follow vendors guidance for other hypervisors)
Memory is not normally impacted
Storage should be optimised for IO latency and high availability
Take advantage of hypervisor networking flexibility to provide availability and performance
In general: Size using guidance for physical, and apply that to virtual
© 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.

16. Co-location Considerations
TechEd 2013
12/4/ :43 AM
Co-location Considerations
Co-locating Exchange with other virtual machines and workloads
Use resource reservation options to ensure that Exchange gets what it needs
Allows other more suitable workloads to take advantage of resource over-commitment
Good practice: Never overcommit any resources in a way that could impact Exchange virtual machines
© 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.

17. Final Sizing Considerations
TechEd 2013
12/4/ :43 AM
Final Sizing Considerations
Avoid excessive scale-up to ensure high availability of Exchange services
Modern hypervisors are capable of hosting hundreds of virtual machines per host, that doesn’t mean you can or should
Plan for a small number of Exchange 2013 mailbox virtual machines per-host
Use remaining capacity for other workloads
© 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.

18. Virtualisation Supportability

19. Supported Hypervisors Host-based clustering Migration Exchange roles
TechEd 2013
12/4/ :43 AM
Supported
Hypervisors
Windows Server 2008 R2
Hyper-V Server 2008 R2
Windows Server 2012
Hyper-V Server 2012
Third-party hypervisors (SVVP)
Host-based clustering
Both Exchange 2013 roles supported
Migration
Both Exchange 2013 roles supported
Exchange roles
Both Exchange 2013 roles supported for virtualisation
Jetstress testing in guests
Supported Windows hypervisors or VMware® ESX™ 4.1 (or newer)
Storage
Block-level
Same requirements as Exchange 2010
© 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.

20. “Server Virtualisation Validation Program”
What Is “SVVP”?
“Server Virtualisation Validation Program”
This is an important resource to determine the supportability of Exchange on virtualised hardware!

21. The Windows Server 2012 Perspective
TechEd 2013
12/4/ :43 AM
The Windows Server 2012 Perspective
Server 2012 Hyper-V adds many new features
Many deployment-blocking limits removed
Customers that virtualise Exchange Server 2013 (and size correctly) will have a great experience on Server Hyper-V
Important to be aware of what does & doesn’t work (and supportability limits)
Resource
Windows Server 2008R2
Windows Server 2012
Improvement
Host
Logical Processors 64
320 5x
Physical memory
Virtual CPU per Host
1 TB
4 TB 4x
512
2,048 VM
Virtual CPU’s per VM 4
16x
Memory per VM
64 GB
Active VM’s per Host
384
1,024
2.7x
Guest NUMA No
Yes -
Cluster
Maximum Nodes 16
Maximum VM’s
1,000
8,000 8x
© 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.

22. New Storage Considerations
TechEd 2013
12/4/ :43 AM
New Storage Considerations
Exchange 2013 supports VHD/VHDX storage on SMB 3.0 file shares
Can be shares presented from Windows Server 2012 or other implementations of SMB 3.0
Specific to VHD/VHDX storage – no direct access to shares from Exchange
SMB 3.0 provides the ability to survive hardware failures that would otherwise impact file access
© 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.

23. What About SMB 3.0
Great platform for inexpensive, simple storage of Hyper-V virtual machines
Scalable to meet various levels of demand
Can use Exchange’s favorite “large low-cost disks” and take advantage of full functionality in the virtualisation stack

24. I Often Get Asked “Why not NFS?”
Performance
Particular NFS implementations have historically shown significant performance issues, and Exchange is very sensitive to high IO latencies
Reliability
Particular NFS implementations have shown reliability issues that can result in database corruption
NFS is a standard
There are many implementations, some better than others
“Given that there are a number of better alternatives for presenting storage to a hypervisor, Microsoft does not support NFS (or older versions of SMB)”

25. I Also Get Asked “What’s the story with VM migration?”
TechEd 2013
12/4/ :43 AM
I Also Get Asked “What’s the story with VM migration?”
Confusion exists about what Microsoft does or does not support with migration
Microsoft does support Live Migration and similar 3rd party technologies with bothExchange roles
Microsoft absolutely does not support Hyper-V’s Quick Migration or any other solution that saves point-in-time state to disk
© 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.

26. And … Why can’t I use my NAS?
TechEd 2013
12/4/ :43 AM
And … Why can’t I use my NAS?
Exchange data must be located on block-level storage
Exchange doesn't support NAS volumes, other than in the SMB 3.0 scenario
NAS storage presented to VM guests as block-level storage via the hypervisor is not supported
VM guest iSCSI initiators are supported, however beware of any VM network stack limitations
© 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.

27. TechEd 2013
12/4/ :43 AM
What Is Not Supported!
Dynamic memory, memory overcommit, memory reclamation
Not supported for any Exchange 2013 role
Configure static memory for all Exchange VMs
Apps on the parent partition
Only deploy management, monitoring, AV, etc.
Significant processor oversubscription
Limited to 2:1, best practice is 1:1
Hypervisor snapshots
Not supported for any Exchange 2013 role
Differencing/delta disks
Not supported for any Exchange 2013 role
© 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.

28. What Is Not Supported (continued)
Hyper-V replica
Replica provides DR for “any” VM via log shipping to a remote hypervisor
Use Data Availability (DAG) to obtain better HA & DR with Exchange 2010 & 2013
Replica makes sense for apps that don’t have DR capability built-in to the product
Windows Azure Infrastructure Services, AWS or similar

29. How To Avoid Problem Areas

30. Exchange Server Distribution
TechEd 2013
12/4/ :43 AM
Exchange Server Distribution
Understanding failure domains is critical for virtualised Exchange design
Placing multiple mailbox DB copies on the same infrastructure impacts availability
Placing any dependencies of Exchange on the same infrastructure also impacts availability
Equipment fails – accept failures and prepare for it with redundancy and multiple paths to infrastructure
© 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.

31. Get the storage right
Allocate sufficient storage for guests on the host
Allocate sufficient storage for Exchange within the guest
Don’t share spindles with the Host OS
Use supported disk configurations
Use fixed sized VHD/VHDX disks

32. Solid Foundations Host Based Failover Clustering “High Availability”
Using Host Based Failover Clustering and automatically failing VMs to an alternate cluster node in the event of a critical hardware issue
What you need to be aware of:
It is not an Exchange Aware Solution
Only protects against server hardware/network failure
There is no HA in the event of storage failure / data corruption
Requires a shared storage deployment
“If you are going to deploy this, combine with Exchange DAG when possible”

33. Best practice: “Static memory configuration for all Exchange VMs”
Forgotten Memory
Hyper-V’s Dynamic Memory and VMware’s Ballooning are fantastic for certain workloads and lab environments
For production Exchange servers, just don’t do it!
Exchange code doesn’t deal well with disappearing memory
The end result for the mailbox role is DB cache served from the page file or very small DB cache
Best practice: “Static memory configuration for all Exchange VMs”

34. Dynamic memory impact TechEd 2013 12/4/2018 11:43 AM
© 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.

35. Where is my stethoscope?
TechEd 2013
12/4/ :43 AM
Where is my stethoscope?
Migration of Mailbox servers can result in cluster heartbeat timeouts
Result is eviction of server from cluster (DAG) and failover of active DB copies
Minimise brownout period
Consider carefully adjusting heartbeat timeout settings
Import-module FailoverClusters
(Get-Cluster).SameSubnetThreshold=5
(Get-Cluster).SameSubnetDelay=1000
© 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.

36. There Is No Such Thing As A TARDIS
TechEd 2013
12/4/ :43 AM
There Is No Such Thing As A TARDIS
Hypervisor snapshots make lab testing much easier
Resist the temptation to use hypervisor snapshots in production – they are not supported!
Aspects of the Exchange system do not handle time travel well (log shipping)
Use caution with snapshots in the lab (multiple machines may need to roll back simultaneously)
© 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.

37. TechEd 2013
12/4/ :43 AM
There Is No Magic Here
Hypervisors create a lot of solution opportunities… but they don’t make CPU appear out of thin air
While oversubscription can help with hardware consolidation, it doesn’t help provide reliable high-performance Exchange services
Proper Exchange sizing ensures that resources are available on- demand, so don’t allow hypervisors to snatch those resources away
CPU constrained Exchange servers will experience reduced throughput.
© 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.

38. Exchange Is Dynamic
Exchange 2013 contains a workload management component
WLM dynamically adjusts background tasks to ensure that resources are being consumed efficiently
WLM monitors resource consumption and makes decisions based on resource availability
Inconsistent resource assignment results in bad WLM decisions

39. Wrap Up
Virtualisation of Exchange 2013 is supported with few limitations
It’s important to understand when to virtualise Exchange – it’s not always the right choice
Don’t oversubscribe!
Exchange uses lots of memory – size properly and don’t rely on hypervisor “magic”
Processor resources are critical for Exchange client experience – ensure that Exchange always gets what it needs
Not all hypervisor features make sense for Exchange
Consider whether similar/same functionality built-in to Exchange may provide better availability or performance

40. Useful information
Exchange 2013 Server Role Requirements Calculator
Server Virtualisation Validation Program
Exchange 2013 Virtualisation
Exchange Server for IT pros
Best Practices for Virtualising & Manage Exchange 2013

41. Related content Breakout Sessions
12/4/ :43 AM
Related content
Breakout Sessions
EXL317 - Microsoft Exchange Server 2013 Sizing
EXL322 - Exchange 2013 High Availability & Site Resilience
SPT006 - Reasons and Methods to Shift your Legacy Infrastructure to Hyper-V on SMB3 by Massively Reducing Conversion Time and Data Migration
Find Me Later At...
© 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.

42. Track resources Exchange Server Documentation – http://aka.ms/E15Docs
12/4/ :43 AM
Track resources
Exchange Server Documentation –
Exchange Team Blog –
Lync Server Documentation -
Lync Server Team Blog –
Download Exchange and Lync Today!
Contact your Microsoft or Partner Account Manager to arrange a time test drive Exchange and Lync at the Office Showcase
© 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.

43. Questions
What are two reasons why you would implement Exchange 2013 on virtual hardware?
What does “SVVP” stand for, and why is it important?
What does “WLM” stand for?
What differentiator with supported and not supported disk infrastructure?

44. Resources Learning TechNet Developer Network
12/4/ :43 AM
Resources
Learning
Sessions on Demand
Virtual Academy
TechNet
Developer Network
Resources for IT Professionals
Resources for Developers
© 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.

45. TechEd 2012
12/4/ :43 AM
Keep Learning
Download both Exchange Server 2013 and Lync Server 2013 and try in your own environment
Trial Exchange and Lync Online
Contact your Microsoft or Partner Account Manager to arrange a time test drive Exchange and Lync in one of our Customer Immersion Experience Centres
Contact your Microsoft or Partner Account Manager to get a Lync business value assessment or an Exchange and Lync technical briefing
© 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.

46. 12/4/ :43 AM
© 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.
© 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.