Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 896
  • Last Modified:

AD user created does not appear in other DC users and computers

Single domain-2003 Native mode AD: We created a user on a remote DC. At the headquarters and indeed at any other DC ( apart from the one in question) we cannot see this user in the OU in question in users and computers.

Looking at repadmin /showreps, it all looks fine, replication is regular and i can force a manual rep from sites and services. no Lingering objects, correct amount of objects in sysvol policies- I am scratching my head. all FSMO roles are at HQ.

The user in question cannot login.
0
Felicity_Harte
Asked:
Felicity_Harte
1 Solution
 
KenMcFCommented:
What DC did you run repadmin from?

can you run DCDiag and post results from each DC?
Also a IPConfig /all from each DC.

When you force repl through ADS&S does the object replicate or does it still not show up.

Is this user att he remote location or at the HQ.
0
 
Darius GhassemCommented:
Dcdiag will help out like Ken requested
0
 
Felicity_HarteAuthor Commented:
Thanks for your comments. the user was created at remote site in Eastern Europe. I ran Repadmin from HQ DC and remote site DC so both ends. No erorrs all Domain partition replicated.

I am wondering about DNS, there are stacks of Red errors at remote site, but if there were problems repadmin would have picked this up?

I will now do a DCDiag from both ends

many thanks

F
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Jackal_sCommented:
I have a similar situation only difference is that the other DC is W2K8. Since the day I have joined it and made it a DC, it has never pulled any users created on W2K3. I read some place, that we need to restat the Net Logon service and re-check DNS Setup. It's all down to some DNS misconfiguration I suspect . I am going to try it. Will keep you posted. Try if it works for you.
0
 
AwinishCommented:
Run repadmin /syncall /AEPD to sync all the domain controller in the forest & see then the user is displaying in other dc.


0
 
Vishal PatelCommented:
The replication is instantaneous if both the DCs are in single site.
If you have created multiple sites, you need to setup site links for replication of data to work it automatic.
Go through these:
http://technet.microsoft.com/en-us/library/dd277429.aspx
http://www.informit.com/articles/article.aspx?p=21472

If you need more help on site and link creation, revert back.

0
 
Felicity_HarteAuthor Commented:
It was a lingering object on the remote DC. Even though repadmin was reporting success at both ends, I found out that there was some lingering objects on remote DC. I am about to clean these, then the user account should replicate to all other DC's
0
 
Felicity_HarteAuthor Commented:
This solution worked.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now