Service Manager

BBrayton

<div>
I saw something about the install limiting the roles on the server install to Exchange and something else. &nbsp;That implied to me to not run Exchange in conjunction with file sharing (not DC) guest. ???
</div>


I saw something about the install limiting the roles on the server install to Exchange and something else.  That implied to me to not run Exchange in conjunction with file sharing (not DC) guest. ???

<div>
For 12 users 16GB vRAM to 24GB vRAM is more than ample for Exchange to run. Make sure to assign 2 vCPUs or 3 vCPUs to the VM to allow for OS and Exchange to work side-by-side.<br />
<br />
I suggest setting up the following for the VM:<br />
&nbsp;VHDX0: OS - 250GB<br />
&nbsp;VHDX1: Exchange and Logs - 250GB<br />
&nbsp;VHDX2: Exchange Databases - 100GB+<br />
<br />
Set up Exchange on VHDX1 and then once the migration is complete move the mailbox database(s) over to VHDX2.<br />
<br />
The <a href="https://docs.microsoft.com/en-us/exchange/exchange-deployment-assistant?view=exchserver-2019" rel="ugc">Microsoft Deployment Assistant</a> is awesome. Please follow it.<br />
<br />
EDIT: Depending on the backup being used make sure in-guest acquiescence is enabled to trigger a log purge!
</div>


For 12 users 16GB vRAM to 24GB vRAM is more than ample for Exchange to run. Make sure to assign 2 vCPUs or 3 vCPUs to the VM to allow for OS and Exchange to work side-by-side.

I suggest setting up the following for the VM:
 VHDX0: OS - 250GB
 VHDX1: Exchange and Logs - 250GB
 VHDX2: Exchange Databases - 100GB+

Set up Exchange on VHDX1 and then once the migration is complete move the mailbox database(s) over to VHDX2.

The Microsoft Deployment Assistant [https://docs.microsoft.com/en-us/exchange/exchange-deployment-assistant?view=exchserver-2019] is awesome. Please follow it.

EDIT: Depending on the backup being used make sure in-guest acquiescence is enabled to trigger a log purge!

<div>
<div class="content wysiwyg-content">
Configuring Exchange under W2016 Hype-v. &nbsp;Here are a couple of questions:<br />
<br />
1. Must Exchange run as it own guest Hyper-V ? &nbsp;Limit cores to 12 cores? &nbsp;Ram to configure? &nbsp; 12 users Exchange<br />
<br />
2. We are migrating to W2016 from SBS 2011. &nbsp;Will standard migration run porting over older Exchange to 2016?<br />
<br />
Tks<br />
Bruce
</div>
</div>


Configuring Exchange under W2016 Hype-v.  Here are a couple of questions:

1. Must Exchange run as it own guest Hyper-V ?  Limit cores to 12 cores?  Ram to configure?   12 users Exchange

2. We are migrating to W2016 from SBS 2011.  Will standard migration run porting over older Exchange to 2016?

Tks
Bruce

Migrating SBS Exchange to new 2016 h-v

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

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.