Windows VM Split-Up

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Sep 13, 2020
5
0
1
Edge of the Multiverse
In the next few months, I'll be migrating a Windows Server VM to a new ESXi host. Before I attempt this, I want to get your opinions on how this move/migration should be carried out. The VM in question has multiple services on it, and I have been considering splitting them between multiple VMs. While the current services function/perform satisfactorily on one VM, I wish to consider best practices moving forward. Keep in mind, this is for a home server (not a true production environment). Here is the current split, if I implemented today:

WinServ0 (domain controller):
  • Active Directory, AD CS
  • Azure Entra Connect Sync
  • ManageEngine Endpoint Central
  • MariaDB
  • DnsTube
WinServ1 (replicated DC):
  • EaseUS BackUp Center
  • hMailServer/Stalwart
  • MailStore Server
WinServ2 (replicated DC):
  • SoftEther VPN Server
WinServ3 (domain member):
  • Windows Admin Center

I'm not sure if I'll benefit from switching to this though, seeing that I'd need to manage/troubleshoot Windows Updates and manage patches for three to four VMs, while running the same number of services Not to mention, paying for two to three more Windows Server licenses. Please let me know your thoughts.
 
Last edited: