Domain Controller On Other Site?

[FN-GM]

Hi,

 

2 sites connected by a 100mb point to point link. The site concerned has about 100 Windows clients. I am planning on hosting a SCCM DP, File Server and Print at that site. Would you put a DC on that site? Im tempted to say no as authentication isn't going to use a lot of bandwidth.

 

What are your thoughts?

 

Thanks

[snagrat]

Could consider a RODC to help with authentication that occur regularly at that site.

 

Doesn't need to be very powerful so if there is space for an extra VM

[FN-GM]

Its not the space its the licences. I don't have a datacenter licence for that server. So can't go over 4 VM's.

[Muz]

It all comes down to licensing cost as you say and specs of main server, don't hold me to this but I read in a tech net article that a DC was recommended for every 250 users. You also need to factor in redundancy if your services such as file shares etc are hosted elsewhere.

[Michael]

Irrelevant of the speed of the P2P, if that link goes down, no one will be able to authenticate/login. Every physical building/link should have a DC or RODC. It makes sense seeing as you are planning to have a server in some capacity on site.

[3s-gtech]

I have the same setup (though the second site also has another domain with its own DCs). I did put a DC in, simply because the link isn't 100% reliable, and plenty of other traffic uses the link (like Lync, SIMS, email, filtered traffic) so wanted to try to be more efficient. Working well at present.

[Davit2005]

We have 2 sites, the satelite site at the moment has no servers just network switches, router and telephone equipment.

 

If I were putting in a file server I would put in a DC. For 100 Workstations you could probably combine the DC with the File server, although I wouldn't mix roles if I had the choice.

 

It would make sense if there was a local file server to have a DC, people could still mostly get on with their work if the link or anything happened at the main site.

Edited January 13, 2015 by Davit2005

[synaesthesia]

We have 2 sites and have a DC on each site, also split SCCM (primary server on one site, distribution server on the other) - clients pick up addresses & software from their nearest servers.

We're on a gig fibre and have a backup 54mbps radio link but we'd rather play safe with the DCs. Also about to (well, February) introduce proper failover to DHCP so we have instant pickup from one server should the other go down (each site is vlan'd separately)

 

It might not be so important for 100 users but extra licensing won't be that much in the long run; it'll be worth the peace of mind IMO.

[john]

Agree with many above a 2nd site should have its own DC for auth and if that link is down you can keep some level of normality going assume you will do DHCP and DNS on that site as well to give it some life or you not worried if the link fails about it being usable?

[rh91uk]

I have done this before and having a second RODC on the other site; with a site with it's own routing engine (i.e. picks it's own DHCP up) really does save you in a failure.

I have also even added a file server down there too and DFS'ed it so it is replicated at the main site and the secondary site.