HI
1.Could you please enter winver in command prompt on Fslogix applied win10 computer and terminal server then look the os version and os version number ?[for example windows 10 enterprise 1809 (os build 17763.316)]
2.Where do you store profile?
Are both FSlogix profile applied server and FSlogix profile storage server in the same AD domain and in the same network segment?
3.Please check if we deploy below policies on all RDS session host servers.
We can create a temp folder in disk C and enter below command on all rds servers to check if we have configure them. These policies will prevent temporary profiles issues happen again after we delete temp profile.
gpresult /h c:\temp\rds.html
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
Restrict Remote Desktop Services user to a single Remote Desktop Services session set to Enabled
Configuring RDP/RDS Sessions Limits (Timeouts) on Windows(Set GPO policy to log off disconnected sessions after X minutes)
http://woshub.com/remote-desktop-session-time-limit/
4.The problem occurs when the user session state is disconnected. Although the user is not connected their sessions, their sessions continue to run in the server background. Therefore their Fslogix profile remains attached to the RDS server. Users will receive temporary profiles if their Fslogix was attached to the RDS server when it was restarted.
How to fix temporary profile issues:
Let all users log off the server. Do not allow users to log on while troubleshooting.
Attempt to delete the temporary profile from Advanced System Properties:
Go to Control Panel → System → Advanced System Properties → Advanced → User Profiles → Settings.
Delete any profiles with Type set as TEMP.
Delete any temporary use profiles from the ProfileList in Regedit.
Open Regedit:
HKLM\SOFTWARE\Microsoft\Windows NT\Current Version\ProfileList
Profiles are listed using objectSIDs, for example:
S-1-5-21-1343024091-200047854-725345543-5879
we need to delete it.
Identify and rename any objectSIDs that have a .bak suffix, these objectSIDs need to reserved for end users.
for example:
rename S-1-5-21-1343024091-200047854-725345543-5879.bak to S-1-5-82-3848493281-17249319953-1783664087-774473773-2625933694
each object SID profile has an expandable string value called ProfileImagePath. Use this string value to easily identify individual users, for example:
Value Name: ProfileImagePath
Value Data: C:\Users\u1
Finally, manually delete any temporary profiles located in c:\users\, for example:
TEMP.Domain.000
TEMP.Backup-0
[Easy] How to fix Temporary Profile in Microsoft Windows and Microsoft Server
https://www.itsmdaily.com/easy-how-to-fix-temporary-profile-in-microsoft-windows-and-microsoft-server/
Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice.
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.