Paul Evans

<div>
Hi Ivan<br />
<br />
Thanks for the help.<br />
I wasn't looking to to run Exchange on a DC - i recognise that's not good practice.<br />
<br />
What I was considering is Server 2016 DC on physical hardware (the server) and then run Exchange 2016 WITHIN a VM on that DC.<br />
<br />
Is this the same as running Exchange on a DC?<br />
Andy
</div>


Hi Ivan

Thanks for the help.
I wasn't looking to to run Exchange on a DC - i recognise that's not good practice.

What I was considering is Server 2016 DC on physical hardware (the server) and then run Exchange 2016 WITHIN a VM on that DC.

Is this the same as running Exchange on a DC?
Andy

<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 />
The host can only be Hyper-V with no other roles. One cannot run a DC on the host along with the Hyper-V Role for licensing reasons but also Hyper-V makes too much of a network stack change to be compatible with a DC running in same.<br />
<br />
Run them as a pair of VMs with the host set up with the Hyper-V Role only.
</div>


I have two very thorough EE articles on all things Hyper-V:

Some Hyper-V Hardware and Software Best Practices [https://www.experts-exchange.com/articles/13256/Some-Hyper-V-Hardware-and-Software-Best-Practices.html]
Practical Hyper-V Performance Expectations [https://www.experts-exchange.com/articles/31442/Practical-Hyper-V-Performance-Expectations.html]

The host can only be Hyper-V with no other roles. One cannot run a DC on the host along with the Hyper-V Role for licensing reasons but also Hyper-V makes too much of a network stack change to be compatible with a DC running in same.

Run them as a pair of VMs with the host set up with the Hyper-V Role only.

<div>
All comments were helpful - i went for best solution with Lee W simply because it was concise and direct.
</div>


All comments were helpful - i went for best solution with Lee W simply because it was concise and direct.

<div>
<div class="content wysiwyg-content">
We currently have SBS2011 and We want to move to Server 2016 as our DC with Exchange 2016.<br />
We don't need any advice for setting-up Server 2016 as a DC or Exchange 2016 - however<br />
<br />
<br />
Should we-<br />
<br />
Setup and configure Server 2016 as a DC on physical hardware - install the Hyper-V element and setup a VM to run Exchange 2016 (within the DC environment)?<br />
OR<br />
Do we setup the host OS (Server 2016) on Physical hardware and install the Hyper-V element - THEN setup 2 VM's - one as the DC and the other as Exchange.<br />
<br />
Which is the best configuration please.<br />
Thank you<br />
Paul
</div>
</div>


We currently have SBS2011 and We want to move to Server 2016 as our DC with Exchange 2016.
We don't need any advice for setting-up Server 2016 as a DC or Exchange 2016 - however


Should we-

Setup and configure Server 2016 as a DC on physical hardware - install the Hyper-V element and setup a VM to run Exchange 2016 (within the DC environment)?
OR
Do we setup the host OS (Server 2016) on Physical hardware and install the Hyper-V element - THEN setup 2 VM's - one as the DC and the other as Exchange.

Which is the best configuration please.
Thank you
Paul

Server 2016 DC and Exchange - Separate VM's or DC on Host Machine with Exchange on VM?

Hardware includes cell phones and other digital living devices, tablets, computers, servers, peripherals and components, printers and scanners, gaming consoles, networking hardware such as routers, hubs, switches and modems, storage devices and security equipment such as firewalls and other appliances.

Hardware

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Virtual machines are created and managed through a web-based interface that relies on Internet Information Services (IIS) or through a Windows client application tool called VMRCplus. Features included Linux guest operating system support, Virtual Disk Precompactor, symmetric multiprocessing (SMP), x64 host operating system support, the ability to mount virtual hard drives on the host machine and additional operating systems support, including Windows Vista, and a volume shadow copy writer.

Microsoft Virtual Server

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

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

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.