Search This Blog

Sunday, March 11, 2012

Lync Server 2010, Stress and Performance Tool

The Lync Server 2010 Stress and Performance Tools (LSS) can be used to prepare, define and validate performance targets of user scenarios offered by on-premise Lync Server 2010 deployment. LSS includes multiple modules and can simulate simultaneous users on one or more Lync Servers


The Lync Server 2010 Stress and Performance Tool (LSS) is capable of simulating user load of the following types:
  • Instant messaging (IM) and presence
  • Audio 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

LSS supports cross-pool load generation and federation through advanced configuration.
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
  • Video load for peer-to-peer calls or conferencing
The following are included in the package:
  • StressConfig.exe. You use StressConfig.exe to create users and contacts. For details, see “Creating Users and Contacts” later in this guide. StressConfig.exe is installed .\StressConfig 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 “Configuring the User Profile” later in this guide. UserProfileGenerator.exe can be found under .\Ocsstress path.
  • OCSStress.exe. OCSStress.exe is the client simulation tool. For details, see “Running OCSStress.exe” later in this guide.
  • Default.tmx. You need Default.tmx to use the Office Communications Server 2007 R2 Logging Tool.
  • MaxUserPort.reg. You use the MaxUserPort.reg registry script to set the MaxUserPort registry key so that the client can open more that 5000 Transmission Control Protocol (TCP) connections.
  • Example provisioning scripts. You can use these examples to configure your topology for running load based on scenarios.

To download the tool & review system requirements [ Hardware & Software ] click here.

No comments:

Post a Comment