Hey everyone! I've cloned a working Windows Server 2019 that has the RDS role using an instant restore from a Veeam backup in a clustered Hyper-V setup. After changing the server's name, MAC address, and IP, I also removed some applications and performed a sysprep. Everything seemed to go smoothly, and I rejoined the domain and reinstalled the necessary apps. However, I'm facing a major issue—whenever I log in with any account, whether it's a domain or local one, I'm always logged in with a temporary profile. This even happens with new local accounts I create. I've already done some troubleshooting like checking NTFS permissions on the user folders, copying the default user profile from another server, cleaning up the registry profile entries, and running various repair tools, but no luck. I'm at my wit's end and considered just reinstalling the server from scratch. Any suggestions?
2 Answers
Honestly, starting from scratch might be your best bet at this point. Just a few questions though: Did you make sure to clean up any old profiles before starting this process? Also, did you remove the server from the domain before running sysprep? It's essential to generalize during sysprep, and I wonder if you removed the RDS role and added it back after the cloning. Those steps can really affect profile creation.
Have you checked the event viewer? The application log can provide insights on why it's generating a temporary profile. It’s crucial for diagnosing the issue.
Yeah, I've looked at it, and I only see events 1511 and 1515. They indicate that temporary profiles are being created, but they don’t explain why.
I think I might not have cleaned up all the profiles before starting. I didn't remove it from the domain before sysprep, but it was definitely not in the domain afterward. I did generalize during sysprep, but I didn't remove the RDS role.