We have a small environment with a physical host running several single-purpose Windows and Linux VMs. I need to add a couple of lightweight services, including Entra Connect and a SAML proxy. Would you put them together on a new VM, or add them to existing servers? We use Hyper-V, and licensing affects how many VMs we can add.
Would you group a few small services on one server?
Asked by
J9~Mildred
Answers
A dedicated utility VM for a few related, low-resource services is a reasonable middle ground. It keeps them off your domain controllers, SQL servers, and application VMs without turning every tiny service into its own machine.
Check the licensing terms before building it, then monitor resource use and keep the VM documented. If one service becomes sensitive, resource-heavy, or hard to maintain alongside the others, split it out later.
Reply to this answer
Before placing anything, check what your current VMs are actually using. A quick look at CPU and memory over normal and busy periods can show whether an existing server has spare capacity. But capacity is only part of the decision: adding services to a production application or database server can make patching and troubleshooting messier.
For identity-related components, I would be especially cautious about putting them on a domain controller. A small, separate utility VM can give you a cleaner boundary, assuming the licensing works.
Reply to this answer
I would group the small, low-impact tools on one task or utility server, then draw a line before it turns into a miscellaneous dumping ground. Give the VM a clear purpose, record what runs there, and make sure its backup and recovery plan covers each service.
Things with their own database, special uptime needs, or a meaningful security boundary deserve their own VM. The right split is about operational risk as much as resource usage.
Reply to this answer
Separate VMs make upgrades and migrations easier, and a failure or reboot for one service is less likely to interrupt another. The tradeoff is extra licensing and more machines to patch and monitor.
If licensing is the blocker, one modest utility VM is a practical compromise. I would avoid adding unrelated services to an existing single-purpose server just because it has spare capacity.
Reply to this answer
Add your answer
Answers are reviewed before publication.
J9~Mildred:
That distinction helps. I was thinking of one utility VM rather than putting these on a domain controller.