I'm sure the schema attribute associated with the PIN is part of the User's record, just like the DTMFAliasId and such are for Unity attributes. Here are the ldif files used to update the schema:
1. C:\dcdsrvr\run\dcx500\config\AD\at_schema.ldif? Adds the attributes for schema updates
2. C:\dcdsrvr\run\dcx500\config\AD\oc_schema.ldif?Adds the object classes for schema updates
3. C:\dcdsrvr\run\dcx500\config\ContainersAndSysProfiles.ldif?Creates the default containers and system profile
4. C:\dcdsrvr\run\dcx500\config\SpecialUserProfiles.ldif?Creates the profiles for Cisco-specific special users
5. C:\dcdsrvr\run\dcx500\config\SpecialUsers_AD.ldif?Creates the Cisco-specific special users
You can use ADSIEdit to view the cisco attributes for a user as well as inspect the ldif file, for example Unity attributes begin with ciscoescbu followed by the specific name. We are using CallManager's own DC directory for our MeetingPlace Express, otherwise I would have looked for the specific nomenclature for you and posted it here.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.