I have had to fix Metaverse objects that, for some unknown reason, aren’t connected to all Management Agents. There was a specific case where user objects were not created in Active Directory and the only fix seemed to be disconnect all of the MAs to allow the MV object to be deleted. Then, most times, the next sync would join them all and provision the AD user object.
The “Get-Records” function finds all the MV objects that meet the supplied criteria. In our case that is based on employeeStatus and employeeType. The function returns a PSCustomObject that has meteverse data including the connector space ID for each connector.
The “Evaluate-Records” function identifies the bad records by counting the number of connectors and capturing any that don’t have all four and returns a PSCustomObject of all broken meteverse objects.
The “Remove-Connectors” function will disconnect each of the existing connectors that do exist so that the meteverse deletion rule will delete the meteverse object.
The “Run-Sync” function executes the run profiles.
This script will require the Lithnet MIIS Automation module.