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 in 2203 LTSR CU4
Compared to: Profile Management 2203 LTSR CU3
Profile Management 2203 LTSR CU4 contains all fixes included in the 2203 LTSR initial release, CU1, CU2, CU3, plus the following, new fixes:
-
The Automatic migration of existing application profiles setting might not work after you upgrade Microsoft Windows 10 version 21H2 to 22H2 or later. [CVADHELP-22510]
-
Deleted profile files might persist in the user store after users log off and log back on to their machines. [CVADHELP-22618]
-
After you upgrade a VDA to 1912 LTSR CU4 or 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. [CVADHELP-22620]
-
The Logon Exclusion Check policy might not work as expected. [CVADHELP-22863]
-
In a scenario where two domains within the same forest have users with the same user name, issues occur when those users log on to the same machine. [CVADHELP-22965]
-
Profile Management might fail to synchronize files whose names have been renamed to a longer path name with profile share. [CVADHELP-22974]
-
With Profile Management 2305 installed, Microsoft Outlook might fail to start with this error message:
C:\Program Files\Citrix\User Profile Manager\upmoutlookhook.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000428.
[CVADHELP-22993]
-
With the Replicate user stores policy enabled, the profiles might not get synchronized with the replicated folder. [CVADHELP-22997]
-
Microsoft Outlook profiles might fail to load when both of the following conditions are met:
- A customized path is configured for Outlook OST files through Group Policy or the registry.
- The customized path contains user environment variables. [CVADHELP-23072]
-
VDAs might experience a fatal exception on upmjit.sys and display a blue screen. [CVADHELP-23296]
-
When you enable the Enable Profile Streaming for Folders option and configure some relative paths to the user profile as the Profile Streaming Exclusion list - directories setting, the files under these relative paths might not work as expected after successful login. [CVADHELP-23411]
-
You might experience a longer logon duration while loading user sessions. [CVADHELP-23482]
-
When the Profile streaming policy is enabled, accessing or fetching files contained in a profile from the user store might fail with the following error message:
The file cannot be accessed by the system.
[CVADHELP-23561]
-
After upgrading a VDA to version 1912 LTSR CU8, user profiles might fail to load from the store. Instead, users are provided with local profiles. [CVADHELP-23877]
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.