![]() getting Jamf Pro to install the pkg as per standard practice fails because it is installed from /Library/Application Support/JAMF/Downloads/ (I think the sub dir is Downloads?). The installer itself has an issue, which I have raised with TeamViewer, where if there is a space in the file path, the post install script is unable to the identify the configuration ID.Įg. The installer is "customised" by including the Configuration ID (for your custom settings) in the file name eg Install TeamViewerHost-idc xyzxyzx.pkg which I then assume, during installation, the installer goes out to TeamViewer and fetches the relevant settings, branding images etc. ![]() You then are provided with a download link to the pkg installer. This is so we can just select the computer and offer remote assistance without needing to ask the customer for an "ID".įirst thing to do is "configure" the host installer by adding branding, selecting to use the assignment tool (to assign the client to the management console), applying the relevant policy and group etc. We need to deploy the software to all of our computers "silently" (the first launch dialogue box is fine) and have them register in the TeamViewer Management console. ![]() Wondering if anyone has had experience with deploying TV 13 or other versions? I have been working to create a POC for TeamViewer 13 in our org for macOS and Windows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |