AppManager for Microsoft Office Communications Server (OCS) provides performance and availability management for the various servers that provide instant messaging, presence, conferencing, and other unified communications used by your corporation.

This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure our products meet all your needs. You can post feedback in the AppManager forum on Qmunity, our community Web site that also includes product notifications, blogs, and product user groups.

This document outlines why you should install this module, lists installation requirements, and identifies known issues. For more information about installing the module, see the AppManager for Microsoft OCS Management Guide, included in the download package.

Why Install This Release?

Release 7.1.59.0 of AppManager for Microsoft OCS resolves the following issue:

• Discovery_OCS fails with a "no monitored OCS components found" event when run on specific devices. Before installing this release of the module, the Discovery_OCS Knowledge Script may fail with an event stating that no monitored OCS components were found on computers on which both 32-bit and 64-bit components of OCS were installed. With this release, the logic to deal with various combinations of 32-bit and 64-bit registry keys has been improved, and the error no longer occurs. (ENG298968)
• Updated text about minimum permissions in the management guide. This release includes an update to the list of permission requirements for an OCS user account. The OCS user account should be a member of the RTCUniversalReadOnlyAdmins group as a minimum permission, instead of the RTCUniversalServerAdmins group as previously listed in the documentation. (DOC301567)

This release of AppManager for Microsoft OCS replaces all Previous Releases.

Return to Top

System Requirements

For the most recently updated list of supported application versions, see the AppManager Supported Products Web site.

AppManager for Microsoft OCS has the following system requirements:

• At minimum, AppManager version 7.0 installed on the AppManager repository (QDB) computer, on the OCS computers you want to monitor (agents), and on all console computers.
  Note Support for Windows Server 2008 requires the most recent version of the AppManager for Windows module. For more information, see the AppManager Module Upgrades and Trials Web page.
• One of the following Microsoft Windows operating systems installed on the agent computers:
  • 64-bit Windows Server 2003 SP2
  • 64-bit Windows Server 2003 R2 SP2
  • 64-bit Windows Server 2008 SP2
  • Windows Server 2008 R2
  Note This release does not support the installation of Microsoft OCS on 32-bit Windows Server 2003 or 32-bit Windows Server 2008.
• AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the OCS computers you want to monitor (agents), and on all console computers
  Note Support for Windows Server 2008 R2 requires the AppManager for Windows module, version 7.6.170.0 at minimum. For more information, see the AppManager Module Upgrades & Trials Web page.
• Microsoft Office Communications Server 2007 R2 only
  Note Customers with OCS 2007 R1 should use version 7.0 of this module.

The following table lists the versions of Microsoft Windows and Microsoft OCS supported by the AppManager for Microsoft OCS module, versions 7.0 and 7.1:

Operating System	OCS 2007 R1	OCS 2007 R2
32-bit Windows Server 2003	Version 7.0	Not supported
64-bit Windows Server 2003 SP2	Not supported	Version 7.1
64-bit Windows Server 2003 R2 SP2	Not supported	Version 7.1
64-bit Windows Server 2008 SP2	Not supported	Version 7.1
Windows Server 2008 R2	Not supported	Version 7.1

Note AppManager for Microsoft OCS version 7.1 or later does not support an upgrade from version 7.0 of AppManager for Microsoft OCS.

For more information about the system requirements, see the AppManager for Microsoft OCS Management Guide, included in the download package.

Return to Top

Contents of the Download Package

AppManager for Microsoft OCS includes a managed object, qccma4.dll, and Knowledge Scripts to discover and monitor CallManager resources. The download package includes this ReadMe, a management guide, Help for Knowledge Scripts, and several files that are used during installation:

• AM70-OCS-7.1.59.0.msi, the application module setup program.
• AM70-OCS-7.1.59.0.ini, a configuration file used with the AppManager setup program.
• AM70-OCS-7.1.59.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
• ckOCS.exe, the pre-installation check used with the AppManager setup program.

When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files directory on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.

Return to Top

Installing This Module

Run the module installer to install the module components in the following locations:

• On the OCS computers you want to monitor (agents)
• On all console computers to install the Help and console extensions

Run the module installer only once on each of these computers.

You must also install the Knowledge Scripts and, where relevant, the Analysis Center reports. You can install these module components to either local or remote databases:

• When installing to each QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
• If Analysis Center reports are available for this module, select the option to install Analysis Center reports, and then specify the SQL Server name of the server hosting the Analysis Center Configuration Database.

Important This release provides SQL stored procedures. To ensure module functionality, run the module installer for each QDB attached to Control Center.

You need to install Knowledge Scripts and Analysis Center reports only once per database. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.

For more information about installing this module, see the AppManager for Microsoft OCS Management Guide, included in the download package.

Return to Top

Uninstalling This Module

You can use the Add or Remove Programs or Programs and Features option from the Control Panel to uninstall this module.

Return to Top

Known Issues

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.

• The CWAIMSessionActivity Knowledge Script reports incorrect values for the number of active IM sessions. Total IM Sessions, a counter used by Microsoft OCS, incorrectly reports the number of active IM conversations on the Communicator Web Access (CWA) server. As a result, the value for the number of active IM sessions remains 0 regardless of the number of active IM sessions actually underway. This behavior occurs only with CWA Server R1. (ENG284457)
• The EdgeServerCallActivity Knowledge Script reports incorrect values for the number of active server connections. ActiveServerConnection, a counter used by Microsoft OCS, incorrectly reports the number of active server connections on the Edge server. (ENG284455)

Return to Top

Previous Releases

This release of AppManager for Microsoft OCS includes enhancements added in previous releases.

Release 7.1.44.0, September 2010

This release provided the following enhancements:

• Support for 64-bit Windows Server 2003, 64-bit Windows Server 2008, and Windows Server 2008 R2. This release does not support Microsoft OCS on 32-bit Windows Server 2003 or 32-bit Windows Server 2008.
• Support for Microsoft OCS 2007 R2 only. Customers with Microsoft OCS 2007 R1 can use version 7.0 of the module.
• The IIS Knowledge Scripts are now located in the AppManager for Microsoft IIS module. The following scripts were moved from AppManager for Microsoft OCS to AppManager for Microsoft IIS: IIS_CpuHigh, IIS_HealthCheck, IIS_KillTopCPUProcs, IIS_MemoryHigh, IIS_RestartServer, and IIS_ServiceUpTime.

Hotfix 71294, October 2008

Hotfix 71294 resolves the following issue:

• OCS discovery fails when the Front-end server is installed behind a hardware load balancer with the pool's fully qualified domain name assigned to it. The Discovery_OCS Knowledge Script in the previous release failed to run when a Front-end server installed in an environment with the pool's fully qualified domain name assigned to a hardware load balancer. After you install this release, you can successfully run discovery on the Front-end server installed in a similar environment. (ENG252742)

For more information about the issues resolved with this release, see NetIQ Knowledge Base article NETIQKB71294.

Release 7.0, July 2008

This initial release of AppManager for Microsoft OCS provided the following features and benefits:

• Monitoring the health of all services running on OCS servers
• Tracking server uptime since last reboot
• Tracking the number, duration, and users involved in all sessions occurring on OCS servers
• Tracking VoIP call activity
• Tracking the load placed on servers due to ongoing conferences and sessions
• Monitoring the availability of OCS servers
• Monitoring the total CPU usage of a server using OCS
• Tracking any failed conferences or session
• Tracking instant messaging, presence, and conferencing data on the Communicator Web Access server

This release of AppManager for Microsoft OCS provides support for AppManager licensing. AppManager for Microsoft OCS consumes one license for each resource that has OCS installed on it.

Return to Top

Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information Web site.

For interactive conversations with your peers and NetIQ experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and user groups.

Return to Top

Legal Notice

NetIQ AppManager is covered by United States Patent No(s): 05829001, 05986653, 05999178, 06078324, 06397359, 06408335.

THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.

This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.

This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.

© 2011 NetIQ Corporation. All rights reserved.

U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.

Check Point, FireWall-1, VPN-1, Provider-1, and SiteManager-1 are trademarks or registered trademarks of Check Point Software Technologies Ltd.

ActiveAudit, ActiveView, Aegis, AppManager, Change Administrator, Change Guardian, Compliance Suite, the cube logo design, Directory and Resource Administrator, Directory Security Administrator, Domain Migration Administrator, Exchange Administrator, File Security Administrator, Group Policy Administrator, Group Policy Guardian, Group Policy Suite, IntelliPolicy, Knowledge Scripts, NetConnect, NetIQ, the NetIQ logo, PSAudit, PSDetect, PSPasswordManager, PSSecure, Secure Configuration Manager, Security Administration Suite, Security Manager, Server Consolidator, VigilEnt, and Vivinet are trademarks or registered trademarks of NetIQ Corporation or its subsidiaries in the USA. All other company and product names mentioned are used only for identification purposes and may be trademarks or registered trademarks of their respective companies.

For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.

Return to Top