Craig Martin

Learning and sharing

1 minute read

For years we’ve enjoyed access to sync functionality via WMI (pronounced ‘Whammy’), all the way back to MIIS. The Windows Management Infrastructure provider for the sync engine provided some useful functionality, including:

  • Start a management agent run or stop an existing management agent run.
  • Get the results of a management agent run.
  • Get statistical information about the connector space or metaverse.
  • Set or change passwords.
  • Get information about FIM Synchronization Service.
  • Search for a connector space object with a specified domain and account name in a global address list, a Windows NT 4.0 domain, or in Active Directory Domain Services (AD DS).
  • Search for a connector space object with a specified domain and user principal name in a global address list, a Windows NT 4.0 domain, or in AD DS.

The WMI provider lives on in MIM but goes away in AAD Connect starting in version 1.4.18.0

Customers should be informed that the deprecated WMI endpoints for MIIS_Service have now been removed. Any WMI operations should now be done via PS cmdlets.

So heads up! If you have been programming against the WMI provider then you will need to refactor before upgrading to any version newer than 1.4.18.0 (ask me how I know). The ADSync PowerShell module does have a ton of cmdlets available, and I’ll be sharing experiences with them in the coming posts.

You May Also Enjoy

Find MIM Active Workflow Definitions

less than 1 minute read

Need to find the workflow definitions that are actually configured to be active? It’s a good way to find configuration bloat that could be cleaned up.

Event Log Entry Count By Severity

less than 1 minute read

Visualizing the count of Event Log events on a computer can be helpful in some cases: starting to investigate an issue - does the issue coincide with an i...