In the previous chapters, we have shown you how to configure a Management Agent for SQL, Active Directory, and MIM Portal. We wrote a simple rules extension for the SQL (HR) Management Agent to generate a unique account name, and generated the display name by concatenating two attributes, the first name and last name. A Metaverse rules extension was created to provision objects to the Active Directory connector space. Run profiles were used to copy the data from the HR system to its connector space, into the Metaverse (called a projection), out to the Active Directory connector space (referred to as a provision), and then out to Active Directory.
As we have it now, the Active Directory objects have minimal information: sAMAccountName
, userPrincipalName
, and a password. The Active Directory accounts are enabled by setting the userAccountControl
attribute, and the pwdLastSet
attribute is set to 0
. Look back at Chapter 3, MIM Sync Configuration, and you will...