Teamviewer Host 64 Bits
Saverio Lazaro
The plugin seems straightforward there is just three buttons, activate teamviwer host and reset password or changing id.
So I would expect reset password to change teamviwer password to connect to it.
Unfortunately it didn't seem to work, I tried Reset password with the plugin activated and deactivated also, still when I try to connect to it, it says the password is wrong so clearly is not changing it.
Moreover, I was looking through the forum and the omv wiki, but found nothing about teamviewer host plugin (or other plugins I was looking at back in the past) so I'm wondering did I miss some other sites where the plugin are discussed?! or maybe some github pages?!?
It seems strange to me that a plugin is been created for omv, but there is none discussion about it or some threads from who requested or created it.
So I hope I have looked everywhere, but if I'm missing some specific thread please advise
I just found out is not a plugin problem, it's just teamviewer not accepting more than 12 characters as password, so if you put more than 12 in the gui it will not be changed, but didn't give you any error message\alert about it through the webgui\plugin.
You get it just from commandline:
Anyway @ryecoaaron maybe could be a good idea to replicate the same message through the webgui\plugin too?! sorry to have called you in the discussion, but I don't know who created the plugin, so I hope you know who is he and point me in the right direction for plugin feature asks maybe?!
I was looking through the forum and the omv wiki, but found nothing about teamviewer host plugin (or other plugins I was looking at back in the past) so I'm wondering did I miss some other sites where the plugin are discussed?! or maybe some github pages?!?
@ryecoaaron thanks man, no big deal, actually, after I tried to make the command through command line I understood what was going on, I just thought to share the webgui "issue" not warning you, so newcomers and non commandline expert can troubleshoot it better.
Anyway thanks for the headsup on omv extras.org I knew that, but there is no wiki for the plugins, I was looking more for something like that for the various plugin, I guess there are not much man power for it, apart from some guides on this forum, so I would like to partecipate and give you my help for it, if you will ever decide to create something like that in a "more official" way, I would be honored to give something back to this project
While we are at it, I just would like to ask you a question without open a new thread, just for curiosity, the most painful aspect of reinstalling omv to me it's reset the firewall rules for the new build etc, mostly because the repetitive task to add port one by one, and when you start to playing around with your omv box the list can became quite long, I was wondering is it difficult to implement a button on the omv firewall to be able to load\save iptables configuration?!
Like a couple of button for iptables-save > file.conf and iptables-restore < file.conf, because unfortunately doing this through the terminal of course does work, but the ports will not be displayed in the gui aswell, so not very useful, I was wondering if could be implemented in the gui directly, but I don't know how much work this is though, just asking out of curiosity
Like a couple of button for iptables-save > file.conf and iptables-restore < file.conf, because unfortunately doing this through the terminal of course does work, but the ports will not be displayed in the gui aswell, so not very useful, I was wondering if could be implemented in the gui directly, but I don't know how much work this is though, just asking out of curiosity
@tinh_x7 it depends on what you need it for, the plugin basically installs teamviewer-host on your omv box, once you activate the plugin it will give you the ID associated with it, then you have to push reset password button to set a password for the plugin installed.
I use this configuration, on a small office to let some of the users turn on their pc remotely and take some files for working from home.
I guess you can add also it to your client for a fast access with the id and password you created, although I didn't use it this way.
The plugin is not getting a valid ID and I am also getting the "systemd[1]: teamviewerd.service: PID file /var/run/teamviewerd.pid" message. Changing file permissions, resetting/reinstalling plugin does not work.
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.
d3342ee215