If an administrator installs the TeamViewer host for unattended use on a server, then he probably clicks directly on the TeamViewer icon after the installation, opens the graphical user interface and notes the ID displayed there. The solution is to distinguish between the server ID and the user ID of the running TeamViewer.Ī TeamViewer service installed as a host can be accessed in two ways:Īnd this is exactly where the core of the problem lies. You might think the solution to this problem is in the TeamViewer settings. Since then, systemd has arrived in force and is normally used for constructing services that start upon boot.If you want to access your server with installed TeamViewer Host via TeamViewer with full access rights, you might know the following problem: The user only expects a black screen and the message “this screen cannot be captured at the moment. This is due to to fast user switching or a disconnected/minimized remote desktop session”.
If you don't feel like rebooting, you can start the service manually with: sudo service teamviewerd.sysv startĢ019 EDIT: This answer was written in 2013.
The service will now start automatically with each boot. Then run sudo update-rc.d teamviewerd.sysv defaults Making sure of this is relatively simple, just copy it to /etc/init.d like so: cd /opt/teamviewer/tv_bin/scriptĭon't forget to make the script non-writable to anyone but the owner! sudo chmod 755 /etc/init.d/teamviewerd.sysv # Description: TeamViewer remote control daemonĪll you need to do is make sure this script runs on startup. # Short-Description: TeamViewer remote control daemon # Required-Stop: $local_fs $network $named TeamViewer provides a script called teamviewerd.sysv available in /opt/teamviewer/tv_bin/script.
0 kommentar(er)
