Teamviewer Installation Instructions
Elder Raman
Just wondering if any of you have experience customizing TeamViewer Host 9 for deployment?
I tried following this instructions: -teamviewer-host-to-be-deployable-via-managed-software-update-munki-on-mac-os-x/
In mid July I'm going through Jumpstart training at our institution. While we primarily use Apple Remote Desktop and will possibly Casper Remote moving forward (all our managed machines are setup with a VPN to connect to us), we're looking to TeamViewer to be our online remote quicksupport system. We're not trying to use the TeamViewer Management Console to organize everything.
My guess is you could take a New & Modified snapshot in Composer prior to install, install and configure your settings - unattended password, wake on LAN, etc. - and then take your after snapshot so your sure to get all your settings.
Still very new to this, but I'm assuming you could then build your .pkg or .dmg and deploy it so those settings ripple to any new or existing home directories on the Mac so no matter who's logged or what new accounts are created you could still connect to them remotely.
All that being said, it might just be easier to download or configure the TeamViewer QuickSupport module and cache it somewhere on your deployed machines so it can be immediately launched without you or your users needing to download or install anything.
Don't know if you have a TeamViewer license or not, but if you have a license you can create custom modules that have your institution's branding and text for your users. I just made and downloaded the custom TeamViewer Host module I created on a freshly imaged computer, took a normal snapshot with Composer, and installed the TeamViewer module. Opened the TeamViewer Host application a few times to make sure it worked as expected and had our custom branding, set custom preferences / settings, and then took my post snapshot.
Worth noting, when you download your custom-made TeamViewer module package, TeamViewer does NOT include your customizations in the package itself. The TeamViewer application has to be able to talk to teamviewer.com to download the customization files it needs. Why TeamViewer doesn't put these things in the package you download I really don't know ... Anyway, we ran into the problem where the VLAN we were using was preventing TeamViewer Host from accessing teamviewer.com, and rather than open up the whole website in our web filter, I just temporarily connected the computer to a different VLAN just to get the customization files. With those files downloaded then took the 2nd Composer snapshot.
As far as I can tell, there's really nothing special you have to do besides that. We made sure to attach our institution's account to TeamViewer Host so we can track them and enforce any TeamViewer policies we might specify in the TeamViewer Management console.
Yes we have license for Teamviewer. Does your Teamviewer settings have the unattended password set?
That is one thing that I can't figure out before, how to apply that password as part of package.
For us to keep the PermanentPassword we need to deploy Teamviewer 8 first and then install the new version on top of it.
I haven't had any luck before deploying it straight from a composer package. If you're saying now that it works perfectly I may have to re-visit my process.
I've tried deploying teamviewer on our macs using composer and it never seemed to work. It's been about a year since I tried last, but I think one of the issues was that it either didn't assign to our account, didn't keep our unattended password, or didn't show up in our list when logging into the Teamviewer clients.
SO! Today I said enough is enough. I'm tired of imaging our machines, logging in, opening a web browser, navigating to our custom PKG URL @ get.teamviewer.com/uniquepathhere, clicking through the installer, setting a passcode, etc. etc. just get to get TeamViewer on our machines.
So, I created a script, which I have tested successfully (EDIT: works with TeamViewer 11 & 12). The script automates most of the process - downloading, installing, and deleting the TeamViewer PKG. You still have to manually enter a remote code, but I can image you could build that yourself it you wanted to.
The real key here for me was getting the full download path to our custom module (the curl line of the script). If you go to your module's URL - get.teamviewer.com/customurlpathformodule - there is a link in the middle of the page that you can click in the event the PKG doesn't download automatically.
Copy that link and pop it into the curl line to have the script download that file and BAM! You've got yourself a script you can use with a policy to automate a lot of the manual work you were doing before.
I had issues over the summer where I was changing the name of the TeamViewer PKG file that gets downloaded and if I recall correctly if you change the name it will not apply your custom design settings. So for this I kept the PKG named whatever it is by default.
You're happy to remove the logging component or shorten/extend the sleep times depending on your Internet speeds. Take it and run with it. I don't have a Github page, but maybe now I'll get around to it.
Awesome thanks, I'll look into this when I get a free moment and see if we can get it working down here, we had just given up putting Teamviewer on our macs for now and have only been pushing it out to our PC's
@dvasquez I haven't gotten around to figuring out how to automatically setup the unattended password. I was just glad to significantly decrease the steps we were taking post-image to setup. This information may live in a preference file, but depending on this information is formatted / written may not be deployable ... I'm going to take another look and see what I can figure out, but it's not something that's critical for me in our environment.
@dvasquez It looks like the /Library/Preferences PLIST (com.teamviewer.teamviewer10.plist) holds this information underneath the key of PermanentPassword, but all the sensitive information in this PLIST is encrypted. To automate or deploy this password you'd have to some fancy stuff, but frankly I'm not sure this is possible.
I'd reach out to TeamViewer and see. They charge extra for Windows if you want to be able to use an MSI file to automate TeamViewer installs, so I'd imagine they'd be not inclined to help do this on the Mac side.
Also, if anyone has been using the script I posted previously, I've posted it on Github with some more helpful comments if you're looking to deploy it in your environment. You can checkout the TeamViewer download & install script here.
Even if you do have a Corporate license and use this tool, it does not appear to allow you to automatically configure an unattended password. However, from their MSI deployment documentation (though focused on Windows) does include a macOS script flag that allows you to enable easy access for the account assignment: -allowEasyAccess=true.
I can confirm though that with the current version of TeamViewer 12 and my automated TeamViewer download & install script works on macOS Sierra (10.12.4). You just need to change the .../version_10x/... portion of the URL to version_12x.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
PS: I do not mind switching to full raspbian from dietpi if that is possible. I put the RP3 in a remote site that I do not visit often, and no body there can switch the OS for me so I have to work on the existing OS installation which is dietpi for rp3 at the moment.
Any chance you got this to work I am having the same issue followed this instructions and got it installed but wont start up -teamviewer-raspberry-pi/#comment-5886 really need teamviewer on my dietpi raspberry please help
Any chance you got this to work I am having the same issue followed this instructions and got it installed but wont start up How to Install TeamViewer on Raspberry Pi really need teamviewer on my dietpi raspberry please help
I gave up already. Tried installed quite alot of pkgs to make it similar to raspbian, but seems some packages are still missing, which I could not figure out. I will install raspbian next time i go back home.
Using TeamViewer for remote desktop shares requires a one-time download of the TeamViewer QuickSupport application. Navigate to the appropriate TeamViewer QuickSupport support site for Linux, Windows, or Mac OS (depending on which OS is on the computer you want to share the desktop from) and scroll down to find the download icon for the TeamViewer QuickSupport application. Select the download icon to download the software installer. The Linux option will directly download your software installer.
The NextSeq 1000/2000 computer is currently the only Linux-based Illumina instrument. TeamViewer QuickSupport is installed by Field Service Engineers during instrument installation. If you encounter issues with the TeamViewer QuickSupport software on a NextSeq 1000/2000, use the following instructions to install it. The Teamviewer for Linux quick support tool can be directly downloaded here.
Your ID is specific to the computer/instrument the application is installed on and will not change. Your Password will change every time the TeamViewer QuickSupport application is launched. Illumina support can only connect to your computer if the TeamViewer QuickSupport application is open and they have your current Password.
c80f0f1006