Avatar of davebo4503
davebo4503
 asked on

To use DHCP on server 2016 essentials or on the router?

SBS 2011 standard to Windows Server 2016 Essentials migration
Microsoft's docs recommend to move the DHCP funtion to the router.
Is there a good reason for this as opposed to moving it to the 2016 server?
Has anyone had favorable/unfavorable results either way?
If on 2016, can the existing scope/parameters be moved easily from SBS?
SBSWindows OSDHCPWindows 10Azure

Avatar of undefined
Last Comment
davebo4503

8/22/2022 - Mon
Shabarinath TR

DHCP can be configured on the router but depends on your specific requirements.

Windows Server DHCP may be easy to manage from my perspective.


If you want to move the existing scopes to the new DHCP - use powershell to export the existing scopes and scope options into CSV. Use the same CSV to import the scope to the new DHCP. Once the scope is available, test it out first. Reduce the lease duration. Cutover on a weekend.


Cheers!

ASKER CERTIFIED SOLUTION
Shabarinath TR

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Paul MacDonald

You'll get much more control on your server than you will on your router.  

If you need (or will need) greater control, stick with Microsoft's DHCP service.  

If you want simplicity (and don't require much control), the router will suffice.
Jackie Man

Microsoft's docs recommend to move the DHCP funtion to the router.

Is there a good reason for this as opposed to moving it to the 2016 server?

We have DHCP on our physical firewall, not router nor server.

https://www.reddit.com/r/sysadmin/comments/9w5q83/dhcp_on_the_firewall_or_on_a_server/

Have a look at the above link for a lengthy discussion.

The main purpose of DHCP on the firewall is simple. If your server is DOWN, how you can troubleshoot without going to the server room and how your users can get Internet access.

For example, recently, one of our DC and file server (which is on hyper-v) is DOWN, our users still could have access to the Internet and emails on Office 365 while I could RDP to the hyper-v host from my desktop PC to fix the problems. If your DHCP is on your DC and it is DOWN, users will not be able to DO anything until you have fixed the problem.

Of course, your physical firewall has to be in HA mode so that it will automatically do failover when there is a problem.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
DP230

Agree with @Jackie, DHCP server on Router/Firewall is more stable since the devices less likely are rebooted than Servers
davebo4503

ASKER
Thanks all - I like the control I have over DHCP in Windows server - servers rarely if ever go down outside of maintenance needs, and the router or firewall could just as likely fault.