OCS 2007 R2 capacity planning tool released

July 30th, 2009 | Tags:

The Office Communications Server 2007 R2 Capacity Planning Toolkit provides a set of tools and documentation to simplify capacity planning for Office Communications Server 2007 R2. The Capacity Planning Toolkit can be used as a complement to the Microsoft Office Communications Server 2007 R2 Planning Guide.

This release of the Office Communications Server 2007 R2 Capacity Planning Toolkit contains tools and documentation to simplify your hardware planning, provide you with increased knowledge and best practices for performance tuning, and improve your ability to verify the performance of your intended Office Communications Server 2007 R2 deployments.

The Capacity Planning Toolkit is intended for use by IT professionals in a test environment prior to production deployment. These tools should never be used against a live production environment.

The tools in this Toolkit are designed to be used with Office Communications Server 2007 R2 only. If you are searching for tools that work with Live Communications Server 2005, please download the Live Communications Server 2005 Capacity Planning Toolkit from http://www.microsoft.com/downloads/details.aspx?familyid=107a5e83-ca59-4bcb-a3bc-27efd97a477d&displaylang=en

Issues addressed in this release of the Capacity Planning Tool:

    Issue Fixed: UserProfileGenerator load problem for AV and Appsharing scenario
    Explanation: As mentioned in the release notes for the previous OCS 2007 R2 Capacity planning tools release, UserProfileGenerator was generating incorrect load for AV and Appsharing scenarios. This QFE fixes this issue and UserProfileGenerator should generate correct load for various load settings: low, medium & high.

    Issue Fixed: Ocsstress needs a _Total instance
    Explanation: A “_Total” performance counter instance was added to Ocsstress. This new instance makes it easier to monitor Ocsstress performance counters.

    Issue Fixed: Ocsstress should not update the CallsFailed counter for 486 , 603 etc decline specific responses
    Explanation: Ocsstress was wrongfully reporting calls which received valid responses such as 486 busy, 603 decline as calls failed. These calls are no longer marked as failed and are considered a successful call-routing scenario.

      Source: here