<div>
If is possible this is the configuration that I prefer:<br />
<br />
- OS on SSD in Raid 1<br />
- For every VM a Virtua Disk for the page file that is store on SSD in Raid 0 (or Raid 1 but different from OS)<br />
- For the Virtul Disk of the VM depends how there are in the Virtual Disk, but Raid 10 is often a good choose, see my post <a href="https://www.devadmin.it/2016/02/25/considerazioni-per-la-scelta-del-raid-corretto/" rel="ugc">https://www.devadmin.it/2016/02/25/considerazioni-per-la-scelta-del-raid-corretto/</a>&nbsp;for some considerations about the RAID.
</div>


JPD153

<div>
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 />
A couple of 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 />
<a href="http://blog.mpecsinc.ca/2016/02/protecting-backup-repository-from.html" rel="ugc">Protecting a Backup Repository from Malware and Ransomware</a><br />
<br />
Disaster Preparedness: <a href="http://blog.mpecsinc.ca/2017/06/disaster-preparedness-kvmip-usb-flash.html" rel="ugc">KVM/IP + USB Flash = Recovery. Here’s a Guide</a><br />
<br />
EDIT: Specific to the questions:<br />
1: Load up the 2.5&quot; bays with 10K SAS in RAID 6. Two logical disks, one 75GB for the host OS and the balance to the VMs.<br />
2: VM in the standalone virtualization host and leave the host in WORKGROUP mode.<br />
3: Leave the host with Hyper-V. That's it. Use the Exchange Migration Advisor to run the migration. It works well.
</div>


<div>
<blockquote>
2) Should Active directory be on a VM or a physical machine ?<br />
3) 2 or 3 VMs planned: 1 for Exchange, one for File and print sharing and may be another one for A/D depending on suggestions to 2)
</blockquote>
<br />
Please don't put AD on either a Hyper-V host (for licensing reasons) or an Exchange server (for a million reasons). Aside from those recommendations, it'll work fine on either a properly resourced VM or a physical server. Promoting at least two domain controllers is recommended for redundancy in case one of them winds up upside down and on fire...but I recognize that this isn't always practical in a small environment. If you have to stick with a single domain controller, just make sure it's being backed up regularly, and don't forget to back up its system state.
</div>


<div>
Move email to O365.<br />
DC should almost always be a VM.<br />
Use same RAID array for Hyper-V and your VMs. You can use SSD in RAID 1 or 5. You can use HDD in RAID 1 or 10. RAID 6 with HDD is a special case where you need large capacity and low IOPS. RAID 5 with HDD is a special case for small drives and a small array.<br />
<br />
Don't buy 15K disks. If your use case calls for 15K HDD, SSD will be cheaper and faster.<br />
<br />
My general platform is a pair of SSD in RAID 1. Use first VM as a DC and file print server. That leaves second VM license available for other needs. If you need more capacity than RAID 1 provides, go to SSD in RAID 5.
</div>


<div>
ANy good reason why the host holding the DC VM should be outside ofthe domain ?
</div>


<div>
I did appreciate all your comments - I am trying to setup something efficient and I am trying to get the best advices from competent people. Thanks again
</div>


<div>
<div class="content wysiwyg-content">
Setting up a new Hyper V environment replacing SBS 2011<br />
I have the opportunity to do a full setup of Windows 2019 server with Exchange 2019 to replace an aging SBS 2011.<br />
I will need a new hardware platform and look for suggestions on the best practices:<br />
1) Should the host OS be on an SSD rather than SAS 15K ? (it will be on a RAID 1 anyway and the Hyper V VMs will be on a RAID 5 or 10 depending on suggestions))<br />
2) Should Active directory be on a VM or a physical machine ?<br />
3) 2 or 3 VMs planned: 1 for Exchange, one for File and print sharing and may be another one for A/D depending on suggestions to 2)
</div>
</div>


Setting up a new Hyper V environment replacing SBS 2011
I have the opportunity to do a full setup of Windows 2019 server with Exchange 2019 to replace an aging SBS 2011.
I will need a new hardware platform and look for suggestions on the best practices:
1) Should the host OS be on an SSD rather than SAS 15K ? (it will be on a RAID 1 anyway and the Hyper V VMs will be on a RAID 5 or 10 depending on suggestions))
2) Should Active directory be on a VM or a physical machine ?
3) 2 or 3 VMs planned: 1 for Exchange, one for File and print sharing and may be another one for A/D depending on suggestions to 2)

Best configuration possible

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

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).

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.