Temporary profile on remote desktop server

Question

We have 6 RD Servers (2012 and 2008) and on all of them users sometimes get assigned a temporary profile. In Eventlog we can always see Event ID 1600 Das Profil kann nicht von \<domain>\files\RD_Profiles<user> nach C:\Users<user> kopiert werden. Es steht nicht genügend Speicherplatz auf dem Datenträger zur Verfügung. my english translation: profile could not be copied from \<domain>\files\RD_Profiles<user> to C:\Users<user>. There is not enough disk space available. The weird thing is that we have more than enough space left (around 100GB on each RDS and about 1TB on the fileserver). And the problem does not always occur, for example today 3 users had this problem (out of ~100). Any suggestions?

Answer 1

HI , There can be many reasons for the temp profile ,to mitigate this ,check the below path in Registry on the affected servers

if there are values with .bak entries , those are temp profiles . Delete these and users will be able to log on normally Also , manually delete any temporary profiles located in c:\users
You can avoid the issue by creating an automatic script using a scheduled task. Or set GPO policy to log off disconnected sessions after X minutes. Additionally, ensure all user sessions are logged off and do not allow new connections to hosts before performing maintenance and/or restarts If the above is useful , please mark this as Accept Answer

Answer 2

Hi, I'd be happy to help you out with your question. Sorry for the inconvenience caused. I know This can be frustrating, but I'll do my best to help you troubleshoot the issue. Firstly, it's important to understand that temporary profiles are usually created when there is an issue with the user profile, such as the profile files being locked or inaccessible. To narrow down the root cause of the problem, there are a few things you can try: Check the size of the affected user profiles - Large user profiles can sometimes cause the profile copy to fail. You can check the size of the user profiles by navigating to the user profile folder on the file server and sorting the folders by size. Check the permissions on the user profile folder - Make sure that the user has sufficient permissions to access and modify the profile folder. Check the event logs for other errors - Look for any other errors or warnings in the event logs that might be related to the user profile issue. For example, there might be errors related to the profile hive being locked or inaccessible. Try deleting and recreating the affected user profiles - If the issue persists, you can try deleting the affected user profiles and letting the system recreate them. This might help identify any corrupt profile files or settings that are causing the issue. Consider using roaming profiles - Roaming profiles allow users to access their profile settings from any computer on the network. This could help eliminate the issue of user profiles being created or copied locally on the RD servers. By investigating the root cause of the issue and taking steps to address it, you can prevent users from being assigned temporary profiles in the future. If you have any other questions or need assistance with anything, please don't hesitate to let me know. I'm here to help.

If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

Answer 3

Hello, from what I saw so far users that have big profiles (around 2GB) have the problem more often. But still the tricky part is that they do not experience that problem all the time. a user can have the problem, I check it for them on the server and see all the usual ID 1600 when they logged on and confirm that they have a 2BG profile. But as soon as I delete their profile on the server and have them log on again, I see no issue anymore. no errors and everything works fine. until some days later when it all repeats. I suspected some weird stuff with roaming appdata going on, that after some time, after the users do something that weird windows does not like. that the server then has problems to copy the profile. But wouldn't we then see other errors and IDs (not sufficient rights or something like that)? but it is always ID 1600 with the not enough space, even when we have plently of disk space.

Answer 4

Hello, administering Windows Server 2022, that is a member of Active Directory, I am facing similar problem. Symptoms are Audit Failure event logs in Security with Return Code 0x8000900024, e.g.

Log Name:      Security 
Source:        Microsoft-Windows-Security-Auditing  
Date:          09.05.2024 10:27:58  
Event ID:      5061  
Task Category: System Integrity  
Level:         Information  
Keywords:      Audit Failure  
User:          N/A  
Computer:      comuter.domain.com  
Description:   Cryptographic operation.  
Subject:  	
  Security ID:		DOMAIN\firstname.surname  	
  Account Name:		firstname.surname  	
  Account Domain:		DOMAIN  	
  Logon ID:		0x1C9E36C2  
Cryptographic Parameters:  	
  Provider Name:	Microsoft Software Key Storage Provider  	
  Algorithm Name:	UNKNOWN  	
  Key Name:	Microsoft Connected Devices Platform device certificate  	
  Key Type:	User key.  
Cryptographic Operation:  	
  Operation:	Open Key.  	
  Return Code:	0x80090024

The temporary profile issue causes the user folder are created as C:\Users\TEMP, C:\Users\TEMP.<domain>, etc. for affected users, being deleted as soon as user signs out (as expected).

In registry key Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-<profile_ID> I can see DWORD value

CentralProfile = \\server\Profiles$\firstname.surname\Profile.V6

for affected users when they are currently signed in.

Only 3 users of 130 are affected, their user profiles in Active Directory are equipped with roaming user profile as shown above. It's setting derived from local ADC in the locality where the users work. For a test user without roaming profile, even in the same locality, there was no problem with the temporary profile. So the roaming profile causes the issue with the temporary profile.

I don't currently know a solution for this issue, but my post may help other administrators determine the cause of the problem.

If you have any ideas what to do to make my terminal server Win Server 2022 to accept user roaming profiles, please tell me.

Regards

Leoš