Your company network includes Forefront Identity Manager (FIM) 2010. You add a new object type from the FIM Portal. You need to ensure that the new object is managed by the FIM Management Agent…

Refreshing the schema is done to detect new attributes or object types exposed by the connected data source, not to configure how a newly selected object type is synchronized into the metaverse.

Only one FIM Service MA is needed per FIM Service instance; creating an additional FIM Service MA for a single object type is architecturally incorrect and unnecessary.

In FIM 2010, after selecting a new object type on the Select Object Types page, you must proceed to the Configure Object Type Mappings page within the FIM MA properties to map the new connector space object type to an existing (or new) metaverse object type. Without this mapping, the synchronization engine has no way to project or join objects of that type into the metaverse, making management of the object impossible. This is a mandatory sequential step in the FIM MA configuration wizard.

The ObjectTypeDescription extended attribute of the synchronization filter controls which object types are filtered out of synchronization, and adding an object there would not configure the MA to manage it - it would affect filtering behavior, not object type mapping.