Once the policy is setup, go to the Custom Modules tab. These policies are checked by the client during installation. (The “enforce” checkbox for each setting prevents the end-user from being able to change that setting). To change a policy, click the edit button next to the one of the policies. If you need to create a new policy, use the “Add policy” button at the top of the screen. The Policies tab has the custom settings used by the client (such as whitelisting, auto-starting, and auto-adding to groups).Įach custom module can only use one “Policy,” but each policy can have all possible settings. You’ll see two tabs: Custom Modules and Policies. Log into to On the left hand side of the screen, choose Design & Deploy In Jamf logs I see Error running script: return code was 206.The scenario: you have computers that are only bound to AzureAD and you need to deploy a customized version TeamViewer to those computers. Launchctl load /Library/LaunchAgents/_ist 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. I am currently trying to replace Teamviewer 12 Host with Teamviewer 14 Host.
0 kommentar(er)
