160 likes | 327 Views
Midwest Messaging and Collaboration User Group. Friday, November 8 th 2013. Exchange 2013 Sizing and Virtualization. Josh M. Bryant Premier Field Engineer. Agenda. Exchange 2013 Sizing Mad Libs Game Sizing Tools Minimums Virtualization Q & A. Exchange 2013 Sizing Mad Libs .
E N D
Midwest Messaging and Collaboration User Group Friday, November 8th 2013 Exchange 2013 Sizing and Virtualization Josh M. Bryant Premier Field Engineer
Agenda Exchange 2013 Sizing Mad Libs Game Sizing Tools Minimums Virtualization Q & A
Exchange 2013 Sizing Mad Libs • 9 Questions will be asked. • Each question should be answered by a different person. • Answers provided will be used to size the infamous Contoso Ltd.!
Sizing Tools • Exchange 2013 Server Role Requirements Calculator. • Exchange Processor Query Tool. • Exchange 2007/2010 Email Status script.
Minimums - Hardware • 64Bit CPU • 8GB RAM for MBX, 4GB for CAS, or 8GB for Multi-Role. • Page File = RAM + 10MB • 30GB Free on install drive plus 500MB for each language pack. • 200MB free on system drive. • 500MB free on queue drive. • Disks formatted as NTFS. • Screen Resolution of 1024x768 or higher.
Minumums - OS • Server roles require Server 2008 R2 SP1(Standard, Enterprise or Datacenter) or Server 2012 (Standard or Datacenter) • Management tools can also be loaded on 64-Bit Windows 7 or 8, with support for 8.1 coming soon. • WMF 3.0 only, earlier/later versions not supported.
Minimums - Clients • Outlook 2013. • Outlook 2010 SP1 with Nov 2012 update. • Outlook 2007 SP3 with Nov 2012 update. • Entourage 2008 for Mac, Web Services Edition. • Outlook for Mac 2011. • IE 7 or later. • Firefox 17 or later. • Safari 5 or later. • Chrome 24 or later.
Virtualization – Can I do it? • Yes! Virtualization is fully supported with Hyper-V or any third-party hypervisor that has been validated under the Windows Server Virtualization Validation Program. • Virtualization of ALL Exchange roles is supported. • Host-based failover clustering and migration technlogies are supported, but must result in cold boot or use technology similar to Hyper-V Live Migration for online migrations. • Snapshots are NOT supported. • Maximum of 2:1 virtual to physical CPU ratio, 1:1 recommended.
Virtualization – Can I do it? • Must use block level storage. • VHDs must be fixed size. • Exchange data should be placed on storage that is separate from the storage hosting guest VMs. • Do NOT use Dynamic Memory features, it is NOT supported and can result in severe performance problems.
Virtualization – Should I do it? • It depends! • Just because you can, doesn’t mean you should.
Thank you! Josh M. Bryant Premier Field Engineer