A Forum reader recently asked:
“We are looking at recertifying our Notes environment. In doing so, we will be creating everyone using the unique org unit – which will be their employee ID (unique across all environments).
This is fine for the recertification of new users who are matched, but we also need to create new users using the Unique Org Unit. Here is where I am running into difficulty.
The shim uses the OU held within the certifier ID used during registration. As far as I can tell, there is no allowance for using the Unique Org Unit during registration by sending an XML element with the create document, etc. Certainly it isn’t mentioned in the documentation
for the driver.”
And here’s the response from Perry Nuffer …
Check this URL and search on ‘extended-ou’:
Below is a sample rule that you may want to use to experiment with the ‘extended-ou’ custom parameter. It demonstrates the usage of this ‘extended-ou’ custom parameter in the
Notes Driver. You will need to replace the “UniqueOrgUnit” text with whatever is appropriate for your system.
<rule> <descriptionInsert extended-ou XML attribute for Lotus Notes Naming</description> <conditions> <and> <if-operation op="equal">add </if-operation> <if-class-name mode="nocase" op="equal">User</if-class-name> <!-- check IDVault containment location --> <!-- <if-src-dn op="in-container">LotusNotes\Users\Active </if-src-dn> --> <!-- <if-src-dn op="in-subtree">LotusNotes\Users</if-src-dn> --> </and> </conditions> <actions> <do-set-xml-attr expression="../add[@class-name='User']" name="extended-ou"> <arg-string> <token-text>UniqueOrgUnit</token-text> </arg-string> </do-set-xml-attr> </actions> </rule>