Optimal use of a server platform for virtualization?

Question

Active Directory

Dear IT people, help with advice to the old, not striving for anything :D
In the organization, 50-70 users decided to buy the next server.

Server platform Supermicro SuperServer SYS-5019S-L
Form factor: 1U
Line: SuperServer
Model: SYS-5019S-ML
Processor: Intel Xeon E3-1220 v6 OEM
Memory: 2 x Crucial [CT16G4RFD424A] 16 GB
Number of hard drives: 2 x SSD Samsung PM883 [MZ7LH240HAHQ-00005]
RAID controller: Intel C232 Network controller: Intel i210
-AT 2x1Gb/s
Power supply: 1 x 200 W

of interest Windows Server 2008/2012/2016/2019 Standard,Enterprise,Datacentr.

Actually I look towards virtualization, but there is no experience with it, not with server hardware.
On the server, as I suppose, there will be the following:
1) WinServer 20 ** r2 with the role of hyper-v (everything else, as I believe, will be in virtual machines, I don’t know about AD only)
2) AD DC + DNS
3) WSUS + Kaspersky Security Center 11
4) As far as I understand, it is desirable to make a backup controller.

And so, I want to push the host on WS and 2 virtual machines, WSUS + KSC into a separate VM.
I don’t know what to do with the controller, maybe it’s better to raise the main controller and dns to the host machine along with hyper-in? Then only 1 VM will be needed, or it will be possible to allocate each role to its own VM.
I think to put the backup controller on another host machine. How to pick it up and set it up so that it connects when the main one falls, to be honest, we will beat our heads against the wall, maybe it will work out.

Need advice from experts, is this server suitable at all? By the way, there are 2 cards, it turns out that only one will be used.
How best to use the resources of this piece of iron?

Tell me what OS and edition to take so that the VM is enough?

Can anyone suggest another way to implement this scheme?

I'm sorry, bummer.

Answer 1

Since the organization had enough money for MS licenses, it’s somehow strange to deploy everything on one server - it’s non-fault-tolerant and in general they usually don’t do one AD DC, but do it starting with three (see split-brain).
A raid controller for a mirror on two disks is also somehow strange. What will you do when one of the SSDs dies?

Answer 2

Processor: Intel Xeon E3-1220 v6 OEM

I doubt that you will go far on four cores . Lift the
first domain controller on hardware, the second - you can virtual
Kaspersky can manage Windows updates, so you can refuse WSUS

Answer 3

Free Hyper-V Server per host, Server 2019 standard for virtual machines.
1. you can't virtualize with 32GB of RAM
2. I don't see any point in virtualization for you at all.

Answer 4

3)WSUS + Kaspersky Security Center 11
Avoid this at the first stage.
Kaspersky for sane money has a cloud admin panel for antivirus, go to their product with it.
WSUS is a thing very specific to mature infrastructures, for now do without it, you probably won't need it at all in the foreseeable future.
Deploy the second domain controller on the second iron server, but you will also need a second license for the win server.
But think about it, why do you need it all, what is the goal? Now for small companies it is much cheaper to keep everything in the cloud if you have software licensed.

Answer 5

Your server is on vmware's supported list, so if the answers above still make a strong case for virtualization, then I highly recommend the free ESXi (version 6.0U3 is supported on your hardware).
And the arguments and counterarguments are not so simple in fact. From a performance point of view, virtualization is a downside. From the point of view of operation, scaling and security - only pluses. If security is at the forefront, then you can even run just one guest on all its resources on the host, which at first glance may seem silly to someone. But when the task of scaling capacity arises, the virtual server is stupidly copied to a new, more powerful hardware, and even without stopping its work if there is an HA license.

Answer 6

Guys, if it's not difficult, tell me a couple more points, I have not encountered server hardware, so questions arise.
The platform was chosen by Supermicro SuperServer SYS-5019S-ML, I think there will be 2 SSDs of 240GB each without raids, 1 for Windows, the second one can be for backups, I haven’t decided yet, but the questions are as follows.
1) The manager suggested the following pros for the platform:
Intel Xeon E3-1220 v6 OEM
processor Intel Xeon E3-1240 v5 OEM processor
I chose the first one, the frequency is lower there, but the RAM frequency is higher, for some reason it attracted, but after reading a little about the platform, I understood that these processors do not have a built-in graphics core, it turns out you need either a graphics card separately in PCIe or an Intel Xeon E3-1245 V6 3.7 GHz / 4core / SVGA HD Graphics P630 / 1 + 8Mb / 73W / 8 GT / s LGA1151 processor?
2) If you combine a disk into a raid, put wines with hell on them, and so on, if one ssdshnik fails, the whole system falls?
3) The UDIMM form factor is indicated in the specification, the manager screams they don’t have them, there are only RDIMMs, and more specifically
Crucial [CT16G4RFD424A] 16 GB and DDR4 Kingston KSM29ES8 / 16ME 16Gb, will this memory fit the platform, do you want to write 4 bars of 16 each in TK.
4) Not exactly on the server .... ISP is needed, as I understand it, it is selected by adding up the power consumption, i.e. server block 350W + Split system 700W, that is, you need an IPB capable of withstanding a voltage of at least 1050W?