2. Vendor-Specific Information

Section Contents:

 

2.1. NICE Desktop Cloud Visualization 2023.1

Installation and Configuration Resources

For hardware requirements, installation and configuration of NICE DCV, refer to the NICE DCV Guide at https://d1uj6qtbmh3dt5.cloudfront.net/docs/DCV_Administration_Guide.pdf . For specific details about host requirements for OS and graphics cards, refer to the "Prerequisites" section of the document.

For more information and assistance with the installation of DCV, contact NICE Support at support@nice-software.com.

 

2.2. Citrix Virtual Desktop 7 2303 for Citrix Virtual Machines (via Citrix Workspace 2311)

Installation and Configuration Resources

For information on hardware requirements, installation and configuration, refer to the "Virtual Desktop" page of the Citrix Product Documentation site at https://www.citrix.com/downloads/citrix-virtual-apps-and-desktops/

 

2.3. Citrix Hypervisor 8.2.1 for Citrix Virtual Machines (via NICE DCV 2023.1)

Installation and Configuration Resources

For information on hardware requirements, installation and configuration, refer to "Citrix Hypervisor ® 8.2" at https://docs.citrix.com/en-us/citrix-hypervisor/8-2/citrix-hypervisor-8.2.pdf.

 

2.4. VMware vSphere ESXi 8.0 U1 Virtual Machines (via NICE DCV 2023.1)

Installation and Configuration Resources

For information on hardware requirements, installation and configuration of Horizon View 8.11 2309, refer to the "Getting Started" page of the VMware Horizon Support Center at https://www.vmware.com/support/horizon-view.html.

For information on vSphere ESXi 8.0 U1 , refer to the vSphere Hypervisor ESXi Support Center at https://www.vmware.com/support/vsphere-hypervisor.html.

 

2.5. VMware Horizon View 8.11 2309 for VMware vSphere ESXi Virtual Machines

Installation and Configuration Resources

For information on hardware requirements, installation and configuration of Horizon View 8.11 2309, refer to the "Getting Started" page of the VMware Horizon Support Center at https://www.vmware.com/support/horizon-view.html.

For information on vSphere ESXi 8.0 U1 , refer to the vSphere Hypervisor ESXi Support Center at https://www.vmware.com/support/vsphere-hypervisor.html.

 

2.6. VNC Connect 7.9 with VirtualGL 3.1

Installation and Configuration Resources

For hardware requirements, installation and configuration of VNC Connect, refer to the VNC Connect support page at http://www.realvnc.com/support/documentation.html.

Note that VirtualGL is required to support server-side rendering with VNC Connect, and must be installed prior to installing VNC Connect. VirtualGL is available from http://www.virtualgl.org/.

The On Red Hat 8+ servers, users may encounter a hang or grey screen. In such cases, refer to the link below vnc documentation to modify xstartup file; https://help.realvnc.com/hc/en-us/articles/360003474792-Why-does-VNC-Server-in-Virtual-Mode-on-Linux-appear-to-hang-show-a-gray-screen-or-not-start-at-all-

To achieve server-side rendering for accelerated graphics performance, Ansys applications must be executed using the VirtualGL vglrun command.

Known Issues and Limitations

  • In the case of Icepak or ICEM graphics failure, a configuration is required for affected fonts. For more information, see the related NICE Support page at http://support.nice-software.com/solution/articles/1000052632-x11-and-dcv-fonts-configuration.

  • Launching polydata, polymat, polystat, or polyman via (vglrun) Virtual GL and VNC Connect on some remote Linux platforms may throw a [VGL] error message. Since these products do not actually benefit from VirtualGL, the workaround is simply to avoid using VirtualGL and to launch the executable normally (84767).

  • To achieve server-side rendering when using Fluent from Workbench, the additional configuration steps below will be necessary in addition to the above described command or GUI based methods:

    • If WorkBench has not yet been launched, define the following environment (assuming bash, tcsh):

      setenv CORTEX_PRE /<Installation_Path_VirtualGL>/bin/vglrun

    • If WorkBench has been launched but Fluent has not yet been launched, define the following in the Fluent launcher window:

      More options>Environment (tab)> CORTEX_PRE=/<Installation_Path_VirtualGLr>/bin/vglrun

  • For all Linux Operating Systems, Xstartup file must be updated with correct KDE session.

 

2.7. Microsoft Windows Remote Desktop

Installation and Configuration Resources

Information on the configuration and use of Windows Remote Desktop is available from https://support.microsoft.com/en-in/help/4028379/windows-10-how-to-use-remote-desktop.

 

2.8. OpenText Exceed TurboX 12.5.2

Installation and Configuration Resources

For hardware requirements, installation, and configuration of Exceed TurboX, refer to the Installation Guide in the Exceed TurboX installation package area.

To achieve server-side rendering for accelerated graphics performance, the hardware acceleration in Xterm should be configured as ON.

Xterm >Advance mode>Protocol >Hardware acceleration ON

To achieve server-side rendering for accelerated graphics performance, Ansys applications must be executed using the ETX ssrrun command.

Known Issues and Limitations

  • To achieve server-side rendering when using Fluent from Workbench, the following additional configuration steps are necessary in addition to the above described command or GUI based methods:

    • If WorkBench has not yet been launched, define the following environment (assuming bash, tcsh):

      setenv CORTEX_PRE /<Exceed TurboX Node Installation_Path>/bin/ssrrun

    • If WorkBench has been launched but Fluent has not yet been launched, define the following in the Fluent launcher window:

      More options>Environment (tab)> CORTEX_PRE=/<Exceed TurboX Node Installation_Path>/bin/ssrrun

 

2.9. TurboVNC 3.1 with VirtualGL 3.1

Installation and Configuration Resources

For hardware requirements, installation, and configuration of TurboVNC, refer to the Turbo VNC support page at https://www.turbovnc.org/

Note that VirtualGL is required to support server-side rendering with TurboVNC and must be installed prior to installing TurboVNC. VirtualGL is available from http://www.virtualgl.org/.

The On Red hat7+ and CentOS 7 servers, users may encounter a hang or grey screen. In such cases, modify xstartup file. Ansys applications must be executed using the VirtualGL vglrun command.

Known Issues and Limitations

  • In the case of Icepak or ICEM graphics failure, a configuration is required for affected fonts. For more information, see the related NICE Support page at http://support.nice-software.com/solution/articles/1000052632-x11-and-dcv-fonts-configuration.

  • Launching polydata, polymat, polystat, or polyman via (vglrun) Virtual GL and TurboVNC on some remote Linux platforms may throw a [VGL] error message. Since these products do not actually benefit from VirtualGL, the workaround is simply to avoid using VirtualGL and to launch the executable normally (84767).

  • To achieve server-side rendering when using Fluent from Workbench, the additional configuration steps below will be necessary in addition to the above-described command or GUI based methods:

    • If WorkBench has not yet been launched, define the following environment (assuming bash, tcsh):

      setenv CORTEX_PRE /<Installation_Path_VirtualGL>/bin/vglrun

    • If WorkBench has been launched but Fluent has not yet been launched, define the following in the Fluent launcher window:

      More options>Environment (tab)> CORTEX_PRE=/<Installation_Path_VirtualGLr>/bin/vglrun

  • For all Linux Operating Systems, Xstartup file must be updated with correct KDE session.