OK, do something like this to display the metadata so you get a feel for the output.
repadmin /showobjmeta <myDC> <CN=joe,OU=Accounts,DC=foo,DC=bar,DC=com> Then do it across all your DCs for that object repadmin /showobjmeta * CN=joe,OU=Accounts,DC=foo,DC=bar,DC=com I piped to findstr to get a single attribute in a crude table for comparison in the final example repadmin /showobjmeta * CN=joe,OU=Accounts,DC=foo,DC=bar,DC=com | findstr /I displayname Output is in the form of: Loc.USN Originating DSA Org.USN Org.Time/Date Ver Attribute 37768474 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 1147664634 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 1140593770 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 1281290025 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 1092592196 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 96116242 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 139373319 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 168876012 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 409381869 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 426794781 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 36359287 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName 264823683 MySiteName\MyDCName 168876012 2015-08-05 15:41:53 1 displayName This shows that on all the DCs in the environment (the *) the USN (Update Sequence Number), attribute version # and timestamp are all the same, e.g. that attribute is converged From: [email protected] [mailto:[email protected]] On Behalf Of David McSpadden Sent: Friday, November 20, 2015 11:26 AM To: [email protected] Subject: Re: [NTSysADM] RE: DC's not getting updates ************************************* Yes A single freaking object I'll fix the dcdiag parm. I am also creating the log to show no issues at that time. Cya It's kind of hostile around here lately. Sent from my iPhone On Nov 20, 2015, at 1:50 PM, Free Jr., Bob <[email protected]<mailto:[email protected]>> wrote: No need for all that. The logs and diagnostic tools will show you what is not playing nice. Have you looked at the DS logs? If repadmin and dcdiag aren't barking at you, and the event log has no errors, there's a good chance that this may be a problem of perception. The original symptom is that one single object does not appear to be converged across the directory. Is that all you are trying to get to the bottom of? Do you have evidence of a more widespread problem? If it's just that object, zero in on the metadata P.S. If you want to test all your DCs quickly it's easier to use dcdiag /e [/v] > blah.log From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Friday, November 20, 2015 9:52 AM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] RE: DC's not getting updates ************************************* IPv6 up and running on the 2008's and 2012's. Here is what I am going to do going forward. I am going to schedule this: ping 120314VMDC1201>output.log ping 120614VMDC1201>>output.log ping 0810123404XB44>>output.log ping 0810123404XM66>>output.log ping 0304090304ZU55>>output.log repadmin /showrepl>>output.log repadmin /replsummary>>output.log dcdiag /s:120314VMDC1201 /v>>output.log dcdiag /s:120614VMDC1201 /v>>output.log dcdiag /s:0810123404XB44 /v>>output.log dcdiag /s:0810123404XM66 /v>>output.log dcdiag /s:0304090304ZU55 /v>>output.log Then review the output.log each morning. Should those commands find me anything that is not playing nice in the DC's? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kennedy, Jim Sent: Friday, November 20, 2015 8:26 AM To: '[email protected]<mailto:[email protected]>' <[email protected]<mailto:[email protected]>> Subject: RE: [NTSysADM] RE: DC's not getting updates Check and see if someone disabled IPV6. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Thursday, November 19, 2015 10:36 PM To: [email protected]<mailto:[email protected]> Subject: Re: [NTSysADM] RE: DC's not getting updates Dcdiag tested good I'll dig deeper in the morning. Sent from my iPhone On Nov 19, 2015, at 10:19 PM, Andrew S. Baker <[email protected]<mailto:[email protected]>> wrote: I just had to address an issue like that recently, where DCDIAG showed RPC errors (1722), which turned out to be one DC that wasn't listening on an IPv6 interface... Fun times. ASB http://XeeMe.com/AndrewBaker<https://urldefense.proofpoint.com/v2/url?u=http-3A__xeeme.com_AndrewBaker&d=BQMFAg&c=hLS_V_MyRCwXDjNCFvC1XhVzdhW2dOtrP9xQj43rEYI&r=TA_mjBT8bS0r8rLrnubGjA&m=IvHVQWyE8ZS7Fe6mK-w6lbfgCUsyFDHDEst3cWRUR3I&s=Y9759_k7DuISw01YIIDdNhOC-N70I9DYl8BpB7ZtoiA&e=> Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market... GPG: 1AF3 EEC3 7C3C E88E B0EF 4319 8F28 A483 A182 EF3A On Thu, Nov 19, 2015 at 5:27 PM, Michael B. Smith <[email protected]<mailto:[email protected]>> wrote: I'd start with dcdiag. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of David McSpadden Sent: Thursday, November 19, 2015 4:57 PM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] DC's not getting updates I have 5 DC's 2 2012R2's (One is the Primary) 1 2008 1 2008 Read Only And a 2003 (I know, it is going away as soon as I can get the last app off of it.) I made a change to a user account on a 2012r2 the other day (Name change). It still had not made it to the 2008 server after 48 hours but when I look in repadmin syncing looks fine? Where should I be looking for something like this? This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
