Binding a user to a specific RDP server in the farm or redirecting user sessions

Question

System administration

The scheme is as follows: they opened an office for 50 people, and 70-80 people will work (the specifics of the work allow), so the jobs are unified, that is, the employee, when he comes to work, sits down in a free place and works (surfing, documents).
For implementation, we decided to use a terminal farm using Microsoft tools. I need that the user, sitting down at the workplace, enters his credentials and gets to his desktop, of course, in a terminal environment, this is the essence of the task. The client part is not in the domain, it is based on a ram image with only an RDP client. While two servers will be used, servers in AD, win2008r2, since there is not enough physical memory, replication of user directories is excluded. That is, I need a single point to connect, while I DO NOT need that, when the RDP1 server is turned off, the sessions are transferred to RDP2, that is, RDBroker is not suitable. To summarize, it is necessary that on the client side all users have identical settings except for the password login, nothing optional or user-changeable, RDP GW also did not fit (maybe of course I’m something, somewhere, missed) the first *tsat pages in Google were viewed. In general, I rarely write questions, but as they say, the deadlines are shaking, so I need help. PS I’ll write right away, this scheme is fully aimed at saving the financial part, so answers like “buy screws, set up replication”, “buy brains”, “buy more chenit” are at least not appropriate, thanks in advance, if I can implement it, I’ll write a post on how to organize such an office from scratch with all the "rakes" (maybe someone will be interested).

Answer 1

It is the broker that solves this issue with spreading users across servers, it should work in a pair of round robin dns (this, however, is described in the setup guides), GW is from a completely different opera.
For user folders, replication is not necessary, it is enough to set up redirection to a network drive and distribute quotas, at the same time this eliminates the need to go to a specific server, and quotas solve space problems.

Answer 2

here's a hitch, you need to use the space on both servers, since there is only half a terabyte there, hmm ... though if there are solutions to combine physical space into one network drive (I never practiced, so I can’t say that I don’t, I’ll google it) if it's not difficult to kinte a link. Thank you. That's what I'll do if I can't find an alternative.

Answer 3

Good afternoon. Did you manage to implement this scheme? I have similar needs: there are a number of virtual machines, it is necessary to make a single entry point and distribute the user to a specific machine. Now everything works with VmWare Horizon. It would be desirable to implement regular means of windows.