Prerequisites
Topic Last Modified: 2013-02-19
There are various hardware, software, and system configuration requirements that you’ll need to run the Lync Server 2013 Stress and Performance Tool.
Client Hardware Requirements
To run the Lync Server 2013 Stress and Performance Tool on your Lync Server 2013 deployment, for every 4,500 users whose load you want to simulate, you’ll need at least one dedicated computer that meets the following minimum hardware requirements:
1 gigabit network adapter
8-GB ram
2 dual-core central processing units (CPUs)
Client Software Requirements
To run the Lync Server 2013 Stress and Performance Tool on your Lync Server 2013 deployment, the supported operating systems are:
Windows Server 2012 operating system
Windows Server 2008 operating system (64-bit edition)
Your client computer must meet the following software requirements:
You must have the Microsoft .NET Framework 4.5 runtime installed.
On Windows Server 2008/Windows Server 2012, the Desktop Experience feature must be enabled.
You must have the Microsoft Visual C++ 2012 redistributable package (x64) installed.
A fully configured Lync Server 2013 deployment.
Important
Microsoft Unified Communications Managed API (UCMA) 4.0 libraries are included in the installation package, so UCMA is not required and should not be installed on client computers.
Configuration Requirements
The computers that will run the Lync Server 2013 Stress and Performance Tool must be configured according to the following requirements:
You must be logged on as a member of the Domain or Local Admins group.
Lync Server 2013 Stress and Performance Tool (LyncPerfTool.exe) cannot be run on a computer that is also running Lync Server 2013 components.
You must run the Lync Server 2013 User Creation tool (UserProvisioningTool.exe) on the Front End Server or on the Standard Edition server where the user accounts will reside. When the tool is run multiple times, each user who is enabled for Microsoft Unified Communications must have a unique phone number.
The page file size should be system-managed, or should be at least 1.5 times the amount of RAM on the system.