TeamViewer 7 ID in Custom Inventory Field?

Does anyone know how to get the TeamViewer 7 ID into a Custom Inventory Field so that you can find it and search for it in the Kace system inventory? I thought I had the solution by creating a custom inventory field by using the following syntax, but nothing seems to work and I get garbage or nothing in the custom inventory field on machines that match the label I'm testing on. I also tried the "NUMBER" type instead of "TEXT" with no luck.

for 64-bitRegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TeamViewer\Version7,ClientID,TEXT)for 32-bitRegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\TeamViewer\Version7,ClientID,TEXT)

Comments

Answers

1

What agent version are you running?

I had several custom inventory rules for TeamViewer IDs that stopped working when we updated the KACE Agent to 5.3.47173 All of the returned data turned garbled. I went back and forth with KACE trying to find a solution for about two weeks before they said it was a bug. I was told it was submitted to engineering.

It would be interesting to try your custom rule on an older version of the agent. Mine were working great using 5.1.33668

:END
exit
-----------------------------
However, we do have several clients that still have TeamViewer 5 installed. I'm having trouble determining the best way to modify the above script to also check the 'version5' registry key if 'version7' doesn't exist. Any help is greatly appreciated!

Thank you for your suggestion! I did exactly this, and it works great.

Now I'm trying to incorporate the TeamViewer ID returned by the custom inventory rule into a machine action. I know I can launch a TeamViewer session with the machine action "C:\\Program Files (x86)\\TeamViewer\\Version7\\teamviewer.exe" -i --Password . Does anyone know if I can replace the field with the string from the custom inventory rule (similar to how I can do mstsc.exe /v:KACE_HOST_IP)?

Kyle, You will be able to do that with the 5.4 release coming soon. You will be able to use any custom inventory field as a variable in machine actions. Machine actions will also be unlimited instead of just 2.