I've been seeing a problem where Context.rename does not always move an object (in this case a user object) in active directory. No exception is thrown, but the object remains at the old DN. The request seems to be ignored.
Is this a known issue? Some thing odd with our server / code? The code works fine over multiple LDAP servers, but in AD it moves some objects and, for others, nothing (including no error) happens. Haven't figured out yet why some are moved (as expected) and some are ignored.
Is there a superior way to accomplish this in AD (using JNDI)? The moves always happen under the same domain, so they are only changing OUs.
Any help would be appreciate.
Is it maybe a timing problem? LDAP isn't bound to do things exactly when you say, it can add some timing 'slop' to suit itself. It's not transactional. However I would expect to see the change in effect within not too many seconds.