How would you plan for a terminal server?

Question

Windows

Good afternoon, dear experts!
A few years ago, I came to work in a small, rapidly growing trading company. The staff was small, about 8 people. On the computer of the chief accountant, in a shared folder, there were 1C bases. The company grew, the staff increased, and productivity fell. My first decision at a new place of work was to buy a server to organize a remote desktop service on it. No sooner said than done! Bought Fujitsu tower server. Tower because the office was small and there was simply nowhere to put the rack, they bought the tower, put it next to the gateway, set up the network, launched it, and are working.
Time went on, the staff grew and grew, regional offices appeared, and the performance of file 1C fell again. It was decided to purchase another server to organize a cluster of 1C servers on it. We bought a server, this time a rack-mount one. The office moved to a more or less normal room with a closet for a server room. We set up a rack, installed an old terminal server and a newly acquired database server into it, and deployed a 1C + MS SQL server on it.
Now the question arose about colocation in the data center. The price tag for placing a tower server (4U) cannot be called humane. From here the idea arose to replace the old tower with a rack-mount one. Put VMware on it and deploy 2 servers. One terminal, and the second Active Directory domain controller.
The following config is assumed for +-100 users:
CPU - 2x Xeon x5660 (6x2.8 GHz)
RAM - 64 Gb (expandable)
HDD - 4x1 Tb
SSD - 1x265 Gb
How to share resources between two VMs?
How much RAM is needed for the comfortable work of users of the vehicle (Google Chrome, MS Office, 1C)?
And probably the most important question: how to properly organize a backup of all this joy?

Answer 1

1 - it is impossible to give an exact answer without knowing the features
2 - are there usb 1C keys? consider Hyper-V, I recommend. this edition of the server is free, the only negative is that there is no usb forwarding, but dynamic memory allocation. If you know how to put keys on another computer (maybe an old tower?) And rummage around the network - Hyper-V is the best choice for hosting Windows virtual machines. disks will have to be distributed by eye, but this is not difficult if you do not try to hang an office file dump there (it is desirable to keep it separately). in any case, all this must be monitored, when there is a clearer picture, it is possible to clarify the distribution and initial allocation of memory and cores. in the presence of backups, at a specially allocated time, you can move the disks, if necessary. further reasoning regardless of the choice of hypervisor
3 -

SSD - 1x265Gb

clearly with a margin in favor of the terminal, but for blood pressure at least 1/3. if you remove all user profiles from the system disk of the terminal to the raid (are you planning a raid on hard drives?), which would be correct, then approximately AD / Terminal = 2/3 is possible, or even in half. BP should not be clamped either
4 -

HDD - 4x1Tb

clearly give everything to the Terminal. I strongly recommend ride 10 (the only ride where the speed increases in proportion to the number of disks). despite the greater loss in volume, better performance and high reliability. 8 cheap disks are better in the top 10 than 4 expensive ones (but a couple of disks of this model should still be put on the shelf for emergency replacement)
5 - BP - I strongly recommend making a backup BP controller (!!! not role separation, but a backup one). a good solution would be to place it in another physical computer (maybe an old tower?)
6 - if you need a sufficiently large file storage - a strong recommendation, again in a separate computer .. (I will not repeat the third time, but in general, NOT a heavily exploited file storage, you can combine with a backup BP controller))
7-

how to properly organize a backup of all this joy?

usually you don’t need to invent anything here - SQL using its standard tools (study backup schemes, losing a day of work, it may already be expensive), Terminal and AD - using winserver’s own tools (during minimum load hours, again schemes, but one daily backup here usually allowed). but here's what you should think about - the backup medium should be again in another computer (or streamer). it is important. let's say something very bad happened and the whole raid is covered - if there are backups on it, then oh
7+ - there are third-party solutions, such as veeam backup (and there seems to be a free edition), they help monitor backup processes, make it easier to configure, report, restore. but as a rule, such solutions require a uniquely dedicated backup server and installation of agents on the backed up servers/stations. these are additional costs and resources on the servers, and on the backup server itself. they are justified when the staff is small (you are alone) and the servers are already like uncut dogs
7++ - about streamers - the ceiling in the server room fell, methorite (tfu-tfu) got into the building - if your backups are in the same room - again.. reliable scheme provides for stepwise backups, and storage of the most durable media in another location. but this is a separate big topic, information security is attracted there, and so on .. although everything is available on the network

Answer 2

HDD - 4x1Tb
SSD - 1x265Gb
You do not pay attention to an extremely important thing - the disk subsystem.
To put on colocation without hot spare and "iron" RAID?
Don't run in case.
And you have to run very fast.
Extension???
Perhaps you know what you are doing.
But I almost never managed to use more than 30-40 G of RAM with 1C and a terminal server. Well, he doesn't want to eat her.