windows 2012 essentials server dhcp and dns

bwierzbicki
bwierzbicki used Ask the Experts™
on
Been a while since I set up a server. I'm now doing this one for an office that has 4 computers connecting to a 2012 essentials server.

While setting up I noticed there is no DHCP role configured by default and that the server is operating off of dhcp from the router.

To top it off I did a couple of quick searches and what I saw was it was designed to work that way and was ok to have the server obtaining an ip from the router along with letting it handle dns

I've got 2 clients connected now, they are new pc's no one is using and everything seems to work fine in this configuration. If no one thinks this will be a problem I might leave it as is because this office shares internet with another office and I'm not crazy about one office using the others server as dhcp (not that it matters I guess)
Last time I ran into this I didn't have control of the firewall and there was a lot of fancy stuff going on so I just assigned static ip's to the 6 or so workstations that were there.

It just concerns me because I've always been of the belief that dhcp and dns with AD was criticall to be on the server, but now Microsoft has these settings by default.

Is this ok or should I assign a static ip and make my server the dhcp server?
If it works like this I think I'd just rather leave it as is.

Thakns,
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2018
Commented:
DNS was and is essential to Active Directory. DHCP never has been, but MS DHCP is just so much easier to provide advanced options that a router that it is a common best practice.

Essentials does ha specific design changes to allow it to work in environments where a small router is managing DHCP. Soecifically, you *must* use the connect wizard to join workstations in such an environment. It installs a small client-side connector that changes DNS from whatever the router hands out to the server...EVEN if the server itself has a DHCP address that can change. So by "fixing" DNS, it allows AD to work as expected.

so, basically, do whatever you are more comfortable with. Leaving DHCP on the router or putting it on the server are both functionally fine options with essentials.

Author

Commented:
Thanks

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial