WMI Deprecated from AAD Connect from version 1.4.18.0

For reference, the following 2 articles show how to reinstate the WMI namespaces for MIM and AAC Connect respectively, but these pre-dated the deprecation from AAD Connect:

• https://social.technet.microsoft.com/wiki/contents/articles/13286.fim-reference-how-to-register-the-fim-wmi-provider.aspx
• https://jorgequestforknowledge.wordpress.com/2014/09/21/change-install-of-the-azure-ad-sync-service-throws-wmi-namespace-error/

It doesn't appear that the PS reference is published online, but there is this: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler - and this does NOT provide a practical way of selectively running MA operations individually.

Attaching logs referencing the "invalid namespace" exception:

UNIFYNowLogFile

The test of Agent AADConnect Agent (5816b02b-a117-423c-b8ae-ad28a7c0f009) failed with message:
System.Management.ManagementException: Invalid namespace 
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Unify.Product.EventBroker.MIMAgent.TestConnection()
   at Unify.EventBroker.Agents.Audit.AgentAuditingDecoratorBase.TestConnection()
   at Unify.Product.EventBroker.AgentEngine.Notify(ITestAgentConnectionMessage message)

Hey Bob,

At the moment, you're correct - UNIFYNow will not support AAD Connect from version 1.4.18.0 onwards. 

If there's a requirement for support we can investigate, but given the agent is shared across AAD Connect and MIM, there would be significant effort to split these up and offer the capability of AAD Connect integration without impacting the existing MIM integration functionality.

Thanks for confirming Matt - I suggest the https://voice.unifysolutions.net/knowledge-bases/8/articles/2731-unifynow-for-dirsync-or-azure-ad-connect article (which preceded the configuration for our customer when Microsoft changed the database name to ADSync but retained the microsoftidentityintegrationserver namespace) needs to be updated accordingly.  I will advise our customer that we should discontinue use of UNIFYNow to operate AAD Connect given there is no longer a compelling need to do so.  I just needed to confirm first.