VMware vCenter Operations Manager for View 1.0.2 Release Notes
VMware

VMware vCenter Operations Manager for View 1.0.2 Release Notes

vCenter Operations Manager for View 1.0.2 | Build 997768

Last Document Update: 19 February 2013

Check frequently for additions and updates to these release notes.

These release notes include the following topics:

Introduction to VMware vCenter Operations Manager for View

vCenter Operations Manager for View extends the functionality of VMware vCenter Operations Manager to monitor and manage VMware View environments.
vCenter Operations Manager for View collects data from managed virtual desktops and presents that data in preconfigured dashboards for both real-time and predictive analysis.

What's New

This is a maintenance release of VMware vCenter Operations Manager for View.
The main new feature with this release is that VMware vCenter Operations Manager for View 1.0.2 now supports version 5.6.0 of the vCenter Operations Manager vApp.
VMware vCenter Operations Manager 5.6.0 adds a number of performance and scalability improvements over the previous 5.0.3 release.

Product Compatibility

vCenter Operations Manager for View 1.0.2 is compatible with the following products:

  • vCenter Operations Manager Custom user interface (vApp) 5.0.3 and 5.6.0
  • View 5.0 or later
  • vCenter Operations Manager for View 1.0.2 is packaged with vCenter Operations Manager 5.6.0. The vCenter Operations Manager for View 1.0.2 View Adapter should only be used with the 5.6.0 and 5.0.3 versions of vCenter Operations Manager vApp.
The View VDI environment should already be setup and functioning. vCenter Operations is installed as part of the vCenter Operations Manager for View installation (ie first install vC Ops vApp and then install the View adapter).

Scalability

vCenter Operations for View scalability limits:

  • A View environment of 4000 virtual machines is supported using the default large vC Ops vApp configuration.
  • For more information, see the Scalability Tuning Technical Note. If you have more than 4000 virtual machines you can select a subset of the vCenter Server inventory to monitor. For more information, see KB 1036195.

Installation Notes

Carefully read the following notes before you install vCenter Operations Manager for View 1.0.2.

  • Upgrading from a Beta release

    Upgrading from a Beta release of vCenter Operations Manager for View is strongly discouraged. Upgrading can result in database inconsistencies or even corruption.

  • Upgrading from the 1.0.1 release to the 1.0.2 maintenance release.

    Perform these steps to upgrade from the 1.0.1 release of vCenter Operations Manager for View to release 1.0.2.

    1. Stop and uninstall the v1.0.1 View Adapter.
    2. Upgrade the vCenter Operations Manager Enterprise vApp to version 5.6.0.
      • Apply the upgrade PAK file VMware-vcops-5.6.0-xxxxxx.pak using the vCenter Operations Manager Administration console.
    3. Install the v1.0.2 View Adapter.
    4. Deploy the new View Adapter PAK file included in the v1.0.2 installation.
      • Apply the v1.0.2 PAK file VMware-vcops-viewadapter-xxxxxx.pak using the vCenter Operations Manager Administration console.
    5. Start the v1.0.2 View Adapter.

  • vCenter Operations Manager for View sizing

    The View adapter adds approximately 100 metrics for each active View desktop session to vCenter Operations Manager. During deployment, consider increasing the deployment size of your vApp to account for this additional load.

  • Attempting to open the ZIP file containing the encrypted View adapter installer fails

    In some environments, the built-in unzip capabilities of Windows do not properly handle encrypted ZIP files.

    Workaround: Use a third-party decompression tool such as WinZip or 7Zip.

  • Testing the connection to an Oracle View Event Database results in an error

    Testing the connection to an Oracle View Event Database can result in this error:
    Connecting to the View event database...FAILED (System.Data.OracleClient requires Oracle client software version 8.1.7 or greater.)

    Workaround: Download and install the latest ODAC release on the View Adapter server. Download the "Xcopy for Windows" update from the Oracle web page: http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html.

    Follow the installation instructions found in the ODAC zip file.

  • After restarting the View Connection Server, the View adapter cannot collect topology from View

    After restarting the View Connection Server, the View adapter cannot collect topology from View. This situation occurs because the View PowerShell extensions are no longer initialized on the Connection Server.

    The View adapter log might show the following error message:
    ERROR Exception running script The term 'get-connectionbroker' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

    Or, the following error might be shown when testing the View Server connection from the View Adapter Settings utility:
    Exception running script The term 'get-viewvc' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

  • Workaround: Take one of the following steps to correct the problem:
    • Run the EnableRemotePS.cmd script again on the View Connection Server as instructed for installation.
    • Run the View PowerCLI command shell from the VMware Start Menu folder on the View Connection Server.

  • vCenter Operations vApp might run out of disk space for its metric datastore

    A vCenter Operations vApp might run of disk space over time when monitoring large VDI environments. For information on adding more storage capacity to a vApp see KB 2016022.

vCenter Operations Manager for View Documentation

The documentation for vCenter Operations Manager for View 1.0 consists of the following document:

Known Issues

This section contains known issues for this release.

Configuration

  • Choosing collection intervals from View

    The collection interval is currently configured in the View Adapter Settings utility, with a choice of the following settings:

    • Small (under 500 VMs): 5 min
    • Medium (500-1500 VMs): 10 min
    • Large (over 1500 VMs): 15 min

    Testing indicates that these intervals are probably longer than necessary. The Small (5 min) configuration can probably be used for any environment up to 2000 VMs.

    Note: This interval is used for collecting View topology, not desktop metrics, and affects how quickly View object topology changes are reflected in vCenter Operations. Topology changes include desktop sessions logging in, logging off, disconnecting, and reconnecting.

Troubleshooting

  • Checking the status of the View adapter

    A new View Adapter application has been added to provide information about the internal status and health of the View adapter. To view this information, choose the Manager dashboard tab, select View Adapter in the Application Overview widget in the upper left of the screen, and drill down into the component tiers (View Topology, Desktop Metrics, and View Events).

    A new View Adapter Status dashboard has been added to monitor the performance and collections times on the View adapter.

  • View Client resources and View Client Network resources might not be created for a User Desktop resource

    If all or certain parts of the registry on a desktop VM cannot be accessed or are not available, View Client resources and View Client Network resources might not be created for a User Desktop resource. This situation will not be a common occurrence if desktop connection settings are configured correctly. A message will appear in the log file when this event occurs.

User Interface

  • New PCoIP metrics of the View Client Network might be displayed as metrics of the View Network
    If the View Network (the network that contains the virtual machine) and the View Client Network (the network that contains the client machine) in an environment have the same name (for example, 192.168.1.0). In this case, the adapter creates only one of these resources (either the View Network or the View Client Network), but not both.
    Workaround: Use a different network for client connections than the one used for the View virtual machine.
  • View dashboards in the Custom UI stop working properly after upgrading the vCenter Operations Manager vApp from 5.0.3 to 5.6
    If vCenter Operations Manager for View 1.0.2 is installed and running on a vCenter Operations Manager 5.0.3 vApp, and you upgrade the vApp to version 5.6, the View dashboards that appear in the Custom UI will start displaying error messages and will not work as expected.
    Workaround: After the upgrade of the vCenter Operations Manager vApp, apply the View adapter PAK file again.
    1. Navigate to the vApp Administration portal.
      The url is https://<UI-VM>/admin/, where >UI-VM< is the IP address of the UI virtual machine in the vCenter Operations Manager vApp.
    2. On the Update tab, click Browse to locate the PAK file, and click Open.
    3. Click Update and click OK to confirm the update.
      The Administration user interface uploads the PAK file. The upload might take several minutes.

  • After installation, some workload metrics for View objects might be artificially high

    After installing the View adapter, some workload metrics for View objects might be artificially high and trigger alerts. This situation is due to the way in which workload is calculated for some View objects. These values will normalize with time and become more accurate.

PowerCLI

  • The View PowerCLI snapin must be initialized each time the system is restarted.

    Add the View PowerCLI snapin to the Powershell profile on the View Connection Server.

    To add the View PowerCLI snapin to the Powershell profile :

    1. Open or create the following file: C:\Windows\System32\WindowsPowerShell\v1.0\Profile.ps1
    2. Add the line:

      add-pssnapin vm*

      to the Profile.ps1 file.
    3. Save the file.

Resolved Issues

This section contains resolved issues for this release.

  • The View Adapter Configuration Utility may show a timeout error when starting the View Adapter service

    In larger View environments (2000+ desktops) the View Adapter Configuration Utility might show a timeout error when starting the View Adapter service. The service might take over 30 seconds to start. In this case it will be started regardless of the timeout message.

    Workaround: Refreshing the service status display in the configuration utility will indicate when the service starts.

  • View topology information cannot be collected from the View server after installing on View 5.1

    There have been problems reported with collecting View topology information from the View server after installing on View 5.1.

    Workaround: The View credentials used by the View adapter do not have the correct privileges. Be sure to include the credentials used by the View adapter with the View Administrators (Read only) role in the View admin console. The View credentials must also be included in the Local Administrators group on the View Connection Server. You must be a member of the local admin group to use the remote PowerShell connection. The View Administrators (Read only) role allows access to run the View PowerCLI cmdlets.

  • The View Adapter Status dashboard

    The View Adapter Status dashboard is now included in the default dashboards created when the vCenter Operations Manager for View .pak file is deployed. The dashboard includes the Session Count Last Month widget. This widget shows a line graph with the concurrent View desktop session count over the last month to help verify license compliance.

  • The average session reconnect time no longer shows unusually high values of 17000 seconds or more

    Session logon and reconnect times would intermittently be unreasonably high. The problem causing this behavior has been corrected.

  • Several alerts, warnings, and red or yellow UI indicators shown in the View dashboards don't offer information detailing the cause

    Additional change events have been included to provide more information regarding several View specific alerts and metrics. References to KB articles have also been added where applicable.

  • When the View adapter PAK file is deployed on a vCenter server with one or more ESX 4.0 hosts, the heat map on the View Pools dashboard might be displayed incorrectly

    Remove the Datastore Latency configuration from this heat map when one or more ESX 4.0 hosts are registered with the vCenter server.

Top of Page