-
-
Standalone Citrix Secure Ticketing Authority (STA) service (Preview)
-
-
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!
Standalone Citrix Secure Ticketing Authority (STA) service (Preview)
The standalone Citrix Secure Ticketing Authority (STA) service enables you to have more control over the delivery of STA tickets in your environment.
The standalone Citrix STA service is installed on every Cloud Connector in a Resource Location by default. This service shifts STA ticketing from the Citrix Cloud ticketing service to the Cloud Connectors and standardizes ticketing operations across both normal and LHC modes. The standalone STA service reduces reliance on cloud services and improves the performance of the solution when entering LHC mode.
Standalone Citrix STA service scenarios
The table shows the various scenarios where Standalone STA service works.
| StoreFront | Gateway | Environment | Ticketing service in Normal mode | Ticketing service in LHC mode |
|---|---|---|---|---|
| Citrix Workspace | On-premises Citrix Gateway | Cloud | Standalone STA service | Standalone STA service. See Service Continuity for more information on how Service Continuity functions if the STA service is unavailable. |
| Citrix Workspace
|
On-premises Citrix Gateway
|
On-premises
|
Standalone STA service
Note: Set the registry key HKEY_LOCAL_MACHINE\Software\Citrix\XaXdCloudProxyPersist\StandaloneStaServiceForced to 1. |
Standalone STA service. See Service Continuity for more information on how Service Continuity functions if the STA service is unavailable.
|
| On-premises StoreFront | Citrix Gateway Service | Cloud | Standalone STA service | Standalone STA service |
| On-premises StoreFront | On-premises Citrix Gateway | Cloud | Standalone STA service | Standalone STA service |
| On-premises StoreFront | Citrix Gateway Service | On-premises | Standalone STA service | Standalone STA service |
System requirements
You need the following system requirements:
- On-premises StoreFront: Version 2311 or later
- Delivery Controller: Version 2503 or later
Configuration required in on-premises environment
If you’re in on-premises environment using the Citrix Gateway Service with on-premises StoreFront and want to take advantage of the standalone STA service, you must install Cloud Connectors.
Step 1: Create a resource location on Citrix Cloud
- Onboard to Citrix Cloud. For more information, see Create a Citrix Cloud account and Connect to Citrix Cloud.
- On Citrix Cloud, install Cloud Connectors and associate them with the resource location. For more information, see Cloud Connector Installation.
Step 2: Create a zone in your on-premises Delivery Controller
In your on-premises Delivery Controller, create a new zone and map it to the resource location created in Citrix Cloud.
Manually update the ZoneMapping.yml file to reflect the correct mapping of on-premises zones to cloud resource locations.
The ZoneMapping.yml file is in %HOMEPATH%\Documents\Citrix\AutoConfig. The content of the .yml file is a dictionary with the zone name as the key and the resource location name as the value.
For example, an on-premises Citrix Virtual Apps and Desktops site with a primary zone called “Zone-1” and a secondary zone called “Zone-2” is mapped to a Citrix DaaS deployment with two newly created cloud resource locations called “Cloud-RL-1” and “Cloud-RL-2”. In this instance, the ZoneMapping.yml is configured as follows:
Zone-1: Cloud-RL-1
Zone-2: Cloud-RL-2
Note:
Add a space between the colon and resource location name. If you use spaces in the zone or resource location name, enclose the name with quotes.
StoreFront Configuration
Configure StoreFront to use the FQDN of Cloud Connectors as STA servers.
- Open the StoreFront management console.
- Navigate to Stores > Manage Citrix Gateways and click Add.
- Provide Display name for the routing gateway.
- Select Citrix Gateway Service for Gateway type.
- Click Next and go to the Cloud Connectors tab.
- Click Add to add the cloud connector URLs.
- Enable Load balance multiple servers and Enable session reliability if necessary.
- Click OK.
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.