Aggiornamento anche per Citrix Profile Management, che “salta” dalla 3.2.2 alla versione 4.

Molti i problemi risolti in questa release, vediamo insieme quali:

1. After upgrading to Version 3.1.1 of Profile management, users cannot launch certain applications when the Profile Streaming feature of Profile management is enabled along with Trend Micro antivirus software.
2. Changes to the NTUSER.DAT file fail to be saved because Profile management does not synchronize the NTUSER.DAT file to the user store.
3. Extended synchronization file modifications are not properly written to the user store when active write back is enabled.
4. Profile changes made during a session that exceeds five hours are not synchronized to the user store when the user logs off if, at any time during the session, the workstation is locked.
5. Attempts to move (as opposed to copy and paste) content between extended synchronization and profile folders do not succeed.
6. This feature enhancement permits multiple uses of the same Active Directory variable in the “Path to User Store” policy.
7. When the “Delete Local Cache on Log Off” policy is enabled, the following registry keys fail to be deleted from the user device at logoff:
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\{SID} [of the user logging off]
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\Status\{SID} [of the user logging off]
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\{SID} [of the user logging off]
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IdentityStore\Cache\{SID} [of the user logging off]
8. Windows Server 2003 Service Pack 2 changed the Windows profile naming convention to a %USERNAME%.%DOMAIN% format. Profile management is looking for the user profile using the convention of %USERNAME%, thus cannot locate the profile. With this fix, Profile management properly resolves to the proper profile even when its present in %USERNAME%.%DOMAIN% format.
9. An occasional corruption of the the UserProfileManager_C.cache file can render UserProfileManager.exe and ultimately the virtual machine unresponsive, and logon attempts fail.
10. On occasion, users can get a temporary profile instead of the actual profile.
11. The “Process Internet Cookie files on Logoff” feature might not work properly intermittently.
12. During times of heavy logon activity, a deadlock in Profile management can cause XenApp 6 servers to disconnect sessions and to refuse to accept new sessions as well as reconnection attempts.
13. Attempts by local administrators to log on to an endpoint running Windows XP or Windows Server 2003 can fail even if the “Process logons of local administrators” policy is enabled, and the following error message appears in UserProfileManager.log:“SetPrivilege: Could not disable privilege SeTcbPrivilege: Access is denied.”
14. Servers can become unresponsive and require a restart due to synchronization issues during logon, logoff and active writebacks.