Skip to main content
Question

Please fix "Horizon 8 on Nutanix AHV" limitations.

  • Oct 28, 2026 4:50 AM UTC
  • 4 replies
  • 69 views

We operate a hybrid VDI environment: Windows 10 on vSphere and Windows 11 on Nutanix AHV(Horizon 2603/2606).

While vSphere works flawlessly, we face two critical blockers on Nutanix AHV that force inefficient manual workarounds.

We request feature parity with vSphere.

 

Issue 1: Manual Pool Registration Limit

Problem: When deploying VMs from a master image with Horizon Agent pre-installed, only one VM successfully registers in a Manual Desktop Pool on Nutanix AHV.

Current Workaround: To register multiple VMs, we must exclude the Horizon Agent from the master image and install it individually on every single VM after provisioning.

Expectation: Nutanix AHV should support standard golden image deployment (Agent pre-installed) allowing multiple VMs to register simultaneously, just like vSphere.

 

Issue 2: Persistent Black Console After Disconnect

Problem: After a user disconnects a session, the VM's console screen remains Black. Administrators can not view the desktop state or perform maintenance via console.

Current Workaround: The only way to restore the console view is to manually reboot the VM.

Expectation: The console should automatically recover or show the login screen after session disconnect, matching the behavior on vSphere.

 

Business Impact:

These issues break our automation workflow on Nutanix AHV that is not needed in our vSphere environment.

Please fix these Nutanix AHV-specific limitations.

4 replies

JeroenTielen
Forum|alt.badge.img+8

Those are not Nutanix issues. Please contact omnissa support for that. 


  • Author
  • Voyager
  • Oct 28, 2026 7:51 AM UTC

Those are not Nutanix issues. Please contact omnissa support for that. 

Hello,

Thank you for your response and guidance.

 

  • Feature Improvement Requests
    • We are currently working with Omnissa Support.
    • Feature Requests have been escalated to the Product Team regarding the Manual Pool limitations (registration, power management, and maintenance mode).
  • Black Console Issue
    • We have opened a dedicated Support Request with Omnissa.
    • Let me share the findings in this thread once the root cause is identified.


I appreciate the community's support.


Forum|alt.badge.img+3
  • Trailblazer
  • Oct 28, 2026 5:44 PM UTC

Disconnect leaves the Windows session disconnected but does not necessarily log the user off; horizon lets you configure a disconnected session to log off immediately, after a delay, or never.  As possible workaround until the issue has been resolved; test automatically log off after disconnect or set disconnect session time limit to immediately in the horizon agent GPO.  Hopefully that allows the console to return to the login screen.


  • Author
  • Voyager
  • Oct 29, 2026 12:33 AM UTC

Disconnect leaves the Windows session disconnected but does not necessarily log the user off; horizon lets you configure a disconnected session to log off immediately, after a delay, or never.  As possible workaround until the issue has been resolved; test automatically log off after disconnect or set disconnect session time limit to immediately in the horizon agent GPO.  Hopefully that allows the console to return to the login screen.

 

Hello DrewPlaaster,

Thank you for your response and guidance.

 

I wanted to share some important information regarding the black screen issue with the console.

Please note that the black screen in the console cannot be resolved by logging off the Guest OS (Windows 11).

Even after restarting Windows, the console view remains black.

The only way to restore the console display is by performing a forced reset or restart of the console from the hypervisor side.

 

Nutanix said that Omnissa is aware of this bug and is working on a fix for a future release.
But Omnissa support likes "I would suggest to investigate the issue from Nutanix hypervisor to know the cause of the Blank screen on console which would help to resolve the issue."