<div>
Hold up<br />
<br />

<blockquote>
I would like to setup a test environment of VMs on Server 2019 Hyper-V that eventually migrating &nbsp;all current physicals to VMs. 
</blockquote>
<br />
OK so when you've configured your test environment, I'm making an assumption here, but you're going to trash it and go from the start again when you're pushing into production right. <br />
<br />
If this is &quot;Pre-Production&quot; I'd throw it straight into your domain with a view to virtualise everything at a later date after testing and configuration.<br />
<br />
Regards<br />
Alex
</div>


Operations Manager

Mike

<div>
Welcome. <br />
<br />
As a FYI:<br />
<br />
I have two very thorough EE articles on all things Hyper-V:<br />
<br />
<a href="https://www.experts-exchange.com/articles/13256/Some-Hyper-V-Hardware-and-Software-Best-Practices.html" rel="ugc">Some Hyper-V Hardware and Software Best Practices</a><br />
<a href="https://www.experts-exchange.com/articles/31442/Practical-Hyper-V-Performance-Expectations.html" rel="ugc">Practical Hyper-V Performance Expectations</a><br />
<br />
Some PowerShell Guides:<br />
<a href="http://www.mpecsinc.com/powershell-guide-standalone-hyper-v-server/" rel="ugc">PowerShell Guide - Standalone Hyper-V Server</a><br />
<a href="http://www.mpecsinc.com/powershell-guide-new-vm-powershell/" rel="ugc">PowerShell Guide - New VM PowerShell</a><br />
<a href="http://www.mpecsinc.com/new-vm-template-single-vhdx-file/" rel="ugc">PowerShell Guide - New-VM Template: Single VHDX File</a><br />
<a href="http://www.mpecsinc.com/new-vm-template-dual-vhdx-files/" rel="ugc">PowerShell Guide - New-VM Template: Dual VHDX Files</a><br />
<br />
<br />
Here are some focused articles:<br />
<br />
<a href="http://blog.mpecsinc.ca/2014/09/hyper-v-vm-set-up-pdce-ntp-time-server.html" rel="ugc">Set up PDCe NTP Domain Time in a Virtualized Setting</a><br />
<br />
<a href="http://www.mpecsinc.com/os-guide-slipstream-updates-and-drivers-using-dism-and-oscdimg/" rel="ugc">Slipstream Updates Using DISM and OSCDImg</a><br />
<br />
<a href="https://blog.mpecsinc.com/2019/05/17/protecting-a-hyper-v-host-and-backup-repository-from-malware-and-ransomware" rel="ugc">Protecting a Backup Repository from Malware and Ransomware</a><br />
<br />
Disaster Preparedness: <a href="https://blog.mpecsinc.com/2019/05/14/disaster-preparedness-kvm-ip-usb-flash-recovery-heres-a-guide/" rel="ugc">KVM/IP + USB Flash = Recovery. Here’s a Guide</a>
</div>


<div>
<div class="content wysiwyg-content">
I would like to setup a test environment of VMs on Server 2019 Hyper-V that eventually migrating &nbsp;all current physicals to VMs. &nbsp; I currently have Small Business Server 2011 standard with a backup domain controller and File server on a given network. &nbsp;I would like to make sure I can safely setup and test the VMs on an isolated network. &nbsp;I have setup a test workgroup for the Hyper-V machine separate from the current domain. Is that enough to prevent any issues or do I need to create a separate subnet for the Hyper-V as well?
</div>
</div>


I would like to setup a test environment of VMs on Server 2019 Hyper-V that eventually migrating  all current physicals to VMs.   I currently have Small Business Server 2011 standard with a backup domain controller and File server on a given network.  I would like to make sure I can safely setup and test the VMs on an isolated network.  I have setup a test workgroup for the Hyper-V machine separate from the current domain. Is that enough to prevent any issues or do I need to create a separate subnet for the Hyper-V as well?

Hyper-V test environment

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.