- Instant messaging (IM) and presence
- Audio/Video/Multi-View conferencing
- Application sharing
- Voice over IP (VoIP), including public switched telephone network (PSTN) simulation
- Web Access Client conferencing
- Conferencing Attendant
- Response Groups
- Distribution list expansion
- Address book download and address book query
- E911 calls and Location Profile
The tool does not simulate the following clients:
- Microsoft Office Live Meeting 2007
- Microsoft Office Communications Server 2007 R2, Group Chat Console
As such, it will not provide support for testing the following components:
- Web conferencing
- Group Chat Console
The following are included in the package:
- UserProvisioningTool.exe. You use UserProvisioningTool.exe to create users and contacts. For details, see “Creating Users and Contacts” later in this guide. UserProvisioningTool.exe is installed .\ LyncStress path.
- UserProfileGenerator.exe. You use UserProfileGenerator.exe to configure the input parameters for the load tool as specified in the desired user profile. For details, see “Configure User Profile” later in this guide. UserProfileGenerator.exe can be found under .\ UserProfileGenerator path.
- LyncPerfTool.exe. LyncPerfTool.exe is the client simulation tool. For details, see “Running LyncPerfTool” later in this guide.
- Default.tmx. You need Default.tmx to use the Lync Server 2013 Stress and Performance Tool.
- Example provisioning scripts. You can use these examples to configure your topology for running load based on scenarios. These are installed under the .\Doc path.
http://www.microsoft.com/en-us/download/details.aspx?id=36819
Documentation:
http://technet.microsoft.com/it-it/library/jj945609.aspx
Running the Lync Stress and Performance Tool
Th e Lync Stress and Performance Tool is not supported when run in a production Active Directory
environment.
Because of the tool’s requirements, and the tool’s high-risk security requirements needed to access
the accounts in Active Directory, it should be run only in test environments.
As a general best practice, any sort of performance testing should be carried out in a separate
environment on hardware identical to that which will be used in production.
