temp profile in AVD

Question

Hi,

Whenever I log in, it creates a temporary profile. As a workaround, to fix this, I need to recreate a fresh profile by deleting the existing one, since we are using FSLogix, and the profiles are stored in Azure File Share. However, by creating a new profile, the user loses the data saved in the previous profile.

Is there any way to retrieve the data or load the previous profile stored as a VHD in an Azure File Share ?

Although it is the user's responsibility to sign out correctly from their sessions to prevent stale sessions, a policy is already in place that will automatically log off the user if they simply disconnect. Therefore, I don't believe that improper sign-out by the user will cause the issue.

FSLogix logs show the reason code: 7 (REASON_WINDOWS_TEMP_PROFILE).

also checked the article below, but nothing there seems to apply to this issue: FSLogix Troubleshooting - Old Temp or Local Profiles.

why this happens ? Is there a permanent fix for this?

Answer 1

Hi @$@chin,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

At first, I would recommend eliminate creating temporary profile. Sometimes if the User account gets corrupted and cannot start, Windows will sign into a temporary account. A Temp Account cannot be used as a normal account so do not set it up or copy files into it because at any restart it might decide to start into your old Account.

Temporary profiles are deleted at the end of each session, and changes made by the user to their desktop settings and files are lost when the user logs off.

Also, Domain Controller AD DS for GPOs at login, if the client can't reach the domain controller, it will set up a temporary profile.

To help with your query there is frx.exe on every computer where FSLogix app was installed - "C:\Program Files\FSLogix\Apps\frx.exe". It easy to copy local profile to vhd, but user mustn't be logged in.

"C:\Program Files\FSLogix\Apps\frx.exe" copy-profile -filename \server\UserProfile\profile.vhdx -username mydomain\tes.user -dynamic 1 -verbose

If you have any further queries, do let us know.

Answer 2

Hi $@chin,

Thank you for posting in the Q&A Forums.

Check the network connection:

Ensure that the network connection for Azure File Sharing is stable and that clients can access it properly.

Check any security groups, firewall rules, or network policies that may affect network connectivity.

Verify FSLogix configuration:

Check the FSLogix configuration settings to ensure that they are correctly pointing to the correct location in the Azure file share.

Verify that the FSLogix Agent is properly installed and running on the client computer.

Check the Azure file share:

Log in to the Azure portal and check the status and properties of the file share.

Ensure that the file share has sufficient storage space and is not set to read-only or otherwise restricted.

Recover lost configuration files:

If possible, try to recover the lost profile from the Azure file share. This may involve locating the old VHD file or restoring it using a backup.

Note: Before restoring, make sure to close all sessions that may be using the profile.

Remount the configuration file:

If the configuration file has been unmounted or corrupted for some reason, try remounting it.

This may require logging back in or using the FSLogix Admin tool to manually mount the profile.

Update FSLogix and clients:

Ensure that the FSLogix Agent and all associated clients are up to date.

Sometimes software updates can address known issues and vulnerabilities.

Review FSLogix logs:

Drill down and analyze the FSLogix log files for more detailed information about why the configuration file could not be loaded.

This may involve looking for specific error codes or warning messages.

Best regards

NeuviJ

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.