All versions of Centrify DirectControl on Microsoft Windows 2000, 2003 (32 and 64-bit systems)
Using Active Directory Users and Computers and "Finding" a user, computer or group from Active Directory, the Centrify Profile tab does not appear when the properties dialog for the object is opened from the search results.
To extend an AD user object to have Centrify profile tab, we have used two approaches.
1) Using display specifier.
2) Using extension snapin.
The one that we show Centrify profile extension from our user node within our snapin is done by extension snapin approach.
The property sheet hosting all the property pages is owned by our MMC snapin. That's why we can add whatever property page we like *IF* the property page is launched from the user node in our MMC console's result pane.
In order to provide a consistent user experience, when we are finding an object from Active Directory, Centrify console is calling Microsoft's object picker. Within the object picker, user can also launch the property dialog from the searched results. However, the property dialog launched in this way is actually owned by Microsoft's object picker. Microsoft only allows third party to extend the property page by using display specifier.
The display specifier by default can only be updated by the domain administrator of the root domain or the enterprise admin. You can also ask enterprise admin to grant you permission on the display specifier container.
Then, you can use your own account to run that VBscript.
The update of the display specifier is reversible. The only purpose of updating the display specifier is to tell the client component what plugin it should load when displaying a particular AD object. If the plugins cannot be
found, it will just skip it.
3. Run the displayspecifier.vbs script.