ADMT ver2 - users not being added to correct groups

[John]

After successfully migrating 40-50 users, we are now getting the
following error messages upon migrating users (from NT4 domain to W2K
AD Domain):

Cannot add LDAP://dc1.childdomain.parentdomain.local/CN=userx,OU=Corporate,DC=childdomain,DC=parentdomain,DC=local
to CN=Groupx, because
LDAP://dc1.childdomain.parentdomain.local/CN=userx,OU=Corporate,DC=childdomain,DC=parentdomain,DC=local
has not been migrated to the target domain. The user name could not
be found.

The groups were originally migrated empty a couple of weeks ago and up
to recently, the users were being added to the correct groups in the
target AD domain. Replication seems to be working just fine.

Any ideas? Does anyone know how I can direct ADMT to use on
particular domain controller?

 

[John]

After successfully migrating 40-50 users, we are now getting the
following error messages upon migrating users (from NT4 domain to W2K
AD Domain):

Cannot add LDAP://dc1.childdomain.parentdomain.local/CN=userx,OU=Corporate,DC=childdomain,DC=parentdomain,DC=local
to CN=Groupx, because
LDAP://dc1.childdomain.parentdomain.local/CN=userx,OU=Corporate,DC=childdomain,DC=parentdomain,DC=local
has not been migrated to the target domain. The user name could not
be found.

The groups were originally migrated empty a couple of weeks ago and up
to recently, the users were being added to the correct groups in the
target AD domain. Replication seems to be working just fine.

Any ideas? Does anyone know how I can direct ADMT to use on
particular domain controller?

P.S. Microsoft was able to duplicate the issue and it is a bug which
will be fixed in the next Service pack for W2K3. When the admt runs
against one particular domain controller- everything works great.
When it goes against any of the others, I get the problem above.
Again, replication between DC's is good. Note: The FSMO roles of the
good server are IM, RID, and PDC. MS says it shouldn't matter but I
wonder...