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 called HyLabs.

  • HySecure: Accops security gateway that helps implement ZTNA-based secure remote internet access.

  • 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 DVMs.

  • Session Provider: A server that can 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 included in the dedicated session provider category and used to create and deliver virtual machines as desktops to end-users.

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

  • Built-in Directory: The Built-in is HyWorks Controller’s user database, used for authentication and retrieving users’ entitlements.

  • Multi-tenancy: A single HyWorks deployment can serve one or more logical entities from 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 that can be configured to deliver HyWorks-managed desktops or applications. Resources within each organization can be shared in accordance with specific rules.

  • Registration: Upon initial communication with the Controller, the HyWorks client provides all basic information about the endpoint, and the Controller assigns a unique ID to it. 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 that allow multiple users to access graphical desktops and Windows applications remotely.

  • 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. Once accessed, the RemoteApp experience is identical to that of natively installed applications, except that it runs on the session host server.

  • Always Seamless: Application access mode in HyWorks to show remote applications in a 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 primarily used for troubleshooting when users experience connection issues with 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. The HyWorks controller can be installed as a management or session node during installation.

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

  • Active-Active: HyWorks deployment mode, where multiple HyWorks session nodes can be deployed to provide a 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: A Group of two or more controllers, formed to have high availability.