Recently a thread I’d started a long time ago about selective provisioning to the FIM MA bubbled back up to the top of the FIM Forum. At the time it provoked a lot of discussion, with the Microsoft line remaining firmly “ALL metaverse objects must be in the Portal” and many FIM users saying they didn’t see why this should be the case.
There are lots of very good reasons I can think of why you’d want some objects in the Metaverse but not in the Portal and seeing the post pop up again reminded me that I’d actually “solved” this problem long ago by the simple expedient of deleting objects that I don’t want.
I didn’t want objects without an accountName cluttering up the Portal so in my Metaverse Extension code I have:
If Not mventry("accountName").IsPresent Then mventry.ConnectedMAs("FIM").Connectors.DeprovisionAll() End If
As the Metaverse extension code seems to run after the hard-coded provisioning to the FIM MA this has the simple result of removing the unwanted objects as soon as they’re created. It didn’t particulary seem to slow things down either.