Additional DC not functioning if the Primary DC is down !!
-
@IT-ADMIN said:
@Dashrender said:
Where are you running active directory users and computers (ADUC) from when you get the error?
Are you getting the error on the new AD box you made?yes i get the error in the second BOX (ADC)
OK, in the network adapter settings, what are the DNS entries?
for the sake of your testing, you should set the primary DNS to the IP of that second ADC.
Then if you still get errors, do what Coliver suggested and make sure the ADUC is pointing to the new DC, because as he mentioned, it doesn't always move over automatically.
-
@coliver said:
@IT-ADMIN said:
is it normal for the ADC not to work if it is offline and do not have FSMO or is it only me who have this issue ???!!!
Have you tried pointing ADUC at the other DC? Sometimes it becomes locked on one and you need to manually change it.
do you mean that ADUC in the ADC still locked with the PDC?? if yes how i can change to read from the ADC database ??
-
@IT-ADMIN Right-click Active Directory Users and Computers and click Change Domain Controller.
-
@Dashrender said:
@IT-ADMIN said:
@Dashrender said:
Where are you running active directory users and computers (ADUC) from when you get the error?
Are you getting the error on the new AD box you made?yes i get the error in the second BOX (ADC)
OK, in the network adapter settings, what are the DNS entries?
for the sake of your testing, you should set the primary DNS to the IP of that second ADC.
but let us suppose the PDC is down, how the ADC see it ??
-
You also have some term confusion here.
There is no more PDC. Sure there is a FSMO role called PDC emulator, but it's just that - an emulator.
Assuming your other domain controller is Windows 2000 or newer, both DCs are equal in the eyes of the domain.
It's better to call them old DC and new DC or DC1 and DC2.. you pick a name that is meaningful for you. -
What version of AD/Windows Server are you running?
-
@IT-ADMIN said:
@Dashrender said:
@IT-ADMIN said:
@Dashrender said:
Where are you running active directory users and computers (ADUC) from when you get the error?
Are you getting the error on the new AD box you made?yes i get the error in the second BOX (ADC)
OK, in the network adapter settings, what are the DNS entries?
for the sake of your testing, you should set the primary DNS to the IP of that second ADC.
but let us suppose the PDC is down, how the ADC see it ??
Windows will eventually time out on the primary DNS and switch over to using the secondary DNS that you list.
So if you want, you can have the Primary point to your old Domain Controller, and have the secondary DNS point to your new Domain Controller. It should still work, though you might have some lag until the switch takes place internally.
-
@Dashrender said:
You also have some term confusion here.
There is no more PDC. Sure there is a FSMO role called PDC emulator, but it's just that - an emulator.
Assuming your other domain controller is Windows 2000 or newer, both DCs are equal in the eyes of the domain.
It's better to call them old DC and new DC or DC1 and DC2.. you pick a name that is meaningful for you.sorry i mean by PDC: primary DC
-
@coliver said:
What version of AD/Windows Server are you running?
both are windows server 2008 entreprise R2
-
@IT-ADMIN said:
@Dashrender said:
You also have some term confusion here.
There is no more PDC. Sure there is a FSMO role called PDC emulator, but it's just that - an emulator.
Assuming your other domain controller is Windows 2000 or newer, both DCs are equal in the eyes of the domain.
It's better to call them old DC and new DC or DC1 and DC2.. you pick a name that is meaningful for you.sorry i mean by PDC: primary DC
that's still a misnomer - there is nothing really primary about it. it's just the first. And sure it holds the FSMO roles, but those can be moved at will, and even seized if the need arose.
-
@IT-ADMIN said:
@coliver said:
What version of AD/Windows Server are you running?
both are windows server 2008 entreprise R2
Wow - hefty licenses there.
-
-
you launch it first, then change it at the top inside ADUC.
-
@Dashrender said:
you launch it first, then change it at the top inside ADUC.
great, i can see it now but i do not know what to type in :
-
type in the name or IP of the new DC.
-
i think since the OK button is not activated, the DC2 is not seeing itself as a DC
-
Did you run DCPromo on the new Domain Controller so that it actually became a DC?
-
With the working DC online, when you go to ADUC and look under the Domain Controllers OU, do you see both servers?
-
@Dashrender said:
Did you run DCPromo on the new Domain Controller so that it actually became a DC?
yeah off course, and choose it to be global catalog and DNS
-
@Dashrender said:
With the working DC online, when you go to ADUC and look under the Domain Controllers OU, do you see both servers?
yeah in DC1, i can see in both DC in domain controllers OU
