Thursday, February 14, 2013

Secrets of the Metaverse Part 1

Many FIMsters wonder about the Metaverse and how works, how the data is stored. In this series I will reveal the secrets of the Metaverse. Parts 1-5 (links live but post yet to come)
  1. What is the Metaverse?
  2. How is the Metaverse data stored?
  3. Is there a limit to how many Metaverse attributes I can have?
  4. Has access to the metaverse gotten faster with recent releases?
  5. How do I safely query the metaverse?
  6. Added (Aug 5 2015): How Many Metaverse Attributes can I have?
Forefront Identity Manager 2010 R2 SP1 (and its predecessors) can be classified as a MetaDirectory based Identity Management Solution. A MetaDirectory collects, aggregates, and stores data from various directories and data sources, such as Active Directory and your HR database.
The Metaverse is the heart of FIM's MetaDirectory. As an implementer of FIM you customize the data model, you decide what object types and attributes you need.


Unknown said...

Great explanation. This really came in handy for troubleshooting.

David Lundell said...

I am so glad it was of use

Aditya said...

I am using MV extension to create users in AD from FIM.
Need to flow password to AD which is any Random number say "$random123"
This attribute flows to AD but can be viewed in account preview etc or the attribute value can be seen. How can we flow the password value so that it can not be viewed in metaverse etc by any one like ********** ?

David Lundell said...

using the out of the box AD Management agent we can't hide the workflow parameter that is passed into the ERE.