2013/5/15 SB MK <[email protected]>: > > Hi, > I'm currently syncing parts of a SUN DS to an AD, using groupOfUniqueName on > the SUN side to feed AD user accounts, located in several OU. > It's working flawlessy, but I'm thinking about a forthcoming problem : how > to deal with users moving between OUs using LSC ? > If I change the SUN groups, the AD account might be deleted and recreated, > with a new SID. Not great. > I've tried without any cleaning process, and it fails : an account with the > same UID already exists, in another OU. > What's the trick to mimick a "move" operation, as one can do with the AD > console ?
The only solution is to have a single task where you can set the main identifier (means you can build the DN in the correct OU with information on the source entry). If the DN change, LSC will rename the entry (modrdn) instead of delete/add it. Clément. _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
