We are doing healthcare interface development.

Developers have Ensemble installed locally on their laptops - code will be developed locally then deployed to integration, test/UAT and ultimately production servers in due course.

One of the other applications we are developing around happens to utilise an Iris desktop client to a remote Iris server. We want to have the application available on the developers laptops alongside the local Ensemble instance.

✅ It appears that if we install their desktop client then install our local Ensemble server, things work.

❌However, if we install a local Ensemble instance then the desktop client, their installation process breaks the local Ensemble instance.

When you do it the correct order the Cache Server Manager shows the local instance, the integration/test/production instances, plus the Iris instance related to the application. When you do it in the "wrong" order Cache Server Manager only shows the Iris instance related to the application. We don't want to have to rely on this ordering - a local Ensemble instance may have multiple namespaces set up, relating to various on-going development we don't want to have to recreate just to install the desktop client for the other application...

We can't figure out where Cache Server Manager stores its list of available instances - filesystem and Registry browsing so far not showing anything obvious!

We are taking it up with the supplier of the application, but in the meantime where might we look to "remind" Cache Server Manager about the local, integration, test and production servers it appears to have "forgotten" about when the application was installed? Developers are on Windows 10 laptops.