Resolution
goal
Can I configure the default OU container for user create operations in the Web Console?
fact
Directory and Resource Administrator 6.60
symptom
When performing a user clone operation with the Web Console client, the default OU for the cloned account is not the same OU as the template account.
cause
The Web Console uses cookies to populate this field. The cookies remember the last OU used during the clone process, regardless of the OU associated with the template account. If the last clone process in the Web Console created a user account in a different OU than the template account, that is the OU that will be used by default by the Web Console for the next clone operation.
fix
This issue is addressed in Directory and Resource Administrator 7.0. DRA 7.0 now uses the template account information to populate the OU instead of using a cookie to populate the OU.
Can I configure the default OU container for user create operations in the Web Console?
fact
Directory and Resource Administrator 6.60
symptom
When performing a user clone operation with the Web Console client, the default OU for the cloned account is not the same OU as the template account.
cause
The Web Console uses cookies to populate this field. The cookies remember the last OU used during the clone process, regardless of the OU associated with the template account. If the last clone process in the Web Console created a user account in a different OU than the template account, that is the OU that will be used by default by the Web Console for the next clone operation.
fix
This issue is addressed in Directory and Resource Administrator 7.0. DRA 7.0 now uses the template account information to populate the OU instead of using a cookie to populate the OU.
Additional Information
Formerly known as NETIQKB29894