D
D
Dmitry2017-02-03 11:46:56
System administration
Dmitry, 2017-02-03 11:46:56

What causes a terminal session auto-completion of a Windows Server 2008 R2 user?

Good day. Faced another deadlock situation.
Available:

  • terminal farm on Windows Server 2008 R2 with automatic balancing
  • non-roaming user profiles
  • harmful user
  • quotas

The essence of the problem:
This user is thrown out of the session for the second time with the closing of all the programs he has started. A person picks up a solution in a serious program and suddenly throws it out for no apparent reason. Throws out 2 times a month.
What I watched:
  • quotas . Checked and cleaned the user's garbage. Yes, quotas have been exceeded. But I did not find any enabled parameters that allow you to end the session (and in general, are there any?)
  • group policies . Watched everything. Those parameters that introduce any restrictions or even somehow indirectly relate to this situation are simply "not set"
  • remote desktop services . There are no restrictions on session duration, idle time, etc.
  • this user's RDP connection settings . The settings are typical, the same as everyone else

I can’t say anything about other users, because there were no complaints from other users. Help solve the problem, please!

Answer the question

In order to leave comments, you need to log in

2 answer(s)
R
res2001, 2017-02-03
@res2001

Try deleting the profile. After creating a new one, copy everything you need from the old one.
Whether it will help in your case, I don’t know, but other strange problems that appear only for one user managed to win in this way.

M
Maxim Yaroshevich, 2017-08-24
@YMax

Maybe it's a network connection issue? It happened on some users - after putting in order the problem disappears. Just if other users do not have such a problem, then the settings are in order.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question