4. Organizations want to: Reduce infrastructure costs Create more value and faster low-cost services Reduce Total Cost of Ownership Leverage existing resources and Server Consolidation Decrease hardware maintenance costs Reduce and standardize on common platform Better capacity planning Operational Efficiency Improve business continuity Increase operational flexibility Improve the server to administration ratio

5. Virtualize Workloads Designed to consume the full physical server capabilities Resource Abstraction Share infrastructure across many applications CPU Memory Network and Disk Utilize consistency via virtualization templates Why Virtualize? Lync Server 2013 Virtualized Workloads Supported Instant Messaging (IM) IM Conferencing Presence Enterprise Voice (PSTN) Audio/Video Conferencing Web Conferencing Application Sharing Remote Access, Federation (Edge Server) Response Group Service Persistent Chat Back-End Database Archiving/Monitoring Databases

7. Validated Hypervisors Windows Server 2012 Hyper-V Windows Hyper-V Server 2012 Other Hypervisors Windows Server 2012 R2 Hyper-V Windows Hyper-V Server 2012 R2

8. Not Recommended Windows 2008 R2 hypervisors are supported, but this is not recommended due to guests being limited to 4 cores making this unsuitable for all Lync Server roles. Windows Server 2008 R2 Hyper-V Windows Hyper-V Server 2008 R2 KB981836 “Network connection is lost on a Windows Server 2003-based Hyper-V VM” at http://go.microsoft.com/fwlink/?LinkId=201212)http://go.microsoft.com/fwlink/?LinkId=201212 Unsupported Hypervisors Windows Server 2008

9. Overhead Typically an overhead of 6-10% Above and beyond what the virtual guest requires Involves both CPU and Memory Net increase of physical servers due to virtualization layer Virtual Machine Image Templates Cannot run sysprep to create machine image templates after Lync Server 2013 is installed Recommend using custom OS templates with applicable prerequisites FEs could use templates for Internet Information Services (IIS) and Windows Media Format Runtime

10. Live Migration and Quick Migration Not supported Technical challenges redirecting real time media traffic without an interruption Can move a virtual machine running Lync Server between hosts Must be shut down prior to doing the activity An outage will be observed by a portion of the client base Any active conferences will be ended Memory Dynamic Memory not supported on any roles Memory must not be over provisioned, will starve other guest VMs

11. Virtual Disks Use fixed-sized disks Fixed-size VHDX delivers near native-to-physical performance Slightly higher performance than dynamically expanding VHDX files Differencing disks and dynamically expanding disks not supported Underlying Storage can become overcommitted Allocated fixed-sized virtual disks to a static amount of disk space Do not store system files on the same drives dedicated to storing VMs Creates disk contention issues Do not use checkpoints for the virtual machines Checkpointing creates a new secondary drive which causes reduce performance

12. Virtual IDE and SCSI Virtual IDE controller use to boot up virtual machine All other drives can be attached to virtual SCSI controller Virtual SCSI can have 64 connected disks per controller and 4 controllers per virtual machine (256 Virtual SCSI disks) Virtual SCSI supports hot-add/removal of disks, Virtual IDE disk do not Ensure optimal performance and greatest flexibility Virtualized Lync Server 2013 can use fibre channel storage solutions

13. Guest Storage Depends on a number of factors Storage is locally attached, or use of SAN Two Methods provided in Windows Server 2012 Hyper-V In-guest iSCSI and Virtual Fibre Channel Common best practices for Guest Storage Operating system boot drive must be mapped to virtual IDE drive SQL Server workloads/binaries use a virtual IDE drive or the operating system drive Guest servers need to move between hosts then iSCSI targets are directly exposed to the guest server

15. Resource Over-Allocation Do not over-allocate the CPU, only 1:1 Mixing Physical and Virtual Servers Mixing of physical and virtual servers in the same pool is not supported Virtual Front End server pool and physical Back End Servers is supported Physical to Virtual CPU Ratio Physical to virtual CPUs ratio should not be oversubscribed Oversubscription of CPU cores of host running Lync Server media workloads not supported and not recommended on other workloads Antivirus Only deploy antivirus software on VM host root partition (OS)

16. Host Redundancy Environment should be full redundant Ensure that similar roles are spread across multiple physical platforms Host Networking Each host must have a dedicated network adaptor Share usage not supported Correct sizing should be used to handle the workload on the host server KB968703, “Microsoft Support Policy for NIC Teaming with Hyper-V” at http://go.microsoft.com/fwlink/?LinkId=211073 http://go.microsoft.com/fwlink/?LinkId=211073 Enable VLAN tagging on the host NIC Implement (multiple) VLANs on the guests to optimize network traffic from FEs to clients and FEs to Bes

18. Guest Core Requirements Hyper-V has not limitations to the number of CPU Cores on Windows Server 2012 Other third-part hypervisors may be limited to 8 cores Lync Server 2013 running on physical hardware does not have any limit to CPU cores Guest Operating System Windows Server 2012 Windows Server 2012 R2 preferred Windows Server 2008 R2 Windows Server 2008 SP2 is not supported

19. Legacy versus Synthetic Virtual NIC Using Legacy adapter results in lower data transfer Emulates Intel 21140-based PCI Fast Ethernet Adapter (usually 1GBps or faster) Synthetic Adaptors preferred Dedicated VMBus to Virtual and Physical NIC Communication Single Root IO Virtualization (SR-IOV) Available in Windows Server 2012 Provides extensions to PCI Express devices like network adapters to separate access which creates a virtual switch Legacy network adapter is not supported

20. IPv4 and IPv6 Not recommended to mix IPv4 with IPv6 Disable Virtual DVD/CD Drives in Guest Prevents allocation resources being allotted for their function

21. Back End Database Role(BE DB) BE Database is no longer the real-time data store in Lync pool Provides overall persistent blob storage of data from Front End Servers Different in comparison to Lync Server 2010 Front End Server Role(FEs) Handles transactions for users A/V Conferencing Server Part of the Front End Server role No longer separate Monitoring nor Archiving Server role Lync Server 2013 Architectural Changes

23. Guest Processor: 12 Cores Memory: 32 GB Disks: 2-C: 4-D: Network: 1GB Guest Processor: 12 Cores Memory: 32 GB Disks: 2-C: 4-D: Network: 1GB Guest Processor: 8 Cores Memory: 16 GB Disks: 2-C: 2-D: Network: 1GB Guest Processor: 8 Cores Memory: 16 GB Disks: 2-C: 2-D: Network: 1GB Guest Processor: 4 Cores Memory: 8 GB Disks: 2-C: Network: 1GB Guest Processor: 4 Cores Memory: 8 GB Disks: 2-C: Network: 1GB

24. Guest Processor: 12 Cores Memory: 32 GB Disks: 2-C: 4-D: Network: 1GB Guest Processor: 12 Cores Memory: 32 GB Disks: 2-C: 4-D: Network: 1GB Used for Lync Roles: Front ends Back Ends Standard Edition

25. Used for Lync Roles: Edge Servers Directors Guest Processor: 8 Cores Memory: 16 GB Disks: 2-C: 2-D: Network: 1GB Guest Processor: 8 Cores Memory: 16 GB Disks: 2-C: 2-D: Network: 1GB

26. Guest Processor: 4 Cores Memory: 8 GB Disks: 2-C: Network: 1GB Guest Processor: 4 Cores Memory: 8 GB Disks: 2-C: Network: 1GB Used for Lync Roles: Stress Agents

27. Front End Edge Server On the server side Frontends scale the fastest 3,333 Users / Front End Back End Stress Agent

28. Front End Edge Server The backend will scale with Pool count. 40,000 Users / Lync Pool Stress Agent Back End

29. Front End The edge server will scale with Pool count. 40,000 Users / Lync Pool Stress Agent Back End Edge Server

30. Front End The stress agents will scale the fastest 2,500 Users / Agent Back End Edge Server Stress Agent

32. Observations Multiple tests were conducted Optimal solution found 10,000 user pool with three Front End Servers Solution produced a high resource utilization Was within critical KHI Limits Testing is required Due to different hardware and user model

34. Storage LocationInternal External DisksDisks 0-3 Disks 4-7Disks 8-11 ArrayArray 0 (RAID 10)Array 1 (RAID 10)Array 2 (RAID 10)Array 3 (RAID 10) Capacity600 GB1.2 TB IOPS (100% Read %)700 IOPS IOPS (100% Write %)350 IOPS

35. Virtual Machine Placement Guest virtual machines were spread across hosts in order to test performance Collocation of specific server roles was not tested. Instead, we used a logical separation of roles Did not place FEs together on same host Can keep virtual servers in the same pool improves resilience Logical Proc Host01Host02Host03Host04Host05Host06Host07Host08 00-03FE01FE02FE03BE01BE02Edge01Edge02ST05 04-07 08-11 DC01DC02ST06 12-15 16-19OWAS01 BE03 (Witness) OWAS02 ST07 20-23 24-27 ST01ST02ST03 ST04ST08 28-31Reserved

36. LSS Ramp Up Throughout testing process required a ramp up period of about 30mins During Ramp-Up time, the following occurred: LSS Configuration files are loaded Users are logged in Lync Server completes some background tasks

37. LSS Ramp Up

38. SQL Express Four processors remained in high utilization over time Associated with the RTCLOCAL SQL Server Express Edition instance SQL Server Express Edition can use only four logical processors http://technet.microsoft.com/en-us/library/ms143760.aspx >90% utilization indicates Enterprise with 3 FEs is already at full capacity From a SQL Server Express viewpoint and can be accommodated by addition Front End Servers Lync Server 2013 is optimized to utilize the four cores assigned for SQL Express Compute Key KHI is Queue Latency and Sproc Latency

39. SQL Express

40. Create users and groups Enable users for Lync Generate contact lists Create test location info. Changing “Average Contacts per User” will increase subscriptions per user and increase processor utilization on the Lync Frontends. Specify Stress Agents Service discovery Enable Modalities to test Set load variables such as number and frequency of PSTN calls Be mindful of the features you enabled and how you configure them. For instance the Reach client can increase processor utilization on the Frontends.

44. Once desired configuration determined Generate files Directory created for each stress agent Each directory should be copied the corresponding agent

45. Runs all the tool generated tests Runs a specific test such as instant messaging

46. Validation Toolset Perform stress testing of a targeted deployment infrastructure Can target a specific usage pattern Simulate individual workloads, such as IM and presence Use to provision users and simulate user loads Ensure proper design and deployment Performed after technical design, before piloting Deploy into lab (controlled environment) Requires clients for stress testing Stress and Performance Lync Server Stress and Performance Tool (LSS)

47. 10 Critical Key Health Indicators Provide the basis for a “Good Pass” Ease of checking all the indicators in each run If testing reveals no issues in the 10 KHIs Further analysis of the full KHI set is recommended Network Planning, Monitoring, and Troubleshooting with Lync Server documentation http://www.microsoft.com/en-us/download/details.aspx?id=39084 http://www.microsoft.com/en-us/download/details.aspx?id=39084 Key Health Indicators Good Pass

48. CounterDescriptionHealthy Range \Processor Information(*)\ % Processor TimeCPU Utilization< 80% (highest core) \Memory\Available MbytesDisplays the amount of physical memory, in bytes, available to processes running on the computer.>20% total system MB \PhysicalDisk\Avg. Disk Sec/Read A key measure of disk latency representing the average time, in milliseconds, of each read to disk where > 20 is poor, <20 is good/fair, <12 is better, <8 is best 25 ms Red \PhysicalDisk\Avg. Disk sec/Write A key measure of disk latency representing the average time, in milliseconds, of each write to disk, where non-cached writes. (>20 poor, 4 poor, <4 fair, <2 better, <1 best ). For online transaction processing (OLTP) databases, the lower this number the better, especially for disks holding the transaction log. 25 ms Red LS:Usrv - DBStore\Usrv – Queue Latency (msec) Queue latency is the amount of time (in milliseconds) that it takes for a request to leave the Front End Server’s queue toward the back-end database. If this value by itself is high, you may have be encountering a network problem between the Front End Server and the SQL Server. If this value is high and Sproc Latency is high, it is most commonly a bottleneck with the Back End Server. <100ms sustained LS:USrv – DBStore\Usrv – Sproc Latency (msec) Sproc latency is the amount of time (in milliseconds) that it takes for the SQL Server database to process the request. This performance value is collected from the time the request leaves the Front End Server queue until that the request returns. If this value by itself is high, it is likely a bottleneck with the Back End Server. <100ms sustained \SQL Server Buffer Manager\Page life expectancy Tells, on average, how many seconds SQL Server expects a data page to stay in cache. The target on an OLTP system should be at least 300 (5 min). When under 300, this may indicate poor index design (leading to increased disk I/O and less effective use of memory) or, simply, a potential shortage of memory. A low value, below 3600 seconds (together with high lazy writes/sec and checkpoint pages/sec) indicates memory pressure. < 300 \MSSQL$RTC:Memory Manager\Total Server Memory(KB) Shows the amount of memory that SQL Server is currently using. This value should grow until it is equal to Target Server Memory, as it populates its caches and loads pages into memory. When it has finished, SQL Server is said to be in a “steady-state”. Until it is in steady-state, performance may be slow and IO may be higher. < 80% of physical memory \ASP.NET Apps v2.0.50727(*)\Requests Rejected < 80%

49. 2 categories, service & resource instrumentation Add to performance collections Analyze to determine services are in a healthy state

50. Actual Counter Names LS:DATAMCU - MCU Health And Performance\DATAMCU - MCU Health State LS:AVMCU - MCU Health And Performance\AVMCU - MCU Health State LS:AsMcu - MCU Health And Performance\ASMCU - MCU Health State LS:ImMcu - MCU Health And Performance\IMMCU - MCU Health State

52. www.microsoft.com/learning http://developer.microsoft.com http://microsoft.com/technet http://channel9.msdn.com/Events/TechEd