-
-
Test Profile Management with a local GPO
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!
Test Profile Management with a local GPO
We recommend you set up a test environment before deploying Profile Management in a production environment. A fully supported and easier means of transferring settings to the domain Group Policy Objects (GPOs) is based on a local installation on a machine.
The general workflow is as follows:
-
Install Profile Management on a machine.
-
Based on your answers to questions listed in Decide a configuration, configure Profile Management policies with a local GPO.
-
Test logon and logoff behaviors.
-
Adjust the local GPO settings until you receive satisfactory results.
Overview
You can test Profile Management safely using a local GPO if the machine is a member of a production OU. Local GPO policies take effect when OU and domain ones are not available. When using a local GPO, make sure no Profile Management GPOs are used elsewhere (for example, in the domain or sites).
If you can’t configure group policies using domain GPOs, you can use local GPOs as a long-term solution. However, this way introduces complexities into the environment, such as:
- Each machine must have the Profile Management ADMX files installed.
- Domain users possibly can’t maintain settings when accessing multiple machines.
Important:
We do not recommend using local GPOs as a long-term, enterprise solution.
Test the user experience
When implementing a profile solution, you must minimize the user experience differences when users access resources from various machines.
Users’ registry and files might vary depending on the physical machine, profile configuration, and operating system. Thus, you must configure Profile Management to address the differences between system installations on machines where the users roam.
To do so, check user access to resources in ways that mimic your production environment. These resources might include:
- A machine with locally installed applications
- A virtual desktop including streamed or locally installed applications
- A virtual app, either published on or streamed from a virtual apps server
- A Terminal Services client
Test operating system variations
Users might access applications from different operating systems. The variation between them might create conflicting settings within a single user profile.
For more information, see Profile versions.
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.