![]() ![]() Now that we have the file we would add this to a DMG like we did originally with version 8 and make this DMG an update for TeamViewer 11.įinally the moment of truth - testing. ![]() My file has removed the following from TeamViewer: To modify a NIB file you will need to use xCode however if you are lazy I have gone ahead and attached my modified NIB file to this post for your use. Thanks to a GitHub project located at I was able to look at the actual NIB file for TeamViewer and then export and modify it. The last step is to insert our special MainMenuHost.NIB file. You could use this same process for version 10. Now that we have all the scripts in place, Munki will install in order, version 8, version 9 and finally version 11. Once imported into the repository we will use a pre instal and post install script in order to achieve full deployability. Still following along? Good! Now we are going to finally install the version that we want. Once imported into your repo you will want to go ahead and add the script below as a post install script: Now that we have TeamViewer 8 setup let's go ahead and get 9 ready for deployment with our script as well. (Of course you will need to remove the spaces) Remember to get SecurityPasswordAES and OptionsPasswordAES you will need to do a manual install on a system and use OS X's built in defaults to read out these binary values. I have gone ahead and scripted it in python so go ahead and use the script below. This will allow us to set our configuration settings before TeamViewer launches which will allow the unattended host password to be set. With Munki, we will require that when we install TeamViewer 11 that 8 and 9 be installed first. So let's get started.įirst we will install TeamViewer version 8 and utilize a pre install script. This is obviously no easy process but thankfully we have Munki (or insert software deployment service here). Finally, apply the MainMenuHost.NIB file that will remove the pieces we want from the menu that appears by clicking the menu bar item.Run a post install script that will set the custom attribute for your custom module from the website and run the application before we apply customization of the Main Menu in the Menu Bar.Run a Preinstall script that will copy the newly converted password with "special" encryption to the new plist for version 11.Load the LaunchDaemon so the password is converted.Set some additional settings that may not have carried over from version 8.Read in the TeamViewer 9 Plist as it is created by the setup.Convert the TeamViewer 9 Plist to XML so we can manipulate it.Cleanup TeamViewer 8's folder as it is now just in applications as TeamViewerHost.app.Unload the Launch Daemon for TeamViewer to run as a service.Run a post install script that will perform the following.Create with the settings we like initially such as the remote control password, settings password and turning off updates.Let's begin by highlighting this process: After a lot of testing, I have been able to make it somewhat deployable.Īre you ready for this process? It is quite the doozy and unfortunately is not an ideal model for a software that is cross-platform and labeled as deployable and customizable. It seems TeamViewer doesn't seem to understand how deployable software should work and there continues to be no improvement to the software. Using those instructions you will have trouble putting the password on another system as well as issues with the helper. Unfortunately my TeamViewer 10 post was incorrect and I did not test the deployment enough.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |