TeamViewer irregular update cycle
Hi,
In our organization we use a package manager solution (Patch my PC) to automatically package and publish a bunch of applications. This solution uses publicly available msi installers. Unfortunately, TeamViewer only publicly provides an exe installer, while the msi package has to be retrieved from the TeamViewer management webconsole. This means we have to log on to the webconsole for every update and download the msi's manually.
This in itself wouldn't be all that annoying, if it wasn't for the unstructured update cycle that TeamViewer seems to uphold. Some months, there are like seven(??) different minor updates that we have to go download.
The solution? Why not use an update schedule, like every other sizeable organization does, in which updates are published monthly or even every three months? The only exception should be security updates. Other than that, I see no reason to publish every new minor feature update as soon as it's ready for production. If implementing a structured system like this would be impossible for some obscure reason, why not make the msi's of the TeamViewer host and full version publicly available?
