Citrix DaaS™ for Citrix Service Providers
This article describes how Citrix Service Providers (CSPs) can set up and manage multitenant Citrix DaaS environments in Citrix Cloud. It also explains how tenant customers can access and co-manage their assigned environments through delegated administration.
For an overview of the features available for Citrix Partners, see Citrix Cloud for Partners.
The setup and management process involves two key areas:
-
Manage multitenant DaaS deployments as partner administrators: How CSPs (Partners) configure and manage multitenant DaaS environments in Citrix Cloud.
-
Manage your DaaS resources as tenant administrators: How tenant customers access and manage their own DaaS resources in cooperation with CSPs under multitenant deployments.
Requirements
-
To set up and manage a multitenant Citrix DaaS environment in Citrix Cloud™, Partners must meet the following prerequisites:
-
Have Citrix Service Provider partner status
-
Have a Citrix Cloud™ account.
-
Have an active multitenant Citrix DaaS subscription
-
-
To manage a tenant's DaaS resources in a multitenant Citrix DaaS environment, Tenant administrators must meet the following prerequisites:
-
Have Citrix Cloud account created by a CSP and added to the CSP's multitenant DaaS service
-
Limitations
This section outlines the current limitations in the CSP multitenant DaaS environment.
-
Tenant administrators can create and update hosting connections only after the partner administrator assigns a zone to the tenant scope. Tenant administrators still cannot manage tags because tag objects aren't scoped.
-
If a zone is assigned to the tenant scope, DaaS creates machine catalogs in that zone automatically. If no zone is assigned, the partner administrator must create the first machine catalog, assign it to a zone, and apply the appropriate scope in the partner’s Studio console.
-
Tenant administrators cannot access Workspace Environment Management™ (WEM) configuration sets. A partner administrator must assign the configuration set.
-
Folders under Machine catalogs are not yet scoped so that aren't accessible to tenant administrators.
Note:
The partner Studio console doesn’t automatically enforce scopes. You are responsible for selecting the appropriate scope when creating machine catalogs, delivery groups, and application groups for the appropriate tenant.