Sometimes I wish I could pause an Operation List (after the current operation completes, obviously), perform some manual steps, and then restart it from the same place.

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?

A new plugin is requested to convert the latest "Safety Catch" PowerShell script into an OOTB plugin for UNIFYNow.  This script is located in DevOps here.

This plugin can then be used as part of an enhanced default configuration wizard - see separate feature request.

The default configuration generated by the auto configuration wizard no longer meets the best practice model I expect of any UNIFYNow deployment - not without a few tweaks to save otherwise time consuming post install configuration.

Changes required include but are not limited to:

1. Creation of a single global synchronisation operation in lieu of a separate one for each MA, which always starts with the FIM MA if there is one present;
2. Auto-creating a default run history archive operation list;
3. Incorporates the option of including a "Safety Catch" concept for each export/import excluding the FIM MA itself.

The above are the main improvements - the latter presumably requiring the bundling of an appropriate version of this script with the product, or a new plugin alternative.

While there is an existing process of migrating config (https://voice.unifysolutions.net/knowledge-bases/8/articles/2719-migrating-unifynow-between-environment) it is far from ideal - essentially because of the challenges posed by the 5 bullet points at the bottom of the article.

Furthermore, the configuration itself is incredibly tedious, even in the simplest of environments, especially since we're now implementing the Safety Catch mechanism as a "best practice".  This is even after having used the Auto Config wizard, which these days gets us perhaps 50% of the way there.  Problems include

1. needing to replace global operations list for each MA with a single global operation list for all MAs in the right sequence with the FIM MA first;
2. needing to configure the Safety Catch mechanism manually for inbound, outbound and global operation lists;
3. having to set up exclusion groups manually; and
4. on occasion (perhaps only with earlier versions) the MA guids have become corrupted (e.g. UNIFYNow startup when the FIMSynchronizationService is not running), and this can cost hours in manually rebuilding the config (Refresh MAs button doesn't ever seem to work in this scenario).

By moving from a manual to a scripted model we could kill 2 birds with one stone and significantly reduce design and deployment time, while improving consistency and reliability of UNIFYNow deployments (I am seeing evidence of misconfigured sites now).

I've spoken to Matt about this idea and I believe some prototype work was being done in a related area … hopefully this can be something worth progressing while the topic is hot.  What needs to be done to get traction with this one please?