Make the tuning parameter Base_AllowSIDLookupFailureForMapping visible by default
When this tuning parameter is enabled, it prevents a PI Collective from being flagged as out-of-sync when some of the PI Collective members can resolve the SID of a PI Mapping and others cannot. However, by default, this tuning parameter is hidden and disabled.
This tuning parameter is important when you are trying to replace all PI Trusts with PI Mappings to accounts that are dedicated to each instance of each PI service and you do not have the power to create domain accounts and/or the creation of dedicated domain accounts is not a priority for the organization as a whole and so it never gets done. The next best option is to use NTLM authentication and set up a local account with the same user name and password on all PI Collective members for each instance of each PI service. Each local account requires its own PI Mapping, and each PI Collective member has a copy of each PI Mapping. However, a PI Collective member cannot "see" the local accounts on any computer other than itself, and so it cannot resolve the SIDs of accounts that are local to the other members, which causes the PI Collective to go out-of-sync unless Base_AllowSIDLookupFailureForMapping is enabled.
The description of Base_AllowSIDLookupFailureForMapping provides a different use case: allowing the PI Collective to remain in-sync even when some members are in different, untrusted Windows environments.
The main point is that this tuning parameter is important for the adoption of PI Mappings, so please make it visible by default so that it can be more easily discovered and set by administrators.