Product Documentation

Fixed issues

May 22, 2017

Profile Management 5.8

Compared to: Profile Management 5.7

Profile Management 5.8 contains all fixes that were included in Profile Management 5.7, 5.6, 5.5, 5.4.1, 5.4, 5.2.1, 5.2, 5.1.1, 5.1 and 5.0 plus the following, new fixes:

  • Occasionally, the user logon screen becomes unresponsive on Windows Server 2012 R2.

    [#LC6149]

  • With Active write back enabled, occasionally profile changes cannot be written back.

    [#LC6954]
  • Profile Management fails to synchronize offline files back to the user store.

    [#LC7843]
  • Enabling both the Offline profile support policy on a VDA and the Delete locally cached profiles on logoff policy simultaneously can cause a new local profile to be created at each logon.

    [#LC7844]

  • Querying session information by using Profile Management WMI cmdlets doesn't display the correct profile type if the profile is loaded as a temporary profile or a mandatory profile. 

    [#LC7846]
  • Occasionally, file type associations (FTA) fails to roam with Profile Management on Windows 10 and Windows Server 2016.

    [#LC7847]
  • The default browser fails to roam with Profile Management 5.7 on Windows 10 and Windows Server 2016.

    [#LC7848]

Profile Management 5.7

Compared to: Profile Management 5.6

Profile Management 5.7 contains all fixes that were included in Profile Management 5.6, 5.5, 5.4.1, 5.4, 5.2.1, 5.2, 5.1.1, 5.1 and 5.0 plus the following, new fixes:

  • With Fix #LC3532 installed, occasionally, when you try to open files in a profile, the file appears empty.

    [#LC5943]
  • Attempts to migrate Windows roaming profiles to Profile Management profiles fail on Windows might fail on Windows 8.1 and Windows 2012R2 unless the UseProfilePathExtensionVersion registry key is set.

    [#LC6150]
  • With Active write back enabled, logging on, deleting a key in the HKEY CURRENT USER hive, and creating a new key with the same name before the change is written back to the user store causes the new key to fail to be backed up to the user store.

    [#UPM-31]
  • Attempts to copy files and directories in an exclusion list from the user store to the local profile at user logon fail.

    [#UPM-39]
  • With the Delete local cache at logoff policy enabled on Windows 10 or Windows 2016, the NTUSER.DAT file might fail to be deleted at logoff, causing another local profile to be created at the next logon.

    [#UPM-96]
  • HDX policies (such as “Number of retries when accessing locked files”) can accept out-of-range and therefore invalid integer values.

    [#UPM-170]
  • If you log off and back on to the session after clicking “Reset Profile” in Citrix Director for that session, the new profile cannot be loaded.

    [#UPM-188][ [#658534]
  • If the template profile path is set as a local path, a temporary profile is created when a user logs on.

    [#UPM-189][#454122]
  • A lack of write permissions on the log file can cause Profile Management's memory consumption to spike.

    [#UPM-200]

Profile Management 5.6

Compared to: Profile Management 5.5

Profile Management 5.6 contains all fixes that were included in Profile Management 5.0, 5.1, 5.1.1, 5.2, 5.2.1, 5.4, 5.4.1, and 5.5 plus the following, new fixes:

  • On Windows 8.1, attempts to download files using Internet Explorer 11 fail if Enhanced Protected Mode is enabled.

    [#LC3464]

  • When attempting to log on to a XenApp 7.7 server using RDP, the server might become unresponsive on the welcome screen.

    [#LC5169]

  • Locally cached profiles might not delete when users log off.

    [#LC5470]

  • When the license server is offline, files using the user redirection folder on the server are lost.

    [#LC5595]

  • Users' files are lost when the license trial period ends without renewal.

    [#LC5775]

  • The application icons might appear as grayed out when you attempt to copy the icons from the Profile Management user profile store through a WAN connection.

    [#LC6152]

Profile Management 5.5

Compared to: Profile Management 5.4.1

Profile Management 5.5 contains all fixes that were included in Profile Management 5.0, 5.1, 5.1.1, 5.2, 5.2.1, and 5.4, 5.4.1, plus the following, new fixes:

  • File locks can occur in Profile Management during the logoff process with the following error message:

    "The process cannot access the file because it is being locked by another process."

    Attempts to delete files locked by Profile Management might fail until the locks are released.

    [#LC3532]

  • XenApp servers might become unresponsive in the farm until the server is restarted.

    [#LC4318]

  • After upgrading the VDA from Version 7.6.1000 or earlier to Version 7.7 or later, attempts to delete, repair, or reinstall Profile Management or the VDA might fail.

    [#LC5207]

  • Profile Management occasionally locks files in user profiles. When this happens, users receive a temporary profile while trying to reconnect while the files are locked.

    [#LC5278]

Profile Management 5.4.1

Compared to: Profile Management 5.4

Profile Management 5.4.1 contains all fixes that were included in Profile Management 5.0, 5.1, 5.1.1, 5.2, 5.2.1, and 5.4, plus the following, new fixes:

  • Some values under this registry key might not be updated correctly, such as article number: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\XenDesktop\Hotfixes.

    [#LC1962]

  • Profile Management 4.1.5 copies users' roaming profiles even when the roaming policy is disabled.

    [#LC3233]

  • On Windows 8.1, attempts to download files using Internet Explorer 11 fail if Enhanced Protected Mode is enabled.

    [#LC3464]

  • File locks can occur in Profile Management during the logoff process with the following error message:

    "The process cannot access the file because it is being locked by another process."

    Attempts to delete files locked by Profile Management might fail until the locks are released.

    [#LC3532]

  • When logging off, Profile Management occasionally locks files/folders on the server, causing applications to fail to launch. Locally cached profiles also do not get deleted.

    [#LC5266]

Profile Management 5.4

Compared to: Profile Management 5.2.1

Profile Management 5.4 contains all fixes that were included in Profile Management 5.0, 5.1, 5.1.1, 5.2, and 5.2.1, plus the following, new fixes:

  • Attempts by certain third party applications to rename or move files during logon or logoff might fail. For example, if there are files file0, file1, and file2 in the local profile, attempts to rename file2 to file3, file1 to file2, and file0 to file1 might fail during the logoff process if file2 already exists on the pending area or user store.

    [#LC0465]

  • When users log off, the Profile Management (UserProfileManager.exe) service occasionally fails.

    [#LC0625]

  • The "LOGON DURATION" panel in the Performance Monitor (Perfmon) counter might record the data for user logons that are not managed by the User Profile Manager (UPM).

    [#LC0779]

  • The User Profile Manager (UPM) might not synchronize the files with the user store after a certain period of time.

    [#LC1338]

  • After enabling the following logging options, no debugging information is recorded in the log file:

    • Policy: Active Directory actions
    • Policy: Policy values at logon and logoff
    • Policy: Registry difference at logoff
       

    [#LC2003]

  • If a user enables Profile Versioning as described in https://support.microsoft.com/en-us/kb/2890783, the User Profile Manager (UPM) might not migrate for the following reasons:

    • The Microsoft roaming profile is created with the extension "V4"
    • The UPM profile was not migrated and created from the "Default user" template.
       

    [#LC2427]

  • After resetting the user profile in Desktop Director, folder redirection does not work when users log on for the first time. Folder redirection does work when users subsequently log on.

    [#LC2602]

  • The Profile Management (UserProfileManager.exe) service might close unexpectedly.

    [#LC2979]

  • After applying Fix #LC0625, the Profile Management (UserProfileManager.exe) service might close unexpectedly.

    [#LC3058]

  • Profile Management can exit unexpectedly while the user device is in the process of shutting down.

    [#LC3626]

  • With Profile Management enabled, Microsoft applications delivered by Microsoft App-V open the first time a user logs on but fail at subsequent logons with the following error message:

    "The Application failed to launch. This may be due to a network failure.

    Error code: 0x4FC09004-0000002C"

    [#349636]

  • When migrating Windows 10 roaming profiles to Citrix roaming profiles, Profile Management resolves the roaming profile path to V2. However, Windows 10 uses V5 as the profile suffix and, as a result, the existing roaming profile cannot be found and a new Citrix profile is created in the user store.

    [#565586]

  • When restarting a user device, the Start menu, taskbar, and Search are unresponsive.

    [#586345]

Profile Management 5.2.1

Compared to: Profile Management 5.2

Profile Management 5.2.1 contains all fixes that were included in Profile Management 5.0, 5.1, and 5.2, plus the following, new fixes:

  • Attempts by certain third party applications to rename or move files during logon or logoff might fail. For example, if there are files file0, file1, and file2 in the local profile, attempts to rename file2 to file3, file1 to file2, and file0 to file1 might fail during the logoff process if file2 already exists on the pending area or user store.

    [#LC0465]

  • When users log off, the Profile Management (UserProfileManager.exe) service occasionally fails.

    [#LC0625]

Profile Management 5.2

Compared to: Profile Management 5.1

Profile Management 5.2 contains all fixes that were included in Profile Management 5.0 and 5.1, plus the following, new fixes:

  • This fix adjusts permissions on some registry keys that are necessary when creating new profiles from a default Windows profile.

    [#LA3724]

  • With this enhancement, Profile Management can copy local profiles to the user store even if the profiles are referenced using relative paths, such as ..\UPM.

    [#LA4696]

  • This fix addresses the following issues:

    • File downloads fail in Internet Explorer when protected mode and UAC are enabled.
    • Profile Management sets write-only permissions on HKEY_CURRENT_USER\Software\Policies.
       

    [#LA4764]

  • Attempts to download files using Versions 9, 10, and 11 of Microsoft Internet Explorer might fail if protected mode and UAC are enabled.

    [#LA4814]

  • Some applications are having unexpected behaviors because the AppData\Local\Microsoft\Windows\WinX and AppData\LocalLow\Sun\Java folders are not available on user's profile. The following error message appears when attempting to launch those applications:

    "explorer.exe
    Windows cannot access the specified device, path or file . You may not have the appropriate permissions to access this item."

    This fix addresses the issue for new created profiles. It does not address it for existing profiles. For existing profiles, copy the local settings folder contents (from template/local default profile) manually.

    [#LA5103]

  • When the mandatory profile is set, Profile Management logs the following error 2003 in the server Event Viewer:

    "The system cannot find the path specified."

    [#LA5212]

  • With this fix, Internet Explorer 10 and later running in Protected Mode can now utilize the browser local store to persist cached data.

    [#LA5478]

  • With offline support enabled, the following error message can appear after restarting the user device:

    "Windows could not connect to the System Event Notification Service service."

    [#LA5763]

  • UserProfileManager.exe can exit unexpectedly and the following error is appears in the Event Log:

    Event ID 7031 - "The Citrix Profile Management service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service."

    [#LC0169]

  • This fix ensures that setting exclusion rules using wildcards, such as \*.tmp or \*.txt, actually excludes those file types from the parent user profile directory (but not from any subfolders) as documented at http://docs.citrix.com/en-us/profile-management/5/upm-tuning-den/upm-include-task-den.html.

    [#LC0217]

  • Profile Management cannot create profiles on a NetApp filer 2.1.

    [#LC0423]

  • This fix ensures that setting exclusion rules using wildcards, such as *.tmp or *.txt, actually excludes those file types from the entire user profile directory (parent folder and all subfolders of the user profile), as documented at http://docs.citrix.com/en-us/profile-management/5/upm-tuning-den/upm-include-task-den.html.

    [#LC0178]

Profile Management 5.1.1

Compared to: Profile Management 5.1

Profile Management 5.1 contains all fixes that were included in Profile Management 5.0 and 5.1, plus the following, new fixes:

  • File downloads fail in Internet Explorer when Protected Mode and User Access Control (UAC) are enabled. Additionally, Profile Management sets write-only permissions on HKEY_CURRENT_USER\Software\Policies.

    [#LA4764]

  • Attempts to download files using Versions 9, 10, and 11 of Microsoft Internet Explorer fail if Protected Mode and UAC are enabled. A fix to address this issue on Windows Server 2012 R2 is not currently available.

    [#LA4814]

  • In Internet Explorer 10 and later running in Protected Mode, cached data in the local store is not persisted.

    [#LA5478]

Profile Management 5.1

Compared to: Profile Management 5.0

Profile Management 5.1 contains all fixes that were included in Profile Management 5.0, plus the following, new fixes:

  • Director does display a session count increase when a hosted application is launched. However, the "Average Logon Duration" panel might fail to display the session duration and the corresponding entry in the graph.

    [#386860]

  • A folder that is moved from a non-monitored area to a monitored area might not persist after logging off and back on.

    [#394798]

  • Windows Server 2012 might experience a fatal exception, displaying a blue screen while unloading and reloading a filter driver.

    [#395123]

  • Using Profile Management along with third-party folder redirection software can cause the Director "Personalization" panel on the "User Details" page to return an error.

    [#404309]

  • There can be an incorrect file version format while installing the profilemgt_x86/_x64.msi package: The third field in the version of the product is not a "0."

    With this fix, the product version is:

    <major>.<minor>.0.<build number> when installing the base package.

    [#407473]

Profile Management 5.0

Compared to: Citrix Profile Management 4.1

Profile Management 5.0 contains the following fixes compared to Profile Management 4.1:

  • Applications can become unresponsive without logging any error messages when the cachefill mechanism conflicts with anti-virus software settings. This enhancement adds an Event Viewer message indicating the problem.

    [#235486]

  • When Profile Management is installed on the terminal servers, Wbemtest.exe reports new user objects. However, when users log off, the report is not updated and user objects remain on the root\rsop\user namespace. With this fix, Wbemtest does not show a namespace for the user after logoff if Delete local profile during logoff is enabled.

    [#235532]

  • 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.

    [#236518]

  • Changes to the NTUSER.DAT file fail to be saved because Profile Management does not synchronize the NTUSER.DAT file to the user store.

    [#241476]

  • 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.

    [#246507]

  • This feature enhancement permits multiple uses of the same Active Directory variable in the "Path to User Store" policy.

    [#253039]

  • 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]
       

    [#255860]

  • 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.

    [#257005]

  • On occasion, users can get a temporary profile instead of the actual profile.

    [#259149]

  • The "Process Internet Cookie files on Logoff" feature might not work properly intermittently.

    [#259398]

  • 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.

    [#259620]

  • With the user store hosted on a NetApp share, profiles can intermittently fail to load.

    [#LA0979]

  • Folders that are excluded from being synchronized can be deleted upon the next time the users logs on.

    [#LA1015]

  • User settings might not get saved when a relative path name is configured for the store location.

    [#LA1340]

  • Internet Explorer can become unresponsive when the user tries to open a URL that was compiled from a user store folder to the equivalent local profile folder.

    [#LA1387]

  • This fix corrects an issue that prevents profiles from being deleted when users log off.

    [#LA1424]

  • With the "Delete locally cached profiles on logoff" option enabled, stale profile folders are left behind after a user logs off.

    With this fix:

    • The profile folder is deleted two to three minutes after the user logs off.
    • The profile folder persists if the user logs off and back on.
    • If the profile folder is locked by any other process during logoff, it does not result in an error. After the process is completed, the profile folder is deleted. If the folder is still locked while the same user logs back on, a new profile folder .x (x increments by 1 if the current user profile folder is locked) is created. The stale profile folder is deleted in the background.
       

    [#LA1680]

  • When using Microsoft's System Preparation Tool (Sysprep.exe) as described in Microsoft article Microsoft article 973289 and setting CopyProfile=true causes the default profile of the operating system to be unusable for Profile Management.

    [#LA1681]

  • With this feature enhancement, users logged on with temporary profiles receive the following message and are logged of after clicking OK:

    "There was a problem setting up your profile.
    You will be logged off when you click OK, and changes you make during this session will not be saved.
    Please contact your administrator to resolve this problem."

    To enable this functionality, enable the "Log user off if a problem is encountered" policy under Profile Management > Advanced Settings.

    [#LA1879]

  • The migration of Windows roaming user profiles to Citrix profiles fails for Windows roaming files configured using a GPO.

    [#LA1898]

  • In certain configurations, after modifying a file on client device A, logging off, and then logging on to client device B, the previous version of the file is deleted from device B without synchronizing the updated version to device B. Only after logging off from device B and then logging back on will the updated file be present on device B.

    [#LA2233]

  • Profile Management can exit unexpectedly while parsing some registry keys.

    [#LA2779]