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!
Mobile or static
Are your machines permanently connected to the Active Directory domain? Laptops and similar mobile devices probably are not. Similarly, some deployments might have fixed machines with persistent local storage but the machines are separated from the data center for significant periods of time. For example, a remote branch office is linked to the corporate headquarters by satellite communications. Another example is disaster recovery, where infrastructure is being restored and power or communications are intermittent.
Typically, Profile Management is resilient to short network outages (less than 24 hours) so long as the user does not log off while the network is unavailable. In these circumstances, you can optimize Profile Management in several ways that significantly speed up the logon process. This is the static case.
Where extended periods of disconnection are expected or users must be able to log off or shut down their computers while disconnected from the corporate network, you cannot optimize Profile Management. When users reconnect, logons are slow while the entire profile is fetched from the user store. This is the mobile case.
The mobile case
For extended periods of disconnection (and only intermittent periods of connection to the Active Directory domain), enable the Offline profile support policy. This approach automatically disables the effect of the following policies, controlling optimizations that are not supported. The policies might not appear to be disabled in Group Policy but they have no effect:
- Profile streaming
- Always cache
Note: If Offline profile support is enabled, Active write back is honored but can only work when the computer is connected to the network.
The static case
Policy: Offline profile support
For short periods of disconnection, disable the Offline profile support policy. This allows the configuration of any of the following policies.
Policy: Streamed user profile groups
Set the Streamed user profile groups policy to Unconfigured. Enabling this policy is effective only if Profile streaming is also enabled. Streamed user profile groups is used to limit the use of streamed profiles to specific Active Directory user groups. It is useful in some scenarios when migrating from older versions of Profile Management. For instructions on setting this policy, see Stream user profiles.
For information on high availability and disaster recovery as it applies to this policy, see Scenario 4 - The traveling user.
Policy: Timeout for pending area lock files
Set the Timeout for pending area lock files policy to Unconfigured to apply the default operation, which is a one-day timeout for the pending area lock. This is the only supported value, so do not adjust this policy.
Policy: Active write back
For information on this policy, see Persistent or provisioned and dedicated or shared
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.