What licenses are required to WORK MS VDI?

Question

Virtualization

Good afternoon.
We plan to send pooled VDI to the pilot. Without a licensing server, if I'm not mistaken, we have 180 days to "feel". I would like to know which licenses will first need to be purchased and installed so that VDI does not turn into a pumpkin after these 180 days.
From reading the MS Licensing docs, I understand that we have three options:

1. VDI Suite
   
2. RDS CALs + VDAs
   
3. RDS CALs + Software Assurance
   

VDI Suite is not suitable for us, because. all additional buns (MDOP, etc.) are not planned to be used. VDA, as far as I understand, is not installed anywhere at all - this is a license "to be kept in a safe in case of checks." As a test, I spiraled a pack of RDS CALs in a known way and set the clock forward a couple of years - the farm did not seem to turn into a pumpkin, but the following messages are present in the licensing manager:
At the same time, an RDS CAL license is not issued to the client, this Temporary VDI Suite is issued. Because of which, naturally, there are doubts whether I correctly understood what licenses are needed.
Oh yes, Windows Server 2012 R2 is used, which, if I understand correctly, no longer uses the VDI Suite Standard/Premium licensing model as in 2K8 R2.
PS The guest system is Windows 8.1 Ent. I correctly understood that it also needs to be licensed? What is the most convenient way to do this? Deploying a KMS server? Or is it possible to completely forget to activate guest systems and just store a pack of purchased licenses for inspection bodies?

Answer 1

I answer myself:
For MS VDI to work in the licensing manager, you need to install only RDS CAL. Windows Server CALs are also required in the same number as RDS CALs + Virtual Desktop Access Licenses (VDA if using non-Windows devices and/or without Windows installed with such rights included in the edition). WS CAL and VDA are taken out of the envelope and installed in a folder with the rest of the licenses in a safe. No more action is required.
Guest systems can be activated with a MAK key when using Personal Virtual Desktops, KMS deployment is only necessary when using Pooled Virtual Desktops.