We use a sync core to standardize agent configs and agent settings, as well as other common things, to our 6 production cores. I am currently building out our new 9.6 SP1 environment (planning migration from 9.5 SP2) and I've found a possible issue in the Client Connectivity settings.
On the 9.6 Sync core I built out all the agent settings and agent configs and set up the sync connection to our freshly built Dev core. Everything seemed to sync properly. On the Dev core, when attempting to push an agent, the task fails, and when building an agent installer, the console shows an error. Digging into the logs, i found that the problem was that it couldn't find the certificate file. I checked the Client Connectivity Settings used by the agent config (both originating from the Sync core) and found that it wanted the cert from the Sync core. I also noticed that the Core [server] address that it was pointing to was the Sync core FQDN rather than the Dev core that the agent was supposed to be connecting to.
After discovering this, my workaround plan was going to be sync'ing over the settings and agent configs, clearing the sync target status on the agent configs and then using a core-specific client connectivity setting for each core to include in the agent config. Unfortunately, when you clear the sync target status on the agent config, the console offers a warning:
"Clearing the sync target status will only be temporary if the source core resends this
If this item is resent, the changes you have made including clearing
sync target status will be overwritten. Continue?"
Through this, I have also discovered that it won't allow you to delete an item designated as a "default".
So my questions to the community, is what I've discovered regarding the client connectivity settings a feature or a bug? Has anyone else run into it and, if so, how did you work around it?
To me it seems somewhat problematic to be able to sync something that isn't able to be used on the target core. Thoughts?