Skip to content
Was this article helpful?

Manage Citrix DaaS using Remote PowerShell SDKs

Citrix DaaS (formerly Citrix Virtual Apps and Desktops service) provides an SDK based on a number of Microsoft Windows PowerShell version 3.0 cmdlets. These SDKs helps you to automate tasks you perform using Citrix Studio console, together with tasks you cannot do with Studio alone.

To automate tasks:

  • Understand the differences in the policies rules when you access it using SDKs and Citrix Studio console.
  • Follow how to use PowerShell SDKs
  • Use Citrix Group Policy Provider.
  • Follow the syntax, descriptions, parameters, and input types for each of the PowerShell SDK commands associated with different components and services of Citrix DaaS.

Differences in policy rules

There are differences between the SDK and the Studio console in terms of policy rules. Entitlement and assignment policy rules are independent entities in the SDK; in the console, these entities are not visible as they are seamlessly merged with the Delivery Group. Also, access policy rules are less restrictive in the SDK.

Use the SDK

The SDK comprises of a number of PowerShell cmdlets packaged both as modules and snap-ins. These are installed automatically by the installation wizard when you install the Controller or Studio components.

To access and run the cmdlets:

  1. Start a shell in PowerShell 3.0.

    To start a shell from the console, click Studio, select the PowerShell tab, and click on Launch PowerShell.

    You must run the shell or script using an identity that has Citrix administration rights. Although members of the local administrators group on the Controller automatically have full administrative privileges to allow Citrix Virtual Apps and Desktops to be installed, Citrix recommends that for normal operation, you create Citrix administrators with the appropriate rights, rather than use the local administrators account.

  2. To use SDK cmdlets within scripts, set the execution policy in PowerShell. For more information about PowerShell execution policy, see your Microsoft documentation.

  3. To use this SDK through the snap-ins, add the snap-ins you require into the PowerShell environment using the Add-PSSnapin command in the Windows PowerShell console. This step is unnecessary if you want to use the cmdlets in this SDK through the modules.

    V1 and V2 denote the version of the snap-in (XenDesktop 7 snap-ins are version 2.).

    For example, type:

    Add-PSSnapin Citrix.ADIdentity.Admin.V2

    To import all the cmdlets, type:

    Add-PSSnapin Citrix.\*.Admin.V\*

    After importing, you have access to the cmdlets and their associated help.

    For an example of a typical use case, see Get started with the SDK.

Was this article helpful?