windows 2012 essentials server dhcp and dns

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,
bwierzbickiAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bwierzbickiAuthor Commented:
Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.