Thankfully with Munki we are able to automate this process. To perform the activation TeamViewer includes an executable that must be run to activate the client with your management account. Adding the ID to your Management Account folder.Now we move to the activation that will assign the device to your account which includes: This means that the changes we make are immediately committed to the system. Thanks to Greg Neagle and Michael Lynn it was recommended to use CFPrefs instead of plistlib when modifying the preferences of TeamViewer. With the changes made above, we no longer need to require a logout to install TeamViewer. See below for the complete script: PostInstall Script In order to accomplish this I have added the creation of a launchagent in the postinstall script that will relaunch the TeamViewer services should they be closed. When exiting TeamViewer it also stops the launch agents. This is definitely not best practice but we want to make sure TeamViewer continues to run in case a user decides to close it. ( Note: The attribute part is completely optional as if you import your package into Munki with the IDC attached in the name you do not need to use the xattr command.) These include:īefore I was modifying the MainMenuHost.nib file to remove the ability to exit TeamViewer. Once the installation completes we want to set our attribute that will allow the customization pieces we defined in the management console to download and be applied to the client. Listed below is my preinstall script that you can take and use in your environment: PreInstall Script We are also going to remove any old TeamViewer preference files from the system should they still exist. This way, TeamViewer gets these crash reports and the user is no longer bothered by them. The last one I added because I was tired of users always getting the crash reports. Allows connections to the system whether you are logged on or not.Sets your Password to change preferences.Firstly, we will need a preinstall script that performs the following: Once imported we are going to make some changes. Once downloaded go ahead and import it into Munki. So first if you haven’t already you should create a Host deployment version so that you can download your prebuilt host package. In this post I will highlight the scripts I used and how I am now able to deploy TeamViewer 12 without requiring the user to log out.
Sounds easy right? Well unfortunately there are settings that are not set and you have to create some scripts in order to perform the assignment of the device to your account. This version was to bring new deployment features and make a simple one click install to deploy host to all machines. Over the past week our college purchased and began testing TeamViewer version 12.
0 kommentar(er)
