| Author |
Message |
Kiosk
Guest
|
 Posted:
Tue Jan 11, 2005 3:12 am Post subject:
New DC |
|
|
I am adding one more DC to one of my locations, because the current
two are overloaded. I am not AD expert but how will the
authentications be directed to the third DC? Do i need to do anything
to the site definition to make sure authentications requests are
properly balanced between the three DC's? |
|
| Back to top |
|
 |
ptwilliams
Guest
|
| Posted:
Tue Jan 11, 2005 3:34 am Post subject:
Re: New DC |
|
|
Through DNS. And proper configuration of sites and subnets.
If this is a remote DC, I would also make it a DNS server and ensure that
local clients point to this DC. They will then ascertain their site and
then always use this DC.
So, create a new subnet and match it with the new site, create a site and
associate the subnet with the site. Promote the DC. If the DC is in the
subnet then it will auto-add itself to the correct site; if not, you'll have
to move the DC object in sites and services into the new site. You will
also need to change the IP when you move to the other site.
If the sites are already configured, then simply promote the DC (ensuring
that the member is pointing to an internal DNS server first).
--
Paul Williams
http://www.msresource.net/
http://forums.msresource.net/
"Kiosk" <jramos@netcom.com> wrote in message
news:uhr5u01dk8c9a67f94564pap3ugfu8t06p@4ax.com...
I am adding one more DC to one of my locations, because the current
two are overloaded. I am not AD expert but how will the
authentications be directed to the third DC? Do i need to do anything
to the site definition to make sure authentications requests are
properly balanced between the three DC's? |
|
| Back to top |
|
|
Kiosk
Guest
|
| Posted:
Tue Jan 11, 2005 3:58 am Post subject:
Re: New DC |
|
|
Thanks for the quick response.
This is a DC for a local site, there is already a site definition and
with the right subnets. This new DC would be going into an existing
site that already as the subnet defined for the network where it is
going to....
I notice that one of the two existing DC's has about 5 times more
replication objects (automatically genertaed) than the other DC, so
something for some reason is not load balancing right.....I am afraid
that by adding another DC wont really help....
On Mon, 10 Jan 2005 21:34:41 -0000, "ptwilliams" <ptw2001@hotmail.com>
wrote:
| Quote: |
Through DNS. And proper configuration of sites and subnets.
If this is a remote DC, I would also make it a DNS server and ensure that
local clients point to this DC. They will then ascertain their site and
then always use this DC.
So, create a new subnet and match it with the new site, create a site and
associate the subnet with the site. Promote the DC. If the DC is in the
subnet then it will auto-add itself to the correct site; if not, you'll have
to move the DC object in sites and services into the new site. You will
also need to change the IP when you move to the other site.
If the sites are already configured, then simply promote the DC (ensuring
that the member is pointing to an internal DNS server first).
--
Paul Williams
http://www.msresource.net/
http://forums.msresource.net/
"Kiosk" <jramos@netcom.com> wrote in message
news:uhr5u01dk8c9a67f94564pap3ugfu8t06p@4ax.com...
I am adding one more DC to one of my locations, because the current
two are overloaded. I am not AD expert but how will the
authentications be directed to the third DC? Do i need to do anything
to the site definition to make sure authentications requests are
properly balanced between the three DC's? |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in