The first one for connecting to the local IP for speed. So in the end I ended up creating 2 machine actions. Just replace the KACE_CUSTOM_INVENTORY_TEAMVIEWERID in the machine action with KACE_HOST_IP. If your host is configured to accept lan connections, then you can connect via IP address instead for a better connection. This speeds it up a little in case you get tired of typing passwords over and over. We have a set password on our teamviewer hosts so I added the "-Password" parameter to the machine action. Teamviewer.exe -i -Password -m fileTransfer P 123456).īelow you can see an example of a command line in which TeamViewer is connecting to a specific ID, using a predefined password and a preset connection mode:Ĭ:\Program Files\TeamViewer\Version8\teamviewer.exe -i 18876347 -Password test -m fileTransfer The available connection modes are: Alternatively you may also use the short form which is executed with a " -" in the beginning (e.g. TeamViewer can be run via command line using different parameters which have to be preceded with a " -" (e.g. I also found this link that explanes teamviewer command line parameters.Īre there parameters to start TeamViewer? Mine was found under HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\TeamViewer\ Version9 So just make sure its pointing to the version you own. It more details on the custom inventory variable.ĭouble check your registry location for the ClientID. You can also click the little orange question mark next to the Machine Actions title on General settings. Once those are done, you can use your machine action to connect to a machine with their TeamViewer ID.
To verify the rule work, look at the machine inventory under Custom Inventory.
0 kommentar(er)
