Hey @aporlebeke ,
Yes we have license for Teamviewer. Does your Teamviewer settings have the unattended password set?
That is one thing that I can't figure out before, how to apply that password as part of package.
I deploy Teamviewer now on our clients as you mentioned but with a slightly different process. I've been following this process: https://jdmsysadmin.wordpress.com/2014/04/16/configuring-teamviewer-host-9-to-be-deployable-with-munki/
For us to keep the PermanentPassword we need to deploy Teamviewer 8 first and then install the new version on top of it.
I haven't had any luck before deploying it straight from a composer package. If you're saying now that it works perfectly I may have to re-visit my process.
@Araneta @rleatherwood Hello everyone. Sorry for not responding, for some reason I didn't have email notifications turned on for JAMFnation. That's since been fixed :)
SO! Today I said enough is enough. I'm tired of imaging our machines, logging in, opening a web browser, navigating to our custom PKG URL @ get.teamviewer.com/uniquepathhere, clicking through the installer, setting a passcode, etc. etc. just get to get TeamViewer on our machines.
So, I created a script, which I have tested successfully (EDIT: works with TeamViewer 11 & 12). The script automates most of the process - downloading, installing, and deleting the TeamViewer PKG. You still have to manually enter a remote code, but I can image you could build that yourself it you wanted to.
Here's the script:
#!/bin/bash
# Created by AP Orlebeke on 2/24/16
# Downloads TeamViewer 10 Host package, effectively going to
# get.teamviewer.com/ourcustomlink in a browser.
########################################################
logfile="/path/to/log/file.log"
USER=$(/bin/ls -l /dev/console | /usr/bin/awk '{print $3}')
# Create a function to echo output and write to a log file
writelog () {
echo "${1}" "${2}" "${3}" "${4}"
echo $(date) "${1}" "${2}" "${3}" "${4}" >> $logfile
}
########################################################
# Check for Log file
if [ -f "/path/to/log/file.log" ]; then
writelog "CHECK: Log Present"
else
touch "/path/to/log/file.log"
writelog "CREATED: Log"
fi
# You can change this to wherever you want, but setting to a local
# user will download the PKG to that user's home folder.
/usr/bin/cd /Users/$USER
writelog "DOWNLOADING: TeamViewer Host PKG"
/usr/bin/curl 'https://download.teamviewer.com/download/version_10x/CustomDesign/Install%20TeamViewerHost-XXXXXXXX.pkg' -o "Install TeamViewerHost-XXXXXXXX.pkg"
sleep 15
if [ -f "/Users/$USER/Install TeamViewerHost-XXXXXXXX.pkg" ]; then
# Installs package
writelog "INSTALLING: TeamViewer Host"
/usr/sbin/installer -pkg "/Users/$USER/Install TeamViewerHost-XXXXXXXX.pkg" -target /
else
writelog "WAITING: Download incomplete"
sleep 5
writelog "INSTALLING: TeamViewer Host Attempt 2"
/usr/sbin/installer -pkg "/Users/$USER/Install TeamViewerHost-XXXXXXXX.pkg" -target /
fi
sleep 5
writelog "DELETING: TeamViewer Host PKG"
sudo rm -rf "/Users/$USER/Install TeamViewerHost-XXXXXXXX.pkg"
writelog "Script Complete"
exit 0The real key here for me was getting the full download path to our custom module (the curl line of the script). If you go to your module's URL - get.teamviewer.com/customurlpathformodule - there is a link in the middle of the page that you can click in the event the PKG doesn't download automatically.
Copy that link and pop it into the curl line to have the script download that file and BAM! You've got yourself a script you can use with a policy to automate a lot of the manual work you were doing before.
I had issues over the summer where I was changing the name of the TeamViewer PKG file that gets downloaded and if I recall correctly if you change the name it will not apply your custom design settings. So for this I kept the PKG named whatever it is by default.
You're happy to remove the logging component or shorten/extend the sleep times depending on your Internet speeds. Take it and run with it. I don't have a Github page, but maybe now I'll get around to it.
Hope it proves helpful for folks!
Small update here.
After upgrading to TeamViewer 12 and updating our modules, I noticed that the script to download our host module was failing during install.
It appears that these downloads have moved a bit, as every time I ran our normal curl command I kept getting a file that was roughly ~200 bytes. The installer should be at least 30MB.
If you run a curl 'https://download.teamviewer.com/download.... (the link you get by right-clicking the "Try Again" URL on your host download page) you'll get something like the following:
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="https://dl.tvcdn.de//download/version_12x/CustomDesign/Install%20TeamViewerHost-XXXXXXXXXX.pkg">here</a>.</h2>
</body></html>You'll notice the difference in the initial portion of the URL compared to what's shown on the download page.
Use this link instead in your script.
