AppManager for Microsoft Hyper-V 8.0.313.0 Release Notes

Date Published: April

AppManager for Microsoft Hyper-V lets you monitor the operation, performance, and availability of your servers running Hyper-V. This module provides a set of Knowledge Scripts designed to give you a comprehensive view of how computers running Microsoft Hyper-V perform in your environment.

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 that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.

The documentation for this product is available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the NetIQ Documentation page. To download this product, see the AppManager Module Upgrades & Trials Web site.

1.0 What’s New?

This release of AppManager for Microsoft Hyper-V provides Knowledge Scripts for monitoring the Hyper-V servers.

This release includes the following Knowledge Scripts:

  • Discovery_Hyper-V. Discovers CPU, memory, networks, and file systems installed on all Hyper-V hosts listed in a discovery input file. Also discovers all guest virtual machines created on the host, online or offline, and the amount of CPU, memory, networks, and file systems assigned to and used by each virtual machine.

  • Hyper-V_EventLog. Scans Hyper-V event logs for entries matching the criteria you specify and raises an event if such entries are found.

  • Hyper-V_HostCPUUtilization. Monitors Hyper-V host computers for the overall system CPU usage, CPU usage by the virtual machines, CPU usage by the Microsoft Hypervisor, and overall CPU usage by the root partition. Also monitors the CPU idle run time and the number of active virtual processors per logical processor.

  • Hyper-V_HostLogicalDiskSpace. Monitors the free space and the percentage of disk space used on logical disk drives on the Hyper-V host computer.

  • Hyper-V_HostLogicalDiskStats. Monitors the average queue length, disk latency, and disk byte transfer rate of the logical disks on the Hyper-V host computer.

  • Hyper-V_HostMemory. Monitors Hyper-V hosts for the overall system physical memory usage, the total memory available, and the average dynamic memory pressure exerted by the virtual machines on the host for acquiring the memory.

  • Hyper-V_HostNetworkUtilization. Monitors Hyper-V host computers for the network utilization of network interface controller (NIC) cards present on the host computer. Also monitors the network queue length of each NIC, and the number of errors in outbound and inbound packets.

  • Hyper-V_HostOverallHealth. Monitors the running status of Hyper-V core services, which include Hyper-V Image Management, Hyper-V Networking Management, and Hyper-V Virtual Machine Management. Also monitors the number of virtual machines that have critical health.

  • Hyper-V_HostPhysicalDiskStats. Monitors the average queue length, disk latency, and disk byte transfer rate of the physical disks on the Hyper-V host computer.

  • Hyper-V_HostReservation. Monitors the CPU reservation and memory reservation for virtual machines or guest machines on the Hyper-V host computer. Also monitors the count of allocated virtual processors on virtual machines per logical processor.

  • Hyper-V_HostVirtualSwitchTransferRate. Monitors Hyper-V host computers for virtual switch transfer rates in MB per second and packets per second.

  • Hyper-V_HyperVAvailability. Monitors the availability of the hypervisor on host computers.

  • Hyper-V_Inventory. Runs an inventory of virtual machines and the details for virtual machines on the Hyper-V host computer, and raises an event if VMs are added or removed.

  • Hyper-V_SetMonitoringInterval. Sets the monitoring interval for Knowledge Scripts that use the global cache. Run this script before running any of the scripts that use the global cache.

  • Hyper-V_VmAvailability. Monitors the availability, health, and uptime of a virtual machine on a Hyper-V host.

  • Hyper-V_VmCPUUtilization. Monitors the CPU usage of a virtual machine on the Hyper-V host computer.

  • Hyper-V_VmDiskSpace. Monitors the free space and the percentage of disk space used on the storage disk of the virtual machines on the Hyper-V host computer.

  • Hyper-V_VmDiskStats. Monitors the number of disk errors and disk reads and writes in bytes per second on the storage disks on virtual machines on the Hyper-V host computer.

  • Hyper-V_VmIntegrationServices. Monitors the version status and the availability of Virtual Machine Integration Services components on virtual machines on the Hyper-V host computer.

  • Hyper-V_VmMemory. Monitors the average memory pressure on virtual machines on the Hyper-V host computer.

  • Hyper-V_VmNetworkAdapterTransferRate. Monitors virtual network adapter transfer rates in MB per second and packets per second on virtual machines on the Hyper-V host computer.

2.0 System Requirements

For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.

AppManager for Microsoft Hyper-V has the following system requirements:

Software/Hardware

Version

NetIQ AppManager installed on the AppManager repository (QDB) computers, on the computers running Hyper-V that you want to monitor (AppManager agents), and on all console computers

8.2 or later

The following hotfixes are required for AppManager 8.2:

  • QDB Hotfix 8.2.0.4 or later for AppManager Repository 8.2

  • MS hotfix 8.2.0.3 or later for AppManager Management Server 8.2

  • MC hotfix 8.2.0.2 or later for AppManager Windows Agent 8.2

For more information, see the AppManager Suite Hotfixes page.

Agent computer requirements

  • Disk Space: 100 GB free

  • Memory: 16 GB recommended

  • Processors: 8 (2.8 GHz and above dual core or multiprocessor)

Management server requirements

  • Disk Space: 100 GB free

  • Memory: 8 GB recommended

  • Processors: 8 (2.8 GHz and above dual core or multiprocessor)

AppManager repository computer requirements

  • Disk Space: 100 GB free

  • Memory: 16 GB recommended

  • Processors: 8 (2.8 GHz and above dual core or multiprocessor)

Microsoft Windows operating system on the proxy agent computers

One of the following:

  • Windows Server 2012 R2

    Note This module does not support Server Core for Windows Server 2012 R2 or Windows Server 2008 R2.

  • Windows Server 2008 R2

  • Windows Server 2008 (64-bit)

Microsoft Hyper-V host

One of the following versions:

  • Hyper-V Server 2012 R2

  • Hyper-V Server 2012

  • Hyper-V Server 2008 R2

  • Hyper-V Server 2008

Microsoft .NET Framework on the agent computers

4.5.1 or later

Windows Management Framework (WMF)

3.0 for agents running Windows Server 2008 R2 and 2008 (64-bit)

3.0 Contents of the Download Package

AppManager for Microsoft Hyper-V includes a managed object and Knowledge Scripts to discover and monitor Hyper-V resources. The download package includes these release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:

  • AM70-Hyper-V-8.0.313.0.msi, the module installer.

  • AM70-Hyper-V-8.0.313.0.ini, a configuration file used with the AppManager setup program.

  • AM70-Hyper-V-8.0.313.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.

  • AM70-Hyper-V-8.0.313.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.

  • ckHyper-V.exe, the pre-installation check used with the AppManager setup program.

  • DefaultRule_Hyper-V.xml, a configuration file used for deploying the module with Control Center.

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 folder 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.

4.0 Installing This Module

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

  • On the Hyper-V host or on a Windows computer that serves as a proxy agent computer to install the agent components

  • 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. You can install these components into local or remote QDBs. To ensure module functionality, run the module installer for each QDB attached to Control Center.

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. Microsoft .NET Framework 3.5 is required on the computer where you run the installation program for the QDB portion of the module. For computers running more recent versions of Windows operating systems that use a newer version of .NET, install .NET 3.5 with the Add Roles and Features wizard in Windows Server Manager, as described in this Microsoft article.

Install Knowledge Scripts only once per QDB. 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 Hyper-V Management Guide, included in the download package.

5.0 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.

  • Hyper-V Knowledge Scripts fail if a value in a field on the Details tab exceeds 128 characters. Hyper-V scripts fail if the number of characters in a field on the Details tab on the Navigation pane or TreeView exceeds 128 characters, which is the current limit. (ENG337276, DOC337557)

  • Hyper-V_Inventory Knowledge Script generates “Metrics data not available” events for downed or inaccessible hosts that are not running Windows Server 2012 R2. Because of differences in the Windows Event Log in Windows Server 2012 R2 compared to previous versions of Windows Server, the Hyper-V_Inventory job generates multiple “Metrics data not available” events if hosts fail that are not running Windows Server 2012 R2. (ENG337298, DOC337559)

  • Hyper-V virtual machine Knowledge Scripts do not immediately display the Object name in event messages for new, changed, or deleted virtual machines. The Hyper-V_VmAvailability, Hyper-V_VmCPUUtilization, Hyper-V_VmDiskSpace, and Hyper-V_VmDiskStats scripts do not list a specific value in the Object name field for event messages generated by those scripts after virtual machines were added, changed, or removed. The Object name is initially set to Unknown, and the events do not display in the Hyper-V view. This issue resolves after the Hyper-V virtual machine Knowledge Scripts complete their first two or three iterations. (ENG337386, DOC337556)

  • Monitoring two guest machines with the same name on a Hyper-V host leads to duplicate data. If you monitor two or more guest machines on a Hyper-v host machine that share the same name, the module collects duplicate data for those machines. To work around this issue, change the name of one or more guest machines to ensure that each machine has a unique name. (ENG336885, DOC337558)

  • Windows Remote Management (WinRM) shell takes unexpectedly long to close after a job stops. Because of an issue with the way in which Microsoft handles cache jobs, the WinRM shell created by a Hyper-V Knowledge Script job might take up to thirty minutes to close instead of closing immediately after the job stops. (ENG337543, DOC337604)

6.0 Third-Party Software

The AppManager for Microsoft Hyper-V product and all updates and modifications thereto (“Software”) is distributed with certain third-party software and open source software (as may be defined in the license agreement provided with the Software).

The following third-party and open source software are included with the Software and are licensed for distribution according to the terms described in this document and any use thereof must be in accordance with such terms, solely in conjunction with your internal use of the Software, and - unless explicitly contradicted below - consistent with the terms and conditions set forth in the applicable license agreement for the software. No further licenses are granted.

Apache License: Distributions of log4net, log4cxx

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

  1. Definitions.

    "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

    "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

    "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

    "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

    "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

    "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

    "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

    "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

    "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

    "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

  2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

  3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

  4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

    1. You must give any other recipients of the Work or Derivative Works a copy of this License; and

    2. You must cause any modified files to carry prominent notices stating that You changed the files; and

    3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

    4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

    You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

  5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

  6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

  7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

  8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

  9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

7.0 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 general corporate and product information, see the NetIQ Corporate Web site.

For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.