VMware vRealize Operations for Horizon 6.7.0

Last Modified: Nov 7, 2020 @ 6:34 am

Navigation

💡 = Recently Updated

Change Log

Planning

vRealize Operations for Horizon is composed of several components:

  • vRealize Operations Manager appliance – this is the same vROps appliance deployed for monitoring of vSphere infrastructures, and hence it can monitor the vSphere clusters that are hosting the Horizon Agents.
  • Horizon Adapter for vRealize Operations – this is a .pak file installed on a vROps appliance. The Horizon Adapter receives data from one or more Broker Agents.
    • Broker Agent is installed on top of a Horizon Collection Server in each Horizon pod. The Broker Agent collects information from Horizon Connection Servers (e.g. events database), and feeds the data to the Horizon Adapter running on a vRealize Operations Manager appliance. The Broker Agent can also collect data from Unified Access Gateway, and App Volumes.
  • vROps Dashboards, Reports, and Alerts for Horizon – these display the information collected by the Horizon Adapter. Installation of the Horizon Adapter .pak file automatically imports the Dashboards, Reports, and Alerts.

The Horizon Adapter and Broker Agent should be the same version.

The vROps Horizon monitoring solution components have different versions:

vRealize Operations Manager 6.6 and newer has a new HTML5 user interface that looks quite different from vRealize Operations Manager 6.5 and older, thus necessitating a new post. See the post vRealize Operations for Horizon 6.4 for the older vROps user interface, and older Horizon Adapters.

vRealize Operations for Horizon comes with two licenses:

  • vRealize Operations Manager Enterprise license – enables vSphere monitoring for Horizon workloads. The license does not entitle vSphere monitoring of non-Horizon workloads.
  • vRealize Operations for Horizon Adapter license – enables the Horizon Adapter to collect data from the Horizon Broker Agent for a specific number of Horizon Agent machines. The Horizon 7 Enterprise License can also be used to license the Adapter.

VMware Blog Post Introducing the vRealize Operations Sizing Tool and https://vropssizer.vmware.com/sizing-wizard/choose-installation.

VMware 2093783 vRealize Operations Manager Sizing Guidelines:

Links to descriptions of new features in vRealize Operations Manager 6.6 and newerfupgra:

If you have Log Insight, there’s also a Content Pack for Horizon View. See VMware Blog Post Horizon View Content pack for vRealize Log Insight

Deploy New vROps Appliance

If you are upgrading an existing vROps appliance, skip ahead to the Patch/Upgrade Appliance section.

For new installations of vROps, download the following:

  1. See VMware’s Product Interoperability Matrix to determine which combinations of vROPs and Horizon Adapter are compatible with your version of Horizon. Also see the 6.7.1 Adapter Release Notes.
    • 6.7.1 Adapter supports VMware Horizon 7.7 or later
    • 6.7.1 Adapter requires vRealize Operations Manager 8.0 or later
    • 6.7.1 Adapter supports VMware App Volumes 2.14.8 to 2.18
    • 6.7.1 Adapter supports VMware Unified Access Gateway 3.6 and later
  2. If vRealize Operations Manager for Horizon 6.7.1, then download vRealize Operations Manager 8.0 from the vRealize Operations Manager for Horizon 6.7.0 download page.
  3. If vRealize Operations Manager for Horizon 6.6.0, download vRealize Operations Manager 7.5 – Appliance installation.
  4. If vROps 7.0, go to the VMware vRealize Operations Manager 7.0.0 download page and download the security patch. It’s the top entry named vRealize Operations Manager – Virtual Appliance Security Patch and dated 2018-12-18.

To deploy a new vROps appliance:

  1. In vSphere Web Client, navigate to a Cluster, right-click it, and click Deploy OVF Template.
  2. In the Select an OVF template page, select Local file, browse to the vRealize Operations Manager .ova file, and click Next.



  3. In the Select a name and folder page, give the VM a name, and click Next.
  4. In the Select a compute resource page, select a cluster, and click Next.
  5. In the Review details page, click Next.


  6. In the License Agreements page, check the box next to I accept all license agreements, and then click Next.
  7. In the Configuration page, select a size, and then click Next.
  8. In the Select Storage page, select Thin Provision, select a datastore, and then click Next.
  9. In the Select networks page, select a port group, and click Next.
  10. In the Customize template page:
    1. Select a time zone.
    2. Enter the IP address information for the appliance.

  11. Then click Next.
  12. In the Ready to Complete page, click Finish.


Create vROps Cluster

If you are upgrading an existing vROps appliance, skip ahead to the Patch/Upgrade Appliance section.

  1. Power on the new vROps virtual appliance.
  2. Wait for the appliance to start.

  3. Use a browser to go to https://IPAddress/admin. If you see a Service unavailable message, wait a couple minutes and try again.
  4. On the bottom of the page, click New Installation.
  5. In the Getting Started page, click Next.

  6. In the Set Administrator Password page, enter a password based on the listed requirements. Click Next.

  7. In the Choose Certificate page, you can upload a PEM certificate.

    1. The Certificate file must have .pem extension. It will not accept any other extension.
    2. Make sure the certificate file has both the certificate and keyfile combined into a single file.
    3. If there are intermediate Certificate Authorities, add them to the PEM file. CA certificates go below the server certificate.
  8. Click Next when done.
  9. In the Deployment Settings page:
    1. Enter a name for the master node.
    2. Enter a NTP Server Address, and click Add.
  10. Then click Next.

  11. In vRealize Operations Manager 8.0 and newer, you can optionally select an Availability Mode. Click Next.
  12. In the Add Nodes page, you can optionally add Remote Collector nodes. Click Next when done.

  13. In the Ready to Complete page, click Finish.

Start Cluster

  1. From the https://IPAddress/admin page, click the button labelled Start vRealize Operations Manager.

  2. Click Yes. This will take several minutes.

  3. Log into the appliance using the admin account.
  4. On the Welcome page, click Next.
  5. In the Accept EULA page, check the box next to I accept the terms, and click Next.
  6. In the Enter Product License Key page, enter the vRealize Operations Manager for Horizon license key, click Validate License Key, and click Next. Note: there is a separate license for the Horizon Adapter that will be entered later.
  7. In the Customer Experience Improvement Program page, make a choice, and click Next.
  8. In the Ready to Complete page, click Finish.

Patch/Upgrade vROps Appliance

Download Patch

To patch a vROps appliance, download the latest patch from the vROps download page.

The vROps security patch for vROps Manager 6.7 or vROps Manager 7.0 is required for Horizon Adapter 6.6.0. There is no security patch for vROps 7.5.

  1. Go to the VMware vRealize Operations Manager 7.0.0 download page or VMware vRealize Operations Manager 6.7.0 download page.
  2. Download the security patch. It’s the top entry named vRealize Operations Manager – Virtual Appliance Security Patch and dated 2018-12-18. You’ll install this after vROps is upgraded.

Download Version Upgrade

If you are upgrading vROps from an older version, download the following:

  1. Go to the VMware vRealize Operations 8.0 download page, VMware vRealize Operations Manager 7.5 download page, VMware vRealize Operations Manager 7.0.0 download page, or VMware vRealize Operations Manager 6.7.0 download page.
  2. Download the Upgrade Assessment Tool.


  3. For vRealize Operations Manager 7.5 and older, download the Virtual Application Operating System upgrade. You’ll install this patch first. vRealize Operations Manager 8.0 no longer has a separate download for Operating System upgrade.

  4. Download the Virtual Appliance upgrade. You’ll install this after you upgrade the operating system.


  5. For vROps 7.0, download the security patch. It’s the top entry named vRealize Operations Manager – Virtual Appliance Security Patch and dated 2018-12-18. You’ll install this patch after vROps is upgraded.

Install Patch or Upgrade vROps

Do the following to upgrade the vROps appliance or install a patch. You might have to perform this procedure several times to complete the upgrade. Also see Brandon Lee Upgrade to VMware vRealize Operations Manager 7.5.

  1. Use a browser to go to https://vROpsIP/admin, and login as admin.
  2. On the left, switch to the Software Update page.
  3. On the right, click Install a Software Update.
  4. Click Browse and browse to an upgrade or Security Patch .pak file downloaded from vmware.com.
  5. If you are upgrading from an older version of vROps, then you must upgrade install several .pak files in a specific order:
    1. Start with the Upgrade Assessment Tool, which is the file named APUAT.


    2. For vRealize Operations Manager 7.5 and older, upgrade the operating system, which is the file with VA-OS in the name. This step is not needed in vRealize Operations Manager 8.0 and newer.

    3. Then upgrade the vROps virtual appliance by installing the .pak file with VA in the name but without OS in the name.


    4. Finally, for vROps 7.0, install the security patch.
  6. If you are not upgrading the vROps version, and if vROps Manager 6.7 or 7.0, then simply install the Security Patch.

  7. Click Upload. Uploading and staging will take a bit of time.
    • Upgrading to 8.0 – separate OS upgrade is no longer needed:

    • Upgrading to 7.5:

    • Upgrading to 7.0:
  8. Click Next.
    • Upgrading to 8.0 – separate OS upgrade is no longer needed:

    • Upgrading to 7.5:


    • Upgrading to 7.0:
  9. In the End User License Agreement page, check the box next to I accept the terms, and click Next.
  10. In the Update Information page, click Next.
    • Upgrading to 8.0:

    • Upgrading to 7.5:


  11. In the Install Software Update page, click Install.
  12. The installation will take a while.
  13. If you installed the Upgrade Assessment Tool:
    1. On the left, click Support.
    2. On the right, switch to the tab named Support Bundles.
    3. Click the Download button for the bundle.
    4. Extract the downloaded .zip file.
    5. Go to apuat-data\report and double-click index.html.
    6. For more info, see VMware 57283 Using the Upgrade Assessment Tool for vRealize Operations Manager 7.5.
  14. Some upgrades or patches require a reboot.
  15. After rebooting and logging in again, the Software Update page shows that the update has been completed.


  16. vROps 7.0 and newer might warn you to set Password Recovery Settings on the Administrator Settings page.
  17. Click Install a Software Update again to install more .pak files as described earlier in this section.
  18. After upgrading vROps, install the security patch.

Configure vSphere Adapter

vRealize Operations Manager 8.0 and newer

  1. Login to the appliance at https://vROps_IP/ui. This is the ui path instead of the admin path.
  2. After logging in, at the top, click Administration.
  3. On the left, expand Solutions and click Cloud Accounts.
  4. On the right, click Add Account.
  5. In the Account Types page, click vCenter.
  6. Give the Cloud Account a name.
  7. In the Connect Information section, enter the address of the vCenter Server.
  8. Next to the Credential field, click the plus icon.
  9. Enter vCenter credentials and click OK.
  10. Click Test Connection.
  11. Click Accept to accept the certificate.
  12. Click OK when prompted that Test connection successful.
  13. Next to the Action Credentials field, click the plus icon.
  14. Enter vCenter credentials, and then click OK.
  15. You can optionally click Define Monitoring Goals.
  16. At the top of the page is a tab named vSAN where you can provide alternate vSAN credentials.
  17. The tab named Service Discovery requires the latest version of VMware Tools (e.g. 11.0.1).
  18. Click Add when done.

vRealize Operations Manager 7.5 and older

  1. Login to the appliance at https://vROps_IP/ui. This is the ui path instead of the admin path.
  2. Go to Administration > Solutions.
  3. Highlight the VMware vSphere Solution.
  4. On the bottom half of the window, highlight the vCenter Adapter, and then click the Configure icon on the toolbar.
  5. In the Display Name field, enter a name for the vCenter adapter.
  6. In the vCenter Server field, enter the address of the vCenter server.
  7. Click the green plus icon to add a Credential.
  8. In the Manage Credential window:
    1. Give the credential a name.
    2. Enter credentials for the vCenter server.
    3. Click OK.
  9. Back in the Manage Solution window, click the Test Connection link.

    1. In the Review and Accept Certificate window, click Accept to accept the certificate.
    2. In the Info window, click OK to acknowledge that the test was successful.
  10. Back in the Manage Solution window, on the bottom right, click Save Settings.

    1. In the Info window, click OK to acknowledge that the adapter instance was successfully saved.
  11. Click Close to close the Manage Solution window.
  12. Note: it takes four weeks for vRealize Operations Manager to determine dynamic thresholds.

Active Directory Authentication

  1. In the vRealize Operations Manager console, in the top of the page, click Administration.
  2. On the left, expand Access, and click Authentication Sources.
  3. On the right, click the green plus icon.
  4. In the Source Display Name field, enter a display name. This name will appear on the logon page as shown below.
  5. From the Source Type drop-down, select Active Directory.
  6. In the Domain/Subdomain field, enter the DNS name of your Active Directory domain.
  7. Enter credentials of a LDAP bind service account.
  8. Check the box next to Use SSL/TLS.
  9. On the bottom of the window, click Test.

    1. In the Review and Accept Certificate window, check the box next to Accept this certificate, and click OK.
    2. In the Info window, click OK to acknowledge that the test was successful.
  10. Click OK to close the Add Source for User and Group Import window.
  11. On the left, click Access > Access Control.
  12. On the right, switch to the User Groups tab.
  13. In the toolbar, click the Import Group icon.
  14. In the Import User Groups page, ensure your Active Directory source is selected, enter your Horizon Administrators group name, click Search, and then select the group. Click Next.
  15. On the Roles and Objects page, from the Select Role drop-down, select Administrator.
  16. Check the box next to Assign this role to the group.
  17. Check the box next to Allow access to all objects in the system. Click Finish.
  18. Click Yes when warned about access to all Objects in the system.
  19. On the top right, click the person icon, and click Log Out.
  20. Change the drop-down to the Active Directory source, and login as an Active Directory account.

Session Timeout

  1. The vRealize Operations web page defaults to 30 minutes timeout. To change it, go to Administration > Management > Global Settings.
  2. In the row labelled Session Timeout, click the pencil icon.
  3. The maximum value for Session Timeout is 34560. Click Save.

Alerting

  1. In vRealize Operations console, go to Administration > Outbound Settings.
  2. On the right, click the green plus icon.
  3. From the Plugin Type drop-down, select Standard Email Plugin.
  4. Give the Instance a name.
  5. Enter the SMTP information
  6. On the bottom, click Test.

    1. In the Test Connection window, click OK to acknowledge that the test was successful.
  7. Then click Save to close the Add/Edit Outbound Instance window.
  8. You can then go to Alerts > Alert Settings > Notification Settings, and create notifications.
  9. Give the notification rule a name.
  10. For Method, select the Standard Email Plugin, and the outbound instance you created earlier.
  11. Enter Recipients.
  12. Select Triggers and Criticality. Click Save.

Install Horizon Adapter PAK File on vROps

Download the vROps for Horizon components for both new installs and upgrades:

  1. From the vRealize Operations for Horizon 6.7.1 download page, or from the vRealize Operations for Horizon 6.6.0 download page, download the vRealize Operations for Horizon Adapter.

  2. On the same page, also download the vRealize Operations for Horizon Broker Agent 64-Bit.

To install or upgrade the Horizon Adapter:

  1. Login to the vRealize Operations appliance web page (/ui path).
  2. Go to Administration > Solutions > Repository.

  3. On the right, scroll down, and then click Add/Upgrade or click Add a Management Pack.

  4. In the Select Solution page, click Browse.
  5. Browse to the Horizon Adapter .pak file and select it.

  6. Back in the Add Solution wizard, click Upload.

  7. After upload is complete, click Next.

  8. In the End User License Agreement page, check the box next to I accept the terms, and click Next.
  9. The Install page appears and installation begins automatically.
  10. After it’s done installing, in the Install page, click Finish.
  11. If you have NVIDIA GPUs, also install the NVIDIA Virtual GPU Management Pack for vRealize Operations.

Horizon Adapter Licensing

  1. In the vRealize Operations web page, go to Administration > Management > Licensing.
  2. On the right, click the green plus icon.
  3. In the Select product or solution drop-down, select VMware Horizon.
  4. Enter the vROps for Horizon license key, and click Validate. Note: you enter the Adapter key (or Horizon 7 Enterprise key), not the vRealize Operations Manager key.
  5. Click Save to close the Add License window.
  6. You might have to add objects to the License Groups as detailed at Associate Horizon Objects with Your vRealize Operations for Horizon License Key at VMware Docs.

Configure Horizon Adapter

Here are some guidelines regarding the Horizon Adapter:

  • You can only have one Horizon adapter per vRealize Operations appliance.
  • Each adapter can handle up to 10,000 virtual desktops.
  • Multiple Horizon pods can point to a single Adapter.

vRealize Operations Manager 8.0 and newer

Do the following to create and configure a Horizon Adapter:

  1. At the top of the page, click the tab named Administration.
  2. On the left, expand Solutions, and click Other Accounts.
  3. On the right, click the button labelled Add Account.
  4. In the Account Types page, click the button named Horizon Adapter.
  5. Give the Account a Name.
  6. Give the Adapter ID a name.
  7. Next to the Credential field, click the plus icon.
  8. Enter a Credential name.
  9. Enter a new secret key. You’ll enter this key later when installing the Broker Agent.
  10. Click OK.
  11. Click Test Connection.
  12. Click OK when prompted that test connection successful.
  13. At the bottom of the page, click Add.

vRealize Operations Manager 7.5 and older

Do the following to create and configure a Horizon Adapter:

  1. In vRealize Operations Manager, go back to Administration > Solutions > Configuration.
  2. On the right, in the top half, highlight the VMware Horizon solution.
  3. On the bottom right, highlight the Horizon Adapter and click the Configure icon.
  4. On the top part, highlight the Horizon Adapter.
  5. On the bottom, give the adapter a Display Name, and an Adapter ID.
  6. Click the green plus icon to add a credential.

    1. Give the credential a name.
    2. Enter a new password (shared key), and click OK to close the Manage Credential window. You’ll use this password later when configuring the Broker Agent.
  7. Back in the Manage Solution window, click Test Connection.

    1. In the Info window, click OK to acknowledge that the test was successful.
  8. On the bottom right, click Save Settings.

    1. In the Info window, click OK.
  9. Then click Close to close the Manage Solution window.

Enable SSH

If vROps 7.0 and newer:

  1. Point your browser to the /admin path at the vROps address.
  2. In the System Status page, in the row containing a node, on the far right is a slider to enable SSH.


  3. SSH to the appliance and login as admin.
  4. When you su to the root account, the initial root password is blank (not defined) and you’ll be prompted to enter a new root password.

If vROps Manager 6.7 or older, see VMware Knowledgebase article – Enabling SSH access in vRealize Operations Manager 6.0.x (2100515):

  1. Connect to the vRealize Operations Manager virtual machine console.
  2. Press Alt+F1, and login as root.
    Note: By default there is no root password configured. Just press <Enter>, and you’ll be prompted to enter a root password.
  3. Start the SSH service by running the command:
    service sshd start
  4. To configure SSH to start automatically run this command:
    chkconfig sshd on

Install Horizon Broker Agent

Only install the Broker Agent on one Horizon Connection Server in each pod.

  1. Log in to one Horizon Connection Server in your Horizon pod.
  2. Run the downloaded VMware-v4vbrokeragent-x86_64-6.7.1-15585151 or VMware-v4vbrokeragent-x86_64-6.6.0.exe.

  3. In the Welcome to the VMware vRealize Operations for Horizon Broker Agent Setup Wizard page, click Next.

  4. In the End-User License Agreement page, check the box next to I accept the terms in the License Agreement, and click Next.
  5. In the Ready to install the Broker Agent page, click Install.
  6. In the Completed the VMware vRealize Operations for Horizon Broker Agent Setup Wizard page, click Finish.

Configure Horizon Broker Agent

  1. The Configuration tool will appear immediately after installation. Or launch vRealize Operations for Horizon Broker Agent Settings from the Start Menu.
  2. In the Pair Adapter page, enter the IP address of the vRealize Operations appliance, enter 3091 for the port, enter the adapter password (configured earlier), and click Pair.
  3. After broker pairing is successful, click Next. If this doesn’t work, make sure the firewall ports are opened on the vRealize Operations appliance.
  4. In the Connection Server page, enter credentials for Horizon View, and click Test.
  5. Then click Next.
  6. In the Event DB and Desktop Pool page, enter the SQL credentials to access the Events database, and click Test.
  7. Then click Next.
  8. In the Configure App Volumes page, enter the App Volumes info, and click Test. Click the plus icon to add it to the list. Then click Next.
  9. In the Monitor Unified Access Gateway page, enter an appliance name, enter the UAG IP, enter 9443 as the port, enter the admin credentials, and click Test.
  10. Click the plus icon to add the Unified Access Gateway appliance to the list. Then click Next.
  11. In the Intervals and Timeouts page, click Next.
  12. In the Logging page, click Next.
  13. In the Broker Agent Service page, click Start. Then click Next.
  14. In the Ready to Complete page, click Finish.
  15. In the vRealize Operations web console (/ui), from the Dashboards page, you can view the Horizon Adapter Self Health dashboard to verify that the adapter and broker agent are functional.

Use vROps for Horizon

Cameron Fore at Location analysis using vROPs for Horizon explains how to create Custom Groups per branch location and report (super metric) average latency for each location.

Cameron Fore at How to leverage Historic User Reporting in vROPs for Horizon 6.5 provides a dashboard to show Horizon User History.

Related Pages

37 thoughts on “VMware vRealize Operations for Horizon 6.7.0”

  1. Hi Carl,

    Some of the widgets in Horizon RDS Host Details are having a question mark. The adapter status is collecting and data receiving as well. Some details are getting collected(eg: RDS host PCoIP Trip latency is having a question mark).
    Is this the normal behaviour?

    Thanks in advance!!

  2. Carl, If we want to Horizon DaaS , what is needed to installed on the desktops , Any partiular agent ? I undersatnd the broker agent is installed only on connection servers for monitoring the VDI’s .. what is needed to monitor the desktops per se DaaS ?

    Many thanks

  3. Carl,

    Is there a way I can configure vROPs to get a notification and/or reset a VM when a desktop goes to ‘Agent Unreachable’ state?

  4. Hi Carl,

    Dont you need to install vRealize Operations for Horizon Desktop Agent during horizon agent installation for each master image?

    Thanks

    1. The Desktop Agent is included with the Horizon Agent. It’s on the Optional Features that is selected by default.

  5. Hi Carl,
    I have a question about Horizon Broker Agent, I need to install a remote collector, and do i need to install the Horizon Broker Agent in it ?

  6. Hello.
    I have two security servers that in my infrastructure but only one of them is sending the number of connections to vRops. I’m using vRops 8.0.1 and adapter and Broker agent are in the version 6.7.1. Any suggestion??

    Thanks in advance.

    Diego Bejar

  7. G’day Carl,

    We are having issues with the Horizon vRops agent not tracking Application usage and session data.

    The v4v-process-xx.logs on the Instant Clones are filled with the message ‘Failed to get value for instance :, metric name UserApplication|*|Application Load Time

    e.g. ‘Failed to get value for instance NT AUTHORITY\SYSTEM:wsnm.exe, metric name UserApplication|*|System Application Load Time

    There are other metrics missing too, but oddly some metrics are working.

    Any ideas would be appreciated 🙂

  8. Carl – FYI there is a problem with the version 6.6.0-9844216 V4H Adapter and Broker agent. The SHA1 digital signing cert for these expired on 12/21/2019, and they have stopped working. We opened VMware case 19090832912 on 12/27, and they provided a new version (6.6.0-15369289) of both of these products, which seem to work fine. The signature on the new binaries is from 12/25/2019, so this must be hot off the presses.

  9. Post setup and all I am still not able to find a way around to get total VDI usage hours of a user in a month/week

    1. There’s an agent installed on one Connection Server. And each virtual desktop and/or RDS Host also has a vROps Agent included with the Horizon Agent installation.

      1. Carl is possible to vicunlate Citrix ADC to vmware vrealize log insight monitoring, is there documentation ? Best regards.

          1. Thanks for the time. Is there a document on which I can support myself to create the policy you mention?

  10. I’m trying to remove unused replicas using sviconfig. Result is no output of replica.txt file and -move doesn’t work either. Here’s what I’m getting.

    Establishing database connection.
    Database connection established successfully.
    Exploring replica.
    Load data from SVI_VC_CONFIG_ENTRY table.
    Load replica info from database.
    Sviconfig finished with an error. Exit code: 4
    Invalid certificate.

  11. HI Carl, thanks for all you do!
    I am having a problem I cannot find the solution to – UNKNOWN_FAULT_FATAL – Either the resource pool: resgroup-8 is empty or all its hosts are marked for maintenance.
    I put the host in maintenance mode as I would for a normal environment – I did not set the instant clone maintenance value. I also deleted the instant clones. Now I cannot provision any instant clones, can you help me?
    Thanks!

  12. I have a pool of VM’s that are all showing 100% VM RAM Usage. The only difference between this pool and the rest is that this pool has NVIDIA vGPU’s and Autodesk AEC installed. Machines with no users logged in are showing 100% as well. Any ideas?

      1. It appears it’s an issue with ESXi 6.5 (I’m using 6.5u2) – I found it mentioned in the NVIDIA GRID release notes for v390.42-391.03 on page 31. On VMware vSphere Hypervisor (ESXi) 6.5, the web client shows a memory usage alarm with critical severity for VMs to which a vGPU is attached even when the VMs are idle. When memory usage is monitored from inside the VM, no memory usage alarm is shown. The web client does not show a memory usage alarm for the same VMs without an attached vGPU.

        1. It is not just ESXi 6.5, ESX 6.0 has the exact same issue. It is because you need to fully reserve all memory when using vGPU.

  13. There is no status in the Horizon Adapter Self Health after adding the vRealize Operations for Horizon Licensing, the steps outlined in the link by Zuma Ac have been followed. The license has a delivery date of 12 Feb, does this mean they will auto activate on that date ?

    1. I am trying configure App Volumes Manager in The broker agent but all I get is “Cannot login the App Volumes Manger”. If I check the activity log in App Volumes I see the system making a “Manager API Login” action that is in red. What am I missing here?

Leave a Reply to Zuma Ac Cancel reply

Your email address will not be published. Required fields are marked *