Unity Migration Blog

I added ncsuAccount as an auxiliary class of the user class. This was done to make it easier and more straightforward to use the additional "ncsu" attributes.

The ncsuAFSPath attribute is currently the only attribute we have added to the schema. This attribute was added to the ncsuAccount class, but the ncsuAccount class was not added to the user class.

Given this configuration, it is still possible to utilize the ncsuAFSPath attribute but you need to explicitly add "ncsuAccount" to the objectClass attribute on user objects. Also, the additional attributes do not show up in ADSI Edit or when you enumerate the available attributes using scripted methods.

Adding ncsuAccount to the user class allows you to set the ncsuAFSPath attribute without having to do or know any additional details. It also causes the new attribute to appear in ADSI Edit and when enumerating available attributes.

This change is reversable. I did the following as a test:

• Added ncsuAccount as an auxiliary class of user
• Created a new user and populated the ncsuAFSPath attribute (ncsuAccount was not added to objectClass)
• Removed ncsuAccount from the user class (AD allowed me to do this without any errors)
• Checked the user account and the ncsuAFSPath attribute was still available
• Tried to create another user account while populating the ncsuAFSPath attribute. AD would not allow this because ncsuAccount was neither an auxiliary class of user nor did I add it to objectClass for the account being created.
• Added ncsuAccount back as an auxiliary class of user

I will be populating the ncsuAFSPath attribute for the user accounts under "Unity Users" today.