Troubleshoot FSLogix Profile Mount Errors

Troubleshoot FSLogix Profile Mount Errors

If a user receives "The user profile failed to attach" FSLogix error when logging in, follow these troubleshooting steps:

  • Ensure the FSLogix services are running on the AVD session host or dedicated AVD instance.

  • Ensure your storage for FSLogix profile containers has available storage.

Manually Troubleshoot File Share Permissions

Using a session host, you can also attempt to troubleshoot possible File Share permissions issues. This is useful if you didn't use Nerdio Manager to create the file share, are using NetApp Files, or a self-managed File Server.

To manually troubleshoot File Share permissions:

  1. Connect to the desktop using the standalone AVD Remote Desktop Client in a full-screen session and wait until you see the error message.

  2. Press CTRL+SHIFT+ESC to open the Task Manager.

  3. Navigate to File > Run new task.

  4. Type explorer.exe and select OK.

  5. Browse to the UNC specified in the Nerdio ManagerSettings > Integrations page under the FSLogix file storage configuration. This is the file share path where the profiles are stored, also known as "VHDLocations."

  6. If you are able to browse to the path, try creating a folder in that location. If unable to, then Share or NTFS permissions are incorrectly set.

    • Set Share permissions to Everyone or Authenticated Users - Full Control.

    • Set NTFS permissions per Microsoft guidance. See this Microsoft document for details.

  7. If you are not able to browse to the path, then either the path, name resolution, or networking is incorrectly specified.

    • Verify that you can browse to the path from another computer.

    • Navigate to Task Manager > File> Run new task.

      • Type cmd.exe and select OK.

      • NSLookup or ping the host name and make sure it resolves and replies.

        Note: Azure Files storage accounts do not respond to ICMP. This is okay.

  8. If you are able to browse the path and create a file or folder, then verify that the user's profile VHD(X) file isn't locked by another session. By default, FSLogix profiles are configured to be exclusively locked by the first session that mounts the profile. If the user is actively connected to another host pool, then the profile is already locked. Concurrent access to profiles is supported by FSLogix but there are trade-offs to consider. See this Microsoft document for details.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Please sign in to leave a comment.