Hi,
We recently discovered a problem with SmartConnect v2.2.0.0 that caused high CPU utilization.
The person attending to the call provided me with a newer version, 2.4.0_B2, which solves the problem we were experiencing. However, there is a problem in that we can't directly upgrade from v2.2 to v2.4 because the same product GUID has been used for both MSI files.
So in order to upgrade, we have to first uninstall v2.2 which requires a reboot. After the reboot, we then have to install v2.4 which requires ANOTHER reboot! As you can imagine, trying to deploy this update to 600+ laptops is going to be extremely disruptive given the requirement for two reboots.
Many other OEMs allow upgrades from earlier versions and also allow the reboot to be supressed and let it happen "naturally". Would it be possible for you to please make it easier for us to deploy the update by allowing the v2.2 to v2.4 upgrade and making the reboot optional?
Thanks,
Jayson.