DSFW: Samify task populates users samaccountname with old name

  • Document ID:7010993
  • Creation Date:24-Oct-2012
  • Modified Date:24-Oct-2012
    • Micro Focus Products:
      eDirectory
      Open Enterprise Server
    • SUSE Products:
      SUSE Linux Enterprise Server

Environment

Open Enterprise Server 11 (OES11)
Open Enterprise Server 11SP1 (OES11SP1)
Domain Services for Windows
DSfW

Situation

When a user is samified (either in with the samify task in the provisioning wizard or moving a user into the domain) the user can not login with the current name but can login with the old name.

Samaccountname is populated with old users name

Resolution

This has been reported to development.

The samify process populates the samaccountname with the first value returned in the cn attribute.  Since cn can be a mutlivalued attribute there can be more than one cn returned.

In iManager when a user is renamed there is an option to "Save old name".  If this is done a the name will be saved as a second cn.  Since the samifing of a user takes the first returned cn (which usually is the old name) to populate the samaccountname this is the cause of the old user name being used for samaccount name.

Until a fix is released the workaround is to use iManager click on the user, click on the "other" tab and change the value in samaccountname to be that of the cn.