Terminologies

In Accops workspace deployments, the following terms can be used frequently:

  • Controller: Accops HyWorks Controller server.

  • Management Console: Administrator portal for managing HyWorks.

  • RMS Portal: Portal for accessing and managing the reservation management system in HyWorks.

  • HyLabs: The reservation management system is referred to as HyLabs.

  • HySecure: Accops SSL-VPN software being used for secure access over the internet.

  • Gateway: Referred for instances of HySecure servers.

  • Endpoints/Devices: End-user terminals running with Accops HyWorks clients are referred to as endpoints or devices.

  • HyDesk: Thin clients embedded with Accops HyWorks Clients.

  • HyLite: Accops HTML5-based access points for connecting applications/ desktops.

  • DVM: Desktop Virtual Machine. Virtual machines configured and managed in HyWorks are referred to as DVM.

  • Session Provider: Session providers are servers that can be used to deliver applications or desktops to end-users. Can be categorized into dedicated, shared, or external providers.

  • Dedicated Session Providers: Hypervisors (VMware ESXi, Microsoft Hyper-V, Nutanix AHV) or hypervisor management servers (VMware vCenter Server, Microsoft SCVMM, Nutanix Prism Central) can be kept under the category of dedicated session providers, which can be used to create and deliver virtual machines as desktops to end-users.

  • Shared Session Hosts: Servers (Microsoft Windows Servers, Ubuntu), which support multiple user sessions on a single instance of servers are referred to as Shared Session Hosts.

  • Built-in Directory: The Built-in is HyWorks Controller’s user database, which can be used for authentication and getting user's entitlements.

  • Multi-tenancy: A single HyWorks deployment can be used to serve one or many logical entities of the same or different organizations. This kind of deployment structuring is referred to as multi-tenancy.

  • Organization: An organization in HyWorks, represents a logical entity, which can be configured to deliver HyWorks managed desktops or applications. The resources in each organization can be shared based on certain rules.

  • Registration: On first communication with the Controller, the HyWorks client provides all basic information about the endpoint and then the controller assigns a unique ID for identification of the endpoint. The process is known as registration.

  • Heartbeat: HyWorks clients periodically send status/configuration information to the Controller, this periodic status update call is named a heartbeat.

  • Remote Desktop Server (RDS): Servers allowing multiple users to remotely access graphical desktops and Windows applications.

  • Terminal Server: Remote desktop servers were previously referred to as terminal servers.

  • Shared Hosted Desktop (SHD): Servers installed with the HyWorks Session Host Agent module are referred to as shared hosted desktops.

  • Session Host Agent: HyWorks module responsible for enabling Windows servers to deliver applications and desktops, managing sessions, etc.

  • Monitoring Service: The service responsible for collecting performance data from shared hosted desktop servers and providing it to the HyWorks controller on demand.

  • Session Team: Collection of multiple session host servers, grouped to support load balancing and high availability of shared hosted desktops.

  • RemoteApp: Applications installed on session host servers and configured to be delivered remotely. The RemoteApp once accessed gives, the experience of natively installed applications only except for the fact that it is running on the session host server.

  • Always Seamless: Application access mode in HyWorks to show remote applications in the seamless window with the experience of natively installed applications. The option is provided in connection profiles.

  • Never Seamless: Application access mode that displays all background activities while sessions are configured. The mode is mostly used for troubleshooting where users are facing connection issues to published applications. The option is provided in connection profiles.

  • Application Publishing: The process of adding applications in HyWorks is called publishing.

  • Management Node: The HyWorks controller node performs only management tasks and does not participate in serving client or session host requests. HyWorks controller can be installed as a management or session node during installation.

  • Session Node: Also termed as broker node as well. If the HyWorks controller is installed as a session node, then it will only serve as a client and session host request and will not participate in management tasks.

  • Active-Active: HyWorks deployment mode, where multiple HyWorks session nodes can be deployed to provide load-balanced multi-node deployment.

  • Active-Passive: Two-node deployment mode of HyWorks, where one server functions as primary and the other acts as secondary.

  • SRMS: Session recording management server.

  • Cluster: Group of two or more controllers, formed to have high availability.