Terminologies

In Accops workspace deployments, 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 reservation management system in HyWorks
HyLabs: Reservation management system is referred as HyLabs
HySecure: Accops SSL-VPN software being used for secure access over internet
Gateway: Referred for instances of HySecure servers
Endpoints/Devices: End-user terminals running with Accops HyWorks clients are referred as endpoints or devices
HyDesk: Thinclients 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 as DVM.
Session Provider: Session providers are servers which 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 server (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 supports multiple user sessions on single instance of servers are referred as Shared Session Hosts.
Built-in Directory: Built-in is HyWorks Controller own user database, 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 same or different organizations. This kind of deployment structuring is referred 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 Controller, HyWorks client provides all basic information about endpoint and then controller assigns a unique id for identification of endpoint. The process is known as registration.
Heartbeat: HyWorks clients periodically send status/ configuration information to Controller, this periodic status update call is named as 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 as terminal servers.
Shared Hosted Desktop (SHD): Servers installed with HyWorks Session Host Agent module are referred as shared hosted desktop.
Session Host Agent: HyWorks module responsible for enabling Windows servers to deliver applications and desktops, managing sessions etc.
Monitoring Service: Service responsible for collecting performance data from shared hosted desktop servers and providing it to 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, experience of natively installed application only except for the fact that it is running on session host server.
Always Seamless: Application access mode in HyWorks to show remote applications in seamless window with experience of natively installed application. The option is provided in connection profiles.
Never Seamless: Application access mode which basically 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: Process of adding applications in HyWorks is called publishing.