Changes have been made to an attribute in the Active Directory Schema using a schema editing tool such as schmmgmt.msc
The changes are visible in Active Directory Users and Computers and ADSIEdit but the ARS MMC is not showing the changes.
This is by Design. ARS is not aware of the changes that have been made as it is running on a cached copy of the schema information that existed when the service was started.
The Schema must be reloaded via schmmgmt.msc and the ActiveRoles Server service must be restarted in order for the changes to be detected during ARS schema enumeration.
Quest does not provide support for problems that arise from improper modification of objects using ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client.
The following statement about ADSIEdit was taken directly from Microsoft:
Warning: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
If you have more than one ActiveRoles Server instance, you may be required to stop all instances and start one at a time for the changes to be picked up.