Conflict between MSI and EXE installs (and alternate deployment strategies)

Fault conditions:

1. User has previously installed/uninstalled the EXE version.
2. User has deployed the MSI edition.
3. SSO such as myapps.microsoft.com fails to launch C9 trader due to left over registry keys.

If a user has previously installed the EXE version of Cloud9 and wishes to switch to using the MSI version, the EXE version should be uninstalled and the registry key at HKCU\Software\Classes\c9trader needs to be deleted in order for the MSI version to be launched via SSO.

This is due to a conflict between registry keys at the user level (EXE version) and registry keys at the system level (MSI).

After removing the EXE version the following command will clean up and registry entries left behind:

reg delete "HKCU\Software\Classes\c9trader" /f

Note that this command needs to be run against each windows account that has previously used the EXE version.

Depending on your deployment preference, IT admins may want to deploy the EXE and MSI side-by-side such as in the following situation:

1. Firm would like to pre-install a fixed/pinned version of Cloud9 across their network of machines.
2. A specific user would like to use a different version of Cloud9 either for testing or troubleshooting.

In this scenario, the EXE version only affects the currently logged in Windows user, while other users of the system will still be tied to the MSI version.