Allan Hancock
asked on
Setting up AD Domain controller and Exchange 2016 on Virtual Machines
Currently have a Dell Server setup with Server 2016 Standard, 32gb Ram 2TB Hardrives (new install) and will put 10 users on it.
Our current system:
We are on an old SBS 2008 with 32GB Ram on a Dell t410 with one NIC
This systems has server two roles. A Customer CRM (uses SQL Express) that is shared among the users and Ex
change is just use for sharing calendars. Two public calendars for our two small conference rooms.
On new server...
Hyper-V Role has been installed and I know I have two Virtual Machine Licenses I can use with Server 2016 Standard.
So my questions are:
(1) Advice on how much storage-memory to allocate during setup of the VM's for AD and Exchange?
Of course I'm assuming I'm first installing Server 2016 on those VM's before doing AD and Exchange.
(2) Can I also assume I should do the Active Directory install before the Exchange VM install?
I'm a little confused when I've seen suggestions like
"To install Exchange 2016 we must update Active Directory. This update extends the current schema to accept the new 2016 attributes." followed by "Exchange can perform this automatically during the graphical setup. However, you may also prefer to do this separately ahead of time"
(3) After setup of Exchange, what about drives within the VM for Exchange Directory , logs and database?
Or any other advice on this exact setup other than choosing office 365, etc. I'm not changing my plan to use this server , this way.
(4) Do I need more than one ethernet card or is one enough considering Virtual Switch?
(5) Do I need a static ip for exchange during setup?
(6) There is a possiblity I will need to put SQL Express on because of a piece of shared software the 10 users share. So the question is: Do I need to buy a 3rd VM license? Or can it go on one of the VM's or even on the main portion of the physical server that's only got the Hyper_V role?
Our current system:
We are on an old SBS 2008 with 32GB Ram on a Dell t410 with one NIC
This systems has server two roles. A Customer CRM (uses SQL Express) that is shared among the users and Ex
change is just use for sharing calendars. Two public calendars for our two small conference rooms.
On new server...
Hyper-V Role has been installed and I know I have two Virtual Machine Licenses I can use with Server 2016 Standard.
So my questions are:
(1) Advice on how much storage-memory to allocate during setup of the VM's for AD and Exchange?
Of course I'm assuming I'm first installing Server 2016 on those VM's before doing AD and Exchange.
(2) Can I also assume I should do the Active Directory install before the Exchange VM install?
I'm a little confused when I've seen suggestions like
"To install Exchange 2016 we must update Active Directory. This update extends the current schema to accept the new 2016 attributes." followed by "Exchange can perform this automatically during the graphical setup. However, you may also prefer to do this separately ahead of time"
(3) After setup of Exchange, what about drives within the VM for Exchange Directory , logs and database?
Or any other advice on this exact setup other than choosing office 365, etc. I'm not changing my plan to use this server , this way.
(4) Do I need more than one ethernet card or is one enough considering Virtual Switch?
(5) Do I need a static ip for exchange during setup?
(6) There is a possiblity I will need to put SQL Express on because of a piece of shared software the 10 users share. So the question is: Do I need to buy a 3rd VM license? Or can it go on one of the VM's or even on the main portion of the physical server that's only got the Hyper_V role?
1. It is always unanswered question, because it's depends how many users you'll have on Exchange, how hard they'll use exchange, is they are going to send a lot of pictures / projects over email
Bottom line is: You should separate Database - logs from OS, so Exchange should have 2 separate disks - in your case 2 separate virtual disks.
Exchange is not using a lot of memory, but You should assign 16GB minimum. I think that hawing 32GB on host is not so much, You should have server with 64GB memory and assign 32 for Exchange to be comfortable.
2. You MUST install Active directory first then Exchange !!!
3. I did explained this in #1
4. If you expected a lot of traffic you should have more than 1 NIC, but if your server has 4 NICs then you can use 1 NIC for HOST then build TEAM with 3 NICs and use TEAM to create Virtual Switch
5. It's recommended to have static IP for all servers in domain especially for DC and Exchange. You'll need to configure your DNS so static IP is recommended
6. You should have separate machine for SQL, but if this is Express and is not going to use a lot of resouces you can install it on
domain controller, or if your HOST server will be part of domain you can install it on HOST
Bottom line is: You should separate Database - logs from OS, so Exchange should have 2 separate disks - in your case 2 separate virtual disks.
Exchange is not using a lot of memory, but You should assign 16GB minimum. I think that hawing 32GB on host is not so much, You should have server with 64GB memory and assign 32 for Exchange to be comfortable.
2. You MUST install Active directory first then Exchange !!!
3. I did explained this in #1
4. If you expected a lot of traffic you should have more than 1 NIC, but if your server has 4 NICs then you can use 1 NIC for HOST then build TEAM with 3 NICs and use TEAM to create Virtual Switch
5. It's recommended to have static IP for all servers in domain especially for DC and Exchange. You'll need to configure your DNS so static IP is recommended
6. You should have separate machine for SQL, but if this is Express and is not going to use a lot of resouces you can install it on
domain controller, or if your HOST server will be part of domain you can install it on HOST
ASKER
I did mention it's for 10 users but forgot to mention what the use was for. I have corrected my question.
The use is just in house sharing of calendars, the same as on our current SBS 2008
So what is considered a lot of traffic?
On our SBS 2008 system we have 32gb ram on a Dell Poweredge T410
and using only 1 Nic. It's running exchange for calendaring and a CRM (customer database software called Junxure (needs SQL Express) and it all works fine, not sluggish, etc.
But we are moving on to Windows 10 so bye bye SBS 2008.
Owners don't want to invest monthly for 365.
The use is just in house sharing of calendars, the same as on our current SBS 2008
So what is considered a lot of traffic?
On our SBS 2008 system we have 32gb ram on a Dell Poweredge T410
and using only 1 Nic. It's running exchange for calendaring and a CRM (customer database software called Junxure (needs SQL Express) and it all works fine, not sluggish, etc.
But we are moving on to Windows 10 so bye bye SBS 2008.
Owners don't want to invest monthly for 365.
So your configuration is OK
ASKER
Thanks Tom!
Any comment on the configuring the AD Virtual machine and Exchange Virtual machine during the setup of those VM's?
Any comment on the configuring the AD Virtual machine and Exchange Virtual machine during the setup of those VM's?
32GB is too small. 64GB should be the minimum with Intel Xeon Scalable having 6 memory channels that means 6x 16GB = 96GB being the best buy for the dollar.
Intel Xeon E-2100/2200 can do 128GB. Do that.
Two VMs:
VM0: ADDS, DNS, DHCP, File & Print (prefer these on their own VM)
VM1: Exchange 2016/2019 (we are deploying 2019)
Resources:
VM0: 2x vCPUs, 4GB vRAM
VM1: 4x vCPUs, 16GB vRAM
What is the storage setup? That's going to be the weakest performance link.
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
Intel Xeon E-2100/2200 can do 128GB. Do that.
Two VMs:
VM0: ADDS, DNS, DHCP, File & Print (prefer these on their own VM)
VM1: Exchange 2016/2019 (we are deploying 2019)
Resources:
VM0: 2x vCPUs, 4GB vRAM
VM1: 4x vCPUs, 16GB vRAM
What is the storage setup? That's going to be the weakest performance link.
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
ASKER
I wish all you “Experts” would at least be somewhat close in your opinions?!!
The difference is so dramatic, I don’t know whose right..
Sheesh...
The difference is so dramatic, I don’t know whose right..
Sheesh...
Allan
I've told you that 32GB ram is not I recommended, but If you don;t want to invest money then your configuration will still work.
Do not assign more than 2 virtual processors per one VM's and you will be OK
I've told you that 32GB ram is not I recommended, but If you don;t want to invest money then your configuration will still work.
Do not assign more than 2 virtual processors per one VM's and you will be OK
ASKER
Thanks Tom
Your responses did make the most sense but I was so bugged by someone saying 96gb ram
Your responses did make the most sense but I was so bugged by someone saying 96gb ram
Because 96GB is optimal amount for your processor in server.
My articles explain a lot about the "why" we do what we do.
If one has a 1 ton dually truck would one run with just one set of wheels leaving one emtpy on the rear axle?
If one has a 1 ton dually truck would one run with just one set of wheels leaving one emtpy on the rear axle?
I've just done similar...
Does your 2008 Server have AD?
Why Server 2016 and not 2019?
Will you want to go to Exchange 2019?
I'd recommend a second DC, also ... Can you use the old machine fo that?
Does your 2008 Server have AD?
Why Server 2016 and not 2019?
Will you want to go to Exchange 2019?
I'd recommend a second DC, also ... Can you use the old machine fo that?
ASKER
It’s SBS 2008 on the old server
It came with AD, 2007 Exchange etc
The why as to Server 2016 doesn’t matter as it’s been purchased and project is started.
As to 2019 probably not as we probably we end up being cloud based in a couple years as the company I work for will be forced to by the company’s we connect to (investment)
Ifs say we could make the old server (Dell T410 32gb ram) a 2nd DC
It came with AD, 2007 Exchange etc
The why as to Server 2016 doesn’t matter as it’s been purchased and project is started.
As to 2019 probably not as we probably we end up being cloud based in a couple years as the company I work for will be forced to by the company’s we connect to (investment)
Ifs say we could make the old server (Dell T410 32gb ram) a 2nd DC
ASKER
As to the one dolly truck example
When your forced by a cheap ass company to come up with a cheap ass solution sometimes your simply stuck with making the truck run on two wheels
When your forced by a cheap ass company to come up with a cheap ass solution sometimes your simply stuck with making the truck run on two wheels
Ok ... Yes, the old machine as DC2 makes sense.
In fact, you could use the free VMware hypervisor on the T410, give the DC2 8-12GB and have plenty for another server (print, or even a replica Exch2016 in a DAG. I run VMWare 6.5 on a T410 with 64GB ram at home
First, I'd make sure your Exch2007 is on SP2.
Then raise Domain and Forest AD functional level to 2008R2 - necessary for later Exch versions
This will help - https://docs.microsoft.com/en-us/exchange/exchange-deployment-assistant?view=exchserver-2016
General phases for migrating to Exchange 2016:
1. Install Exchange 2013 into existing Exchange 2007 organization - you can use an eval 2012OS and eval Exch2013
2. Move services and other infrastructure to Exchange 2013.
3. Move mailboxes and public folders to Exchange 2013.
4. Decommission remaining Exchange 2007 servers.
5. Install Exchange 2016 into existing Exchange 2013 organization - with database and logs on separate volumes
6. Move mailboxes, public folders, services, and other infrastructure to Exchange 2016.
7. Decommission remaining Exchange 2013 servers
Then you can create the VM for 2016 AD, move the FSMO roles to it.
Move any other services from the old machine - maybe test with it off for a day or so.
Decommission old machine
Install new OS on old server for use as additional DC ... possibly with VMWare as I said above
One other suggestion would be to have the CRM on it's own VM ... If only 10 users, you could use Win10 as the OS
In fact, you could use the free VMware hypervisor on the T410, give the DC2 8-12GB and have plenty for another server (print, or even a replica Exch2016 in a DAG. I run VMWare 6.5 on a T410 with 64GB ram at home
First, I'd make sure your Exch2007 is on SP2.
Then raise Domain and Forest AD functional level to 2008R2 - necessary for later Exch versions
This will help - https://docs.microsoft.com/en-us/exchange/exchange-deployment-assistant?view=exchserver-2016
General phases for migrating to Exchange 2016:
1. Install Exchange 2013 into existing Exchange 2007 organization - you can use an eval 2012OS and eval Exch2013
2. Move services and other infrastructure to Exchange 2013.
3. Move mailboxes and public folders to Exchange 2013.
4. Decommission remaining Exchange 2007 servers.
5. Install Exchange 2016 into existing Exchange 2013 organization - with database and logs on separate volumes
6. Move mailboxes, public folders, services, and other infrastructure to Exchange 2016.
7. Decommission remaining Exchange 2013 servers
Then you can create the VM for 2016 AD, move the FSMO roles to it.
Move any other services from the old machine - maybe test with it off for a day or so.
Decommission old machine
Install new OS on old server for use as additional DC ... possibly with VMWare as I said above
One other suggestion would be to have the CRM on it's own VM ... If only 10 users, you could use Win10 as the OS
ASKER
Hey Mike ..
You mention doing the AD VM On 2016 Server after having put exchange on
I thought the AD had to be put on first. before Exchange? I’m not sure if it was said in prior answer or not..
You mention doing the AD VM On 2016 Server after having put exchange on
I thought the AD had to be put on first. before Exchange? I’m not sure if it was said in prior answer or not..
Also, you might need to migrate SYSVOL before changing the AD
https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405
https://techcommunity.microsoft.com/t5/storage-at-microsoft/streamlined-migration-of-frs-to-dfsr-sysvol/ba-p/425405
ASKER
Mike..
One other thing
Have you read thru my original post and all the comments made. Just wondered what you’re take is compared to what others have said
One other thing
Have you read thru my original post and all the comments made. Just wondered what you’re take is compared to what others have said
You have an AD with SBS ... As long as you have it at Functional Level 2008R2, you can do the Exchange migrate and kill the old Exchange server before doing the same with the other services and AD.
You'd only create the AD VM first if you want to build a new Domain and that might have usersoff-line for a while
You'd only create the AD VM first if you want to build a new Domain and that might have usersoff-line for a while
Most others address the hardware, which is mainly performance. Though, the storage setup is the big factor here
All the OSs in this scenario should have static IPs.
What version of SQL is the CRM using?
If it's as old as the server, it might not run on the later OSs ... So having it on it's own VM (on either machine) would be better
All the OSs in this scenario should have static IPs.
What version of SQL is the CRM using?
If it's as old as the server, it might not run on the later OSs ... So having it on it's own VM (on either machine) would be better
ASKER
It’s sql express not the full blown sql
According to the crm people the amount of users we have doesnt warrant the full blown sql
And whatever express version they will use for our 2016 they claim will be compatible
According to the crm people the amount of users we have doesnt warrant the full blown sql
And whatever express version they will use for our 2016 they claim will be compatible
ASKER
Storage size and speed I’m hoping won’t be an issue with 2Tb of ssd (not the consumer ssd)
Our current sbs2008 has (2) 1tb drives in raid with lots of room left over
The crm uses only 8gb of space
Our current sbs2008 has (2) 1tb drives in raid with lots of room left over
The crm uses only 8gb of space
Then it must be SQL 2014 ... That's the only version that's ok on Server 2008 and 2016.
Though technically it ended mainstream support last year.
Either way, I'd have it on its own VM ... Can be Win 10 for 10, or fewer, users.
With the Exchange VM, best to have one volume for OS, one for database and one for logs
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
For 10 users I suggest you carry on with O365 Business premium or even F1 plan and avoid maintaining onpremise exchange software
U even don't need AD in that case, You can use Azure Identities to logon to workstations directly in Azure in secure manner and can avoid entire onpremise setup