Can we deploy both Server-based and Client-based VMs like this in the same VDI environment? Do we need to worry about licensing each individual Client-based VM? It seems ridiculous to need to provide a separate product key/activation for each VM instance when they're only needed for a short time. Do I have any of the information above wrong? Please correct me if I do ![]() We can deploy Client-based VMs, and employees can concurrently access up to 4 client virtual machines at any given time because they have SA Employees can connect to Server-based VMs only if they have a CAL We can deploy as many Windows Server-based VMs as we would like, and can properly handle licensing VM OS's using AVMA We need to apply a core-based license to our physical WS2019 Datacenter, covering all 16 cores, for the hardware to be in compliance. More often, VMs will probably be needed on a week-long basis, then destroyed. At max, each VM would be used for a month or two. None of these VMs would be in use long-term. Our employees will not need to use this scenario often, only in unique Very rarely, we would occasionally like to host Server-based VMs (WS2012RS and WS2016 mainly) on our physical WS2019 and allow employees to access their personal server virtual machines. To host Client-based VMs (Win10 mainly) on our physical WS2019 and allow employees to remotely access their dedicated personal virtual machines ![]() All employees have Software Assurance included with their Windows OS license on their laptops We have a Windows Server 2019 Datacenter Edition running on a physical machine with 2 8-core processors (total of 16 cores) I've read a lot of documentation regarding VDI and RDS, yet I am still a little confused on some aspects.
0 Comments
Leave a Reply. |