-
-
Fixed issues
-
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!
Fixed issues
Profile Management 2305 contains the following fixed issues compared with Profile Management 2303:
-
Profile containers might fail to load when you enable Profile Management on Azure non-domain-joined VMs. [UPM-4729]
-
Profile Management versions 2209, 2212, and 2303 might cause user profile sync issues, such as failing to populate the Start menu icons. [UPM-4801]
-
Profile containers (VHDX files) might show an Access Denied error message when you upgrade Profile Management from a version earlier than 2009 to version 2009 or later. [UPM-4825]
-
After you upgrade a VDA to 2203 LTSR CU2 with Profile Management enabled, a PowerShell window might pop up for a short amount of time. The issue occurs during the desktop session logon, [UPM-4911]
-
Profile Management might reset the customized Outlook OST path during user logon. [UPM-4914]
-
With the profile container-based Profile Management enabled, a user might have access to the profile files and folders of other users. [UPM-4919]
-
After you upgrade Profile Management from version 2212 to version 2203 LTSR CU1, the profile containers might fail to load. [UPM-4920]
-
When configuring an app access control rule to hide an application from certain computers, in addition to those computers, you must configure at least one OU for the assignments. If not, the rule applies to all OUs—the application is invisible to all computers in your domain.
The same issue occurs when you configure rules to hide an app from certain OUs. In addition to those OUs, you must configure at least one computer for the assignments. If not, the rule applies to all computers—the application is invisible to all computers in your domain. [UPM-4896]
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.