I have a provisioning application that at two different stages contacts AD and 
manipulates
an existing account object via LDAP to change its sAMAccountName and 
userPrincipalName
and later via ADSI, creates a new account object with the old values.

Problem exists with replication, the create always fails as its not performed 
late enough after
the original account is manipulated and therefor an account exists if it hits a 
new dc.

What programmatic means can I trigger an immediate replication of the account 
object, and
invalidate the old data? A lockout does this, but via ldap I am not aware of a 
means to do this
elegantly?

Anyone have any insight to this?
jlc

Reply via email to