In Jamf logs I see Error running script: return code was 206.
The software requires a 4-digit password (you enter it here).
A quick 21.6MB download later, we had the TeamViewer app up and running. The TeamViewer 14 Setup screen asks some questions, and we answered that we’re doing a basic installation for a company/commercial use. Launchctl load /Library/LaunchAgents/_ist TeamViewer 14 is remote access software and can transfer files when the computer is in. Client software is right on the TeamViewer home page triggered by a button labeled Download for Free for personal use. Launchctl load /Library/LaunchDaemons/_ist #sh "/Library/Application Support/TV/Assign.sh" Run Assignment Tool (trying to run this directly from Jamf) /Applications/TeamViewerHost.app/Contents/Helpers/TeamViewer_Assignment -api-token *******-********************* -group-id g******** -alias "$" -grant-easy-access -wait 10 I can continue Installing v12 and then running the v14 installer on top, which will retain the assignment but I'd rather it was installing cleanly on new devices. If I run it in Terminal, or from a local script file it will work but neither option works when calling from Jamf. Teamviewer have now bundled the Assignment file with the installer but trying to call this doesn't seem to work via Jamf. I previously found a script on here and got it to work using Dropbox to host the PKG and Assignment files, as seen in the below script. TeamViewer supports key exchange and AES (256 Bit) session encoding and works behind firewalls. It can do remote administration of unattended servers, file transfers, remote support without installation, remote presentations, and more. I am currently trying to replace Teamviewer 12 Host with Teamviewer 14 Host. TeamViewer contains support, administration and screen-sharing in one package.
0 kommentar(er)
