When you look at & unpack the actual installer (we use Suspicious Package), what you find is the function file below. This is confirmed by our experience with the installer name change that the the unique 7 character, alpha-numeric configuration ID plays a role in the customization. Imagine having to build custom PKG installers for every organization’s custom modules! Definitely not efficient. Below, you can see the hashes of our downloaded custom module and the generic installer from TeamViewer’s website are the same.Īnd this makes sense. Taking a closer look at the TeamViewer Host module PKG, we can verify that there isn’t anything unique about our custom installer from the generic installer. Because of this we left the package named as downloaded. At the time, I determined that this was due to our renaming of the host module installer, but didn’t explore the reason further.

When we first deployed TeamViewer Host, I found that our customizations never appeared. It wasn’t until recently that I decided to take a closer look behind the scenes to see how TeamViewer Host acquired its custom module configuration. Breaking Down the Custom Host Module Installer With only a Premium license, this rules out this option.Īs such, we’ve had to come up with our own workflow to install TeamViewer Host and assign it to our account. Unfortunately, TeamViewer requires a corporate license in order to remotely & programmatically deploy the Host module and automatically assign it to your account. To fill this need, we use TeamViewer and the TeamViewer Host module on our managed employee computers. While both VNC and Apple Remote Desktop are viable options on LAN (for Macs at least, we install a VNC client to accomplish this on Windows), these tools do not give us a way to request remote access and have users approve this.

Working for a school, it’s important that when necessary we can remotely connect to machines off our LAN.

Team viewer mac