?
Solved

GC not responding,

Posted on 2012-08-18
6
Medium Priority
?
701 Views
Last Modified: 2012-08-18
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
0
Comment
Question by:MAS
  • 3
  • 3
6 Comments
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38307589
How many DC's do you have in the domain ?
Did you enable GC option from Sites&Serives and restart the server after that ?
Any specific events on the GC ?

- Rancy
0
 
LVL 28

Author Comment

by:MAS
ID: 38307610
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
0
 
LVL 52

Accepted Solution

by:
Manpreet SIngh Khatra earned 2000 total points
ID: 38307612
Good to hear that :)

Check this article once
Domain Controller Cannot Become Global Catalog
http://www.experts-exchange.com/Software/Server_Software/File_Servers/Active_Directory/Q_27393654.html

- Rancy
0
Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

 
LVL 28

Author Comment

by:MAS
ID: 38307617
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
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38307636
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
0
 
LVL 28

Author Closing Comment

by:MAS
ID: 38307659
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
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
This video discusses moving either the default database or any database to a new volume.
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Suggested Courses

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question