Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using the FRSDIAG room(from tech-net) to do diagnosis on FRS replication. The issue is its tying to check the DC's which no ,longer exist . Error being "missing server reference for the server XXXX". Where is it getting those servers from? they don't exist in AD as objects. please let me know if any extra information is required.

share|improve this question
up vote 3 down vote accepted

If you use ADSIEdit, connect to the Default Naming Context.

DC=Domain > CN=System > CN=File Replication Service > CN=Domain System Volume (SYSVOL Share)

The nTFRSMember references are under that location, and each has an attribute "serverReference".

share|improve this answer
Found them , exactly at that location. they cant be found either in AD(Objects) or in sites. So i assume these are not cleaned up during a metadata cleanup. So please answer other question, can/should these be removed manually? If they are left as it is, would it effect FRS to DFSr migration? – Darktux Jul 29 '14 at 16:37
The stale ntfrs member and subscriber references should be removed during metadata cleanup. If not, you would need to manually delete them. – Greg Askew Jul 29 '14 at 17:05

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.