This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Multi-type licensing
Multi-type licensing supports consumption of different license types for Delivery Groups on a single XenApp or XenDesktop site. Type is a single combination of Product ID (XDT, MPS) and Model (UserDevice, Concurrent). The Delivery Groups must use the Product Edition set for the site.
If multi-type licensing is not configured, different license types can be used only when configured on entirely separate sites. The Delivery Groups use the site license.
To determine the Delivery Groups that consume the different types of licenses, use these Broker PowerShell cmdlets:
- New-BrokerDesktopGroup
- Set-BrokerDesktopGroup
- Get-BrokerDesktopGroup
To install licenses, use:
- Citrix Studio
- Citrix Licensing Manager
- License Administration Console
- citrix.com
Subscription Advantage dates are specific to each license file and to each product and model. Delivery Groups set differently might have different Subscription Advantage dates than each other.
Broker PowerShell SDK
The DesktopGroup object has these two properties you can manipulate using the associated New-BrokerDesktopGroup and Set-BrokerDesktopGroup cmdlets.
Name | Value | Restriction |
---|---|---|
LicenseModel | An enum (Concurrent or UserDevice) specifying the licensing model for the group. | If the feature toggle is disabled, attempting to set a property fails. |
ProductCode | A text string of XDT (for XenDesktop) or MPS (for XenApp) specifying the licensing Product ID for the group. | If the feature toggle is disabled, attempting to set a property fails. |
New-BrokerDesktopGroup
Creates a desktop group for managing the brokering of groups of desktops. For more information on this cmdlet, see https://citrix.github.io/delivery-controller-sdk/Broker/New-BrokerDesktopGroup/.
Set-BrokerDesktopGroup
Disables or enables an existing broker desktop group or alters its settings. For more information on this cmdlet, see https://citrix.github.io/delivery-controller-sdk/Broker/Set-BrokerDesktopGroup/
Get-BrokerDesktopGroup
Retrieves desktop groups matching the specified criteria. The output of the Get-BrokerDesktopGroup cmdlet includes the ProductCode and LicenseModel properties of the group. If the properties have not been set using New- BrokerDesktopGroup or Set-BrokerDesktopGroup, null values are returned. If null, the site-wide license model and product code are used. For more information on this cmdlet, see https://citrix.github.io/delivery-controller-sdk/Broker/Get-BrokerDesktopGroup/.
Configure different license products and models per Delivery Group
- Open PowerShell with Administrative rights and add the Citrix snapin.
- Run the command Get-BrokerDesktopGroup –Name “DeliveryGroupName” to view the current license configuration. Find the parameters LicenseModel and ProductCode. If you haven’t configured these parameters before, they might be blank.
Note:
If a Delivery Group does not have license information set, apply the Site level Site license.
- To change the license model, run the command Set-BrokerDesktopGroup –Name “DeliveryGroupName” –LicenseModel LicenseModel.
- To change the license product, run the command Set-BrokerDesktopGroup –Name “DeliveryGroupName” –ProductCode ProductCode.
- Enter the command Get-BrokerDesktopGroup –Name “DeliveryGroupName” to validate the changes.
Note:
You cannot mix and match editions, for example, Premium and Advanced licenses.
- To remove the license configuration, run the same Set-BrokerDesktopGroup commands as described above and set the value to $null.
Note:
Studio doesn’t display the license configuration for each Delivery Group. Use PowerShell to view the current configuration.
Example
This PowerShell cmdlet example illustrates setting multi-type licensing for two existing Delivery Groups and creates and sets a third Delivery Group.
To see the license product and license model associated with a Delivery Group, use the Get-BrokerDesktopGroup PowerShell cmdlet.
- We set the first Delivery Group for XenApp and Concurrent. Set-BrokerDesktopGroup -Name “Delivery Group for XenApp Platinum Concurrent” -ProductCode MPS -LicenseModel Concurrent
- We set the second Delivery Group for XenDesktop and Concurrent. Set-BrokerDesktopGroup -Name “Delivery Group for XenDesktop Platinum Concurrent” -ProductCode XDT -LicenseModel Concurrent
- We create and set the third Delivery Group for XenDesktop and UserDevice. New-BrokerDesktopGroup -Name “Delivery Group for XenDesktop Platinum UserDevice” -PublishedName “MyDesktop” -DesktopKind Private -ProductCode XDT -LicenseModel UserDevice
Special considerations
Multi-type licensing has different functionality than regular XenApp and XenDesktop licensing.
There are no alerts and notifications from Director or Studio:
- No information when nearing license limits or the trigger or expiry of the supplemental grace period.
- No notification when a specific group has a problem.
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.