Thank you for making me and my team's life just that little bit more miserable by wasting even more of our precious screen real-estate. All we want visible and accessible is the Contacts and Computer list, we don't need any of the other stuff always readily available. We all care more about our screen real estate than your UX designers' obsession with reducing click-through-counts and following the '3 click rule' for various UI workflows, but thanks for all the useless whitespace on the right and bottom left, very helpful. We have 1x3 or 2x3 1080p monitor setups and the width is double and now takes up an entire third of a screen but hey, thanks for the dedicated 350x475 area of the list of Available services we're never going to use, ever. Honestly, if there any other option out there that had was as resilient and effective with the actual remote desktop experience as TeamViewer (as opposed to all the other fluff you've added over the years) we would have ditched this software stack ages ago. I sometimes wish we could just license the core technology and make our own user interface (Or even just some comprehensive URI handlers to immediately launch sessions, bypassing UI completely) instead just to avoid this annoying **bleep** with change for the sake of change and micro-optimisation of UX.
... View more
Another Corporate user here, we use SCCM, MSIs and SCP (at least, we try to) I must admit, I'm tired of this flaky non-standard feature too. Not sure why MSI public and private properties aren't used to pass parameters during install, that's the standard way of doing such things when it comes to MSIs. Transforms (MST) would be swell too. Example: Note:This command is not real, it's just an example of how properties are used. msiexec.exe /i "TeamViewer_Host.msi" CONFIGID="1234567" DEVICEALIAS="Corp Machine X" -instead I have yet another Scripted Deployment Type I have to babysit in SCCM with a wrapper script to ensure it gets pushed out correctly.
... View more