Customizing Connector issues

[bkd]

I've used the supplied javascript to customize the .MSI for the Outlook connector with our server name. When Installed interactively by an administrative user the customized connector does populate the server name and select SSL as expected. However, if a different user logs into the computer and sets up Outlook with the Zimbra connector, or if I deploy the connector through group policy to machines; the server name is not populated. Is this a bug or expected behavior?

I'm using 5.0.11 version of the connector.

[fsiegel]

The fix for bug 35196 (which happened in 5.0.14) should fix this issue for you. Try upgrading to the latest connector (5.0.16). I also suggest that since we changed registry behavior, you completely uninstall the 5.0.11 connector and then install 5.0.16, rather than doing an upgrade.

[Rich Graves]

If we're not affected by bug 35196 (single-user machines), is there any reason to uninstall/install versus upgrade?

[fsiegel]

Well -- here's the reason, and you can decide. We used to put almost all our keys in HKCU (the ones that were in HKLM were kind of an oversight). But people wanted the ability to customize per user, so we now put everything in HKLM to start (the admin installs ZCO), and then if individual users want to customize while they run the product, their keys go in HKCU. We check HKCU first, and if there is something there, we'll use it. If there were leftover keys from a previous install, we'll use them.

So I said the thing about unintalling and reinstalling so you wouldn't run into a situation where you wanted a fresh install, but you had leftover keys. If you don't care about that, then you can just upgrade.