M A
asked on
GC not responding,
I installed and additional DC but exchange is nor able to connect this.
I came to know that it is not advertising as GC.
Please help
I came to know that it is not advertising as GC.
Please help
ASKER
I opened this question for you and to add a solution to EE database
your solution provided in question helped me to fix the GC issue.
I removed the orphaned DCs and removed the domain which we had trust before from ADSI and restarted the FSMO holder. Then demoted the ADC and promoted back to GC.
Just write the same solution down here
your solution provided in question helped me to fix the GC issue.
I removed the orphaned DCs and removed the domain which we had trust before from ADSI and restarted the FSMO holder. Then demoted the ADC and promoted back to GC.
Just write the same solution down here
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I suggest you write what is written in that question so that It will be more clear from this question only. No need to go to another question. Just write about orphaned domain removal.
If you think no need just ignore this comment I will accept the above comment
If you think no need just ignore this comment I will accept the above comment
I would try to take out some time and try write an article for it :)
So to remove a orphaned DC object you need to use Ntdsutil command line to remove that DC object information from the AD database.
Run the command to check any old DC or Domain instance information and remove it.
Make sure all FSMO roles are with a functional DC\GC.
Try to re-promote the DC to a GC.
- Rancy
So to remove a orphaned DC object you need to use Ntdsutil command line to remove that DC object information from the AD database.
Run the command to check any old DC or Domain instance information and remove it.
Make sure all FSMO roles are with a functional DC\GC.
Try to re-promote the DC to a GC.
- Rancy
ASKER
Removed the greyed out trusts from ADSI and removed the orphaned domains and instances using ntdsutil. Repromoted the DC. Now exchange working fine with the new DC.
Many thanks to Rancy
Many thanks to Rancy
Did you enable GC option from Sites&Serives and restart the server after that ?
Any specific events on the GC ?
- Rancy