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!
Policies
Policies are a collection of settings that define how sessions, bandwidth, and security are managed for a group of users, devices, or connection types.
You can apply policy settings to VDAs or to users. You can edit settings in Web Studio or in the Active Directory Group policy objects (GPOs). You can specify filters (object assignments) for policies. If you do not specifically assign policies to filters, settings are applied to all user sessions.
You can apply policies on different levels of the network. Policy settings placed at the Organizational Unit GPO level take the highest precedence on the network. Policies at the Domain GPO level override policies on the Site Group Policy Object level. The Site Group Policy Object level overrides any conflicting policies on both the Microsoft and Citrix Local Policies levels.
All Citrix Site Policies are created and managed in the Web Studio console and stored in the Site Database. Group Policies are created and managed by using the Microsoft Group Policy Management Console (GPMC) and stored in the Active Directory. Microsoft Local Policies are created in the Windows Operating System and are stored in the registry.
Web Studio uses a Modeling Wizard to help administrators compare configuration settings within templates and policies to help eliminate conflicting and redundant settings.
Settings are merged according to priority and their condition. Any disabled setting overrides a lower-ranked enabled setting. Unconfigured policy settings are ignored and do not override lower-ranked settings.
Web Studio policies can also have conflicts with group policies in the Active Directory, which might override each other depending on the situation.
All policies are processed in the following order:
- From the Citrix Workspace app, the end user logs on to a VDA using domain credentials.
- Citrix policies are processed for the end user and for the VDA
-
Policies are applied in the following order:
- Local policies
- Site policies
- Domain policies
- OU (Organizational unit) policies
Note:
- All policies might not be present at the four levels. For most of the customers, only site policies are used. Local policies require the user to log on to VDA to edit policies. Hence, these policies are almost never used.
- We do not support mixing Windows and Citrix policies in the same GPO.
For complete information about Citrix policies, see the following:
- Work with policies
- Policy templates
- Create policies
- Prioritize, model, compare, and troubleshoot policies
- Default policy settings
-
Note:
The policy settings references for Citrix DaaS are the same as the policy settings for Citrix Virtual Apps and Desktops. So, you can refer to the Policy settings reference section in the Citrix Virtual Apps and Desktops documentation for Citrix DaaS also.
Share
Share
In this article
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.