Hyper-V test environment
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks!
Welcome.
As a FYI:
I have two very thorough EE articles on all things Hyper-V:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
Some PowerShell Guides:
PowerShell Guide - Standalone Hyper-V Server
PowerShell Guide - New VM PowerShell
PowerShell Guide - New-VM Template: Single VHDX File
PowerShell Guide - New-VM Template: Dual VHDX Files
Here are some focused articles:
Set up PDCe NTP Domain Time in a Virtualized Setting
Slipstream Updates Using DISM and OSCDImg
Protecting a Backup Repository from Malware and Ransomware
Disaster Preparedness: KVM/IP + USB Flash = Recovery. Here’s a Guide
As a FYI:
I have two very thorough EE articles on all things Hyper-V:
Some Hyper-V Hardware and Software Best Practices
Practical Hyper-V Performance Expectations
Some PowerShell Guides:
PowerShell Guide - Standalone Hyper-V Server
PowerShell Guide - New VM PowerShell
PowerShell Guide - New-VM Template: Single VHDX File
PowerShell Guide - New-VM Template: Dual VHDX Files
Here are some focused articles:
Set up PDCe NTP Domain Time in a Virtualized Setting
Slipstream Updates Using DISM and OSCDImg
Protecting a Backup Repository from Malware and Ransomware
Disaster Preparedness: KVM/IP + USB Flash = Recovery. Here’s a Guide
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.
If this is "Pre-Production" I'd throw it straight into your domain with a view to virtualise everything at a later date after testing and configuration.
Regards
Alex