Organization Resource Sharing Concepts
-
With a freshly installed HyWorks Controller, a default organization is created
-
The default organization cannot be deleted, but can be modified
-
No sibling organization can be created at the default (root) organization level
-
With only a single organization, while logging-in client/ Management Console does not require a selection of the organization
-
-
Only parent organization resources can be shared with the child organizations and child organizations cannot share resources with their sibling organizations or the parent.
-
Configurations available at the Root organization level (Global Configurations): Some configurations are global (System) configurations and are either available to the Super-administrator or at the default organization level only. The following are such resources:
-
Role creation
-
Default Settings for endpoints
-
Server Configurations: HyWorks Controller for making/managing a cluster
-
System Configurations: License, Backup Restore, SMTP Configurations, Service Path, Service Configurations, Advance Configurations
-
-
Resources/Configurations which are not shared among organization: Some resources are organization-specific and cannot be shared, such as the following:
-
Connection Profiles
-
Session Teams
-
Shared Hosted Session Host
-
Desktop Pools
-
Endpoints
-
Desktop VMs
-
Built-in Users/ Groups
-
-
Sharable resources/Configurations among organizations: Some resources are sharable, such as the following:
-
Authentication servers
-
Authentication Domains
-
Realm Settings
-
Session Providers (Dedicated and External)
-
Applications
-
-
Shared resources cannot be modified at the child organization level but can be configured
-
Configurations getting created for every organization: With every organization (default or created by the Administrator), some resources are created which cannot be deleted, such as:
-
Default Connection Profile
-
Built-in Directory
-
Default Session Team (Windows and Linux)
-
Default Device Groups
-
-
A Share license is part of the HyWorks system. All organizations can use this license as long as they are not restricted
Based on the above mentioned specifications, organizational structure can be planned and deployed. For example:
-
In a deployment where a single authentication server is present, but the application servers are in a workgroup and not part of the domain, a structure can be followed where the authentication server will be configured at the root level and will be shared with all the child organizations. When configuring the child organizations, every child organization can choose the authentication server as the one being shared from the parent and the authorization server as the Built-in for the workgroup environment.
-
In another deployment, where only one vCenter server is available as the Session Provider, it can be configured at the root level and the child organizations can use this session provider and use it's desktop VMs as needed.
-
In a deployment where no sharing is expected and they can use their own authentication server, nothing should be configured and shared from the parent organization. Instead, each child organization can define resources at it's own level and use their own resources.