We are running FSLogix 2.9.8884.27471 on Server 2022.  Our domain controllers are all Server 2022.  We just migrated to a new file server.  The Citrix profiles are stored on a completely different server; we have not changed the Citrix profile file server.  We only changed/migrated the general file server used for general file storage.

After we powered off the old file server, Citrix users complained of “slowness” when using File Explorer.  We discovered that there are a bunch of references to the old file server in each user’s FSLogix profile registry.  If we mount the FSLogix profile, when a user is logged out, and delete the references from a user’s profile registry, the “slowness” issues with File Explorer, are resolved.  The registry entries that seem to be present in each user’s profile are located in the following:

HKUFSL.VHD.****SoftwareMicrosoftWindowsCurrentVersionExplorerMountPoints 2 (there are a couple mount points still present for the old file server) 

HKUFSL.VHD.****SoftwareMicrosoftWindowsCurrentVersionExplorerShell Folders (we use GPO to redirect a users “Favorites” folder – the old file server is still listed in the “Favorites” registry entry, even though the GPO is setup to point to the new file server)

HKUFSL.VHD.****SoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders (we use GPO to redirect a users “Favorites” folder – the old file server is still listed in the “Favorites” registry entry, even though the GPO is setup to point to the new file server)

When we delete the “Favorites” entries, we find that after a user logs in/out, the “Favorites” entry updates properly to the new file server path.

We can also remedy the File Explorer “slowness” by simply powering on the old file server.  Again, all of the sharing on the old file server has been disabled.  So it seems like as long as a user can “ping” the old file server, then that’s all FSLogix needs to ensure that File Explorer works.

This issue does not occur on physical Windows computers/servers- only with with FSLogix profiles.

Instead of either leaving on the old file server powered on, or manually editing the registry in each user’s profile, is there a way to remove (or update) these registry entries that point to the old file server?

​We are running FSLogix 2.9.8884.27471 on Server 2022.  Our domain controllers are all Server 2022.  We just migrated to a new file server.  The Citrix profiles are stored on a completely different server; we have not changed the Citrix profile file server.  We only changed/migrated the general file server used for general file storage. After we powered off the old file server, Citrix users complained of “slowness” when using File Explorer.  We discovered that there are a bunch of references to the old file server in each user’s FSLogix profile registry.  If we mount the FSLogix profile, when a user is logged out, and delete the references from a user’s profile registry, the “slowness” issues with File Explorer, are resolved.  The registry entries that seem to be present in each user’s profile are located in the following: HKUFSL.VHD.****SoftwareMicrosoftWindowsCurrentVersionExplorerMountPoints 2 (there are a couple mount points still present for the old file server)  HKUFSL.VHD.****SoftwareMicrosoftWindowsCurrentVersionExplorerShell Folders (we use GPO to redirect a users “Favorites” folder – the old file server is still listed in the “Favorites” registry entry, even though the GPO is setup to point to the new file server) HKUFSL.VHD.****SoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders (we use GPO to redirect a users “Favorites” folder – the old file server is still listed in the “Favorites” registry entry, even though the GPO is setup to point to the new file server) When we delete the “Favorites” entries, we find that after a user logs in/out, the “Favorites” entry updates properly to the new file server path. We can also remedy the File Explorer “slowness” by simply powering on the old file server.  Again, all of the sharing on the old file server has been disabled.  So it seems like as long as a user can “ping” the old file server, then that’s all FSLogix needs to ensure that File Explorer works. This issue does not occur on physical Windows computers/servers- only with with FSLogix profiles. Instead of either leaving on the old file server powered on, or manually editing the registry in each user’s profile, is there a way to remove (or update) these registry entries that point to the old file server?     Read More

​