Hi,
we are getting more and more logon errors from users using a new rds environment that they are unable to log in because the RDS are busy. Even if the server only has 2 Users connected. Yesterday I also got stuck logging in via teamviewer. In the tesk manager I see several logged on users without a name that are probably stuck loggin on and I cannot log them off.
I was able to get some precise feedback from users and I think everytime they are logging in, they trigger an event 69 where it says that the ntuser.dat on the local RDS-server is newer than the one wintin the roaming profile.
Here are some details about the environment:
site1 - datacenter:
- RDS-Servers
- local DC
- local fileserver
site 2 - Office:
- local DC
- local file server
- clients connecting via mstsc
The sites are connected via a site 2 site vpn. The filers sync via dfs. Roaming roaming profiles are stored on the filers. In AD the default profile folders point to filer one and in the datacenter they are being changed via GPO to the local filer in the datacenter.
Some of the applications that used to live in the old terminal server farm in site 2 are being shared as remote apps since they havent been migrated yet.
I am fairly certain that the situations stem from the user profiles, but how do I resolve this?
Thanks in advance and have a good one
Fabian