Evenin' All,
Had the pleasure of jumping into warm waters at work today with a client
where an authoritative restore was performed a few weeks ago following
an U being mistakenly deleted. Under this U were a number of users
whom have yet to be wholly migrated to AD but are still using their
legacy NT4 accounts to access Exchange 2003 (i.e. disabled user in AD)
before they are fully migrated to AD (Windows XP) all DCs are running
Win2K3SP1 I've discovered a number of mismatches between certain
attributes of thes user objects according to the DC you query
<plugFor example, if I use the infamous ADFIND tool </plug>
Using the following syntax I query the homeMDB attribute on each DC
Syntax:
for /f %%a in (mydclist.txt) do adfind -h %%a:389 -b
"U=RU,DC=MYAD,DC=ACME,DC=CM" -c -u ACME\admin -sort name "dn"
-f "&(objectClass=user)(!(homeMDB=*))"
The following information is returned (paraphrased)
AdFind V01.30.01cpp Joe Richards (joe (AT) joeware (DOT) net) January 2006
Using server: gbsrv01.myad.acme.com:389
Directory: Windows Server 2003
1804 returned
Using server: gbsrv002.myad.acme.com:389
Directory: Windows Server 2003
1804 returned
Using server: ussrv001.myad.acme.com:389
Directory: Windows Server 2003
2669 returned
Using server: itsrv001.myad.acme.com:389
Directory: Windows Server 2003
1804 returned
Using server:
Directory: Windows Server 2003
4260 returned
Using server: ussrv002.myad.acme.com:389
Directory: Windows Server 2003
2670 returned
Using server: essrv001.myad.acme.com:389
Directory: Windows Server 2003
4146 returned
Using server: sesrv001.myad.acme.com:389
Directory: Windows Server 2003
1804 returned
Using server: frsrv001.myad.acme.com:389
Directory: Windows Server 2003
4090 returned
etc
Interestingly, in certain cases, particular servers, not necessarily in
the same site, return the same value of objects (not 1804)
Given that the query is looking for user IDs with empty homeMDB, less is
good and given that 1804 objects returned (seems) to indicate that
these are the DCs with the correctly populated homeMDB attributes, my
questions are thus:
(1) Is a USN problem associated with the restore a possible cause here?
(2) Given that a REPADMIN /showutdvec on all DC's reveals no USN
inconsistencies as such, and that replication is working correctly, how
was this situation likely to come about?
(3) What's preventing successful update of these attributes (dumb
question maybe but I want to be certain)
(4) (Big If) but can I force replication from my suspected good entries
to overcome this issue
Granted, there's a paucity of information to go on but I'll try and
elaborate as the night goes along :-)
Many thanks,
Mylo