Resolution
fact
Directory and Resource Administrator 6.x
symptom
The LastNameFirstPre.vbs trigger does not work if either the first or the last name of the cloned user account is the same as the template account.
symptom
When cloning a user account if the first name of the account being cloned is the same as the first name of the template account, the LastNameFirstPre.vbs trigger updates the CN field with only the last name.
cause
This problem occurs if either the first name or last name (givenName or SN) remains the same as the template account when cloning a user account. The GUI does not pass in any information to the Varset. The script looks for a property in the Varset, which is not available which causes the trigger to give inconsistent results. The reason that the property is not passed is done to optimize performance and not reapply properties that have not changed.
fix
To resolve this problem, the script can be modified to use "In.User" varset property to get to the user that is being copied. The script will then gather all of the properties of the user from the Active Directory directly rather then depending on the GUI to pass it in.
Directory and Resource Administrator 6.x
symptom
The LastNameFirstPre.vbs trigger does not work if either the first or the last name of the cloned user account is the same as the template account.
symptom
When cloning a user account if the first name of the account being cloned is the same as the first name of the template account, the LastNameFirstPre.vbs trigger updates the CN field with only the last name.
cause
This problem occurs if either the first name or last name (givenName or SN) remains the same as the template account when cloning a user account. The GUI does not pass in any information to the Varset. The script looks for a property in the Varset, which is not available which causes the trigger to give inconsistent results. The reason that the property is not passed is done to optimize performance and not reapply properties that have not changed.
fix
To resolve this problem, the script can be modified to use "In.User" varset property to get to the user that is being copied. The script will then gather all of the properties of the user from the Active Directory directly rather then depending on the GUI to pass it in.
This issue is resolved in Directory and Resource Administrator (DRA) 7.0 and later. The LastNameFirstPre.vbs script in the DRA Software Development Kit has been modified.
Additional Information
Formerly known as NETIQKB33138