MIM Event Broker Forum
Welcome to the community forum for MIM Event Broker.
Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.
I know this is somewhere on the roadmap, but I thought I'd give you a specific example of how I would like to use this to lookup the Operation List name for a corresponding guid from within a PowerShell script. I know this method exists on the WCF endpoint because it is exposed in the WSDL. However it is not a simple exercise to access this from PowerShell.
For the time being I have a work-around which relies on looking up the Event Broker registry key to determine the extensibility file path, then querying the operations extensibility xml directly. However the limitation here is that this will only work if the script is running locally on the Event Broker service host.
Now that this has been proven in Identity Broker we'll look at this for MIM Event Broker.
Just upgraded UNIFYNow (22.214.171.124 to 126.96.36.199) after upgrading broker (188.8.131.52 to 184.108.40.206) and alot of the UNIFYNow operations lists that are supposed to trigger IDB operations lists are failing all with the same error.
The field the error message is quoting was removed in v4.0.3. Please check for and remove any old patches, as we discuses in your earlier issue.
Event Broker agent wizard leads to "The server is unwilling to process the request" exception for specific OU
When an OU is configured for an AD agent that is NOT the domain root (e.g. "OU=Employees,DC=mim2016,DC=local") we get the following exception when the generated incoming operation list is activated:
Operation faulted: The server is unwilling to process the request. - Please see the log viewer for more details.
This is because the AD Sync Changes check operation uses the full DN for the "Domain" property instead of the DC part only (i.e. "DC=mim2016,DC=local").
To avoid this error the AD sync changes operation needs to extract the DC DN from the full DN supplied.
Fixed in 4.0
Presently the TO address supports only a single target email address. However this field is multi-valued in the sendmail API and the logger could easily be extended to support this. There is no tooltip on this field so it was not intuitive that this restriction applied - however attempts using "," and ";" delimiters both failed. Work-arounds include setting up multiple loggers, or using a distribution list. However there are times when this would still be handy - especially when d-lists are not easily modified or the requirement is only temproary.
Added ability to have logs emailed to multiple addresses. Will be included in the next release.
With the release of Ryan Newington's latest Lithnet miis-powershell module it occurred to me that it may be possible in some scenarios (e.g. full imports vs. delta imports) to leverage the progress bar idea for the Event Broker console.
To be investigated during UI rewrite.
The native AD MA for the FIM Sync service has long had an optional configuration section for preferred DCs, so that administrators can nominate an ordered list of preferred DCs to connect to for imports/exports. When this is used with Event Broker, especially in forests where there are delays in AD replication between DCs, the result can be that Event Broker detects a change before it is replicated to the DC from which FIM is connecting. This generally results in a missed change.
A feature to configure the AD agent exactly in line with that in the corresponding AD MA is suggested here.
Getting the following error in Event Broker. Running version: 4.0.4 Rev 1
Operation AD MA - Delta Import and Delta Sync with id 72e8799b-cbf2-402b-9d2e-119957d9cfc2 failed in the operation list REDACTED Outgoing with id 21bb9f43-c07e-42db-bb21-118e7752123c for the following reason. This is retry number 0: System.InvalidCastException: The agent of type IdentityBrokerAgentAuditingDecorator was not of requested type IMIMAgent.
at Unify.Product.EventBroker.AgentExtensions.GetTypedAgent[TAgent](IAgent agent)
at Unify.Product.EventBroker.AgentEngineRepository.GetAgent[TAgent](Guid agentId)
at Unify.Product.EventBroker.RunProfilePlugInFactory.CreateComponent(IOperationFactoryInformation factoryInformation)
at Unify.Framework.ExtensibilityPlugInGenerator`4.CreateComponent(TFactoryInfo factoryInformation)
at Unify.Product.EventBroker.OperationListExecutorBase.RunNextOperations(IEnumerator`1 operationEnumerator)
In attempting to upgrade an existing UNIFYNow site to work with the latest AAD Connect version, I found that the microsoftidentityintegrationservice WMI namespace was missing. This was preventing the successful creation of an AAD Connect agent for the new AAD Connect host.
After locating articles on how to restore this namespace, I found this reference which stated "... the deprecated WMI endpoints for MIIS_Service have now been removed ...". Furthermore, the local ADSyncAdmins, ADSyncBrowse, ADSyncOperators and ADSyncPasswordSet groups no longer exist - these being the security roles associated to the WMI namespace.
Guidance in the above reference is now this: "Any WMI operations should now be done via PS cmdlets"
Does this mean that UNIFYNow will not support AAD Connect from version 220.127.116.11 onwards, or is work underway to change the agent to connect via PS?
Thanks Bob. I've updated the article to contain this information.
Microsoft has just published this MIM article which explains how to configure the MIM Sync and Server service accounts to be gMSA (ones that don't require passwords).
To make for a more compelling business case to leverage this at MIM sites it would help if UNIFYNow (and UNIFYBroker for that matter) also supported gMSA. This would help simplify MIM/Broker deployments at customer sites.
Can we please have this feature request put forward for consideration?
Customer support service by UserEcho