F5F Stay Refreshed Software Operating Systems Learn how to license Windows virtual machines.

Learn how to license Windows virtual machines.

Learn how to license Windows virtual machines.

K
kaiflow
Junior Member
Find
4
05-18-2016, 07:17 PM
#1
I'm aiming to set up a server to host four Windows VMs and support RDP via thinclients. Licensing each Windows 10 installation on the VM is a key challenge for my family's small business. We currently have two offices—one with four desktops and another with just two laptops, one exclusive to me. The first office has four desktops with Intel dual-core processors and 8GB RAM, while the newer office only has two laptops, one private. All tasks are administrative in nature, so heavy app usage is unlikely. I’m exploring homelab projects and think a server VM would suit our growing needs. My plan is to start with a single 12 or 16-core server at the first office and move the existing desktops there. I intend to purchase older Intel Xeon workstations (with dual sockets) for future upgrades. I’ll manage the VMs using ESXi, aiming to either buy refurbished thinclients or use Raspberry Pi-based thinclients for RDP access. The main hurdle is licensing—currently, I’m using a throwaway VM for Windows 10 Pro, but business requirements demand individual licenses per VM. This seems costly and limited to two Windows Pro VMs. I’m unsure how to handle multiple licenses without breaking the budget. I also want to add a VPN later so remote employees can connect from the second office as staff numbers increase. In short, I need a clear path to license each VM properly while keeping costs manageable.
Reply
Reply
K
kaiflow
05-18-2016, 07:17 PM #1

I'm aiming to set up a server to host four Windows VMs and support RDP via thinclients. Licensing each Windows 10 installation on the VM is a key challenge for my family's small business. We currently have two offices—one with four desktops and another with just two laptops, one exclusive to me. The first office has four desktops with Intel dual-core processors and 8GB RAM, while the newer office only has two laptops, one private. All tasks are administrative in nature, so heavy app usage is unlikely. I’m exploring homelab projects and think a server VM would suit our growing needs. My plan is to start with a single 12 or 16-core server at the first office and move the existing desktops there. I intend to purchase older Intel Xeon workstations (with dual sockets) for future upgrades. I’ll manage the VMs using ESXi, aiming to either buy refurbished thinclients or use Raspberry Pi-based thinclients for RDP access. The main hurdle is licensing—currently, I’m using a throwaway VM for Windows 10 Pro, but business requirements demand individual licenses per VM. This seems costly and limited to two Windows Pro VMs. I’m unsure how to handle multiple licenses without breaking the budget. I also want to add a VPN later so remote employees can connect from the second office as staff numbers increase. In short, I need a clear path to license each VM properly while keeping costs manageable.

Reply
Reply