MVP Award here, can't see why LS couldn't just add the custom scanning fields as an action, but fantastic work dude. See the magic happen when clicking on the TeamViewer action. Start-process -filepath "C:\Program Files (x86)\TeamViewer\TeamViewer.exe" -argumentlist "-i $ARG"ĥ. $ARG = import-csv "\\\export\TeamViewer_DeviceID.csv" -Delimiter ' ' |where-object assetname -like $server | select value -ExpandProperty value In the Actions folder of your Lansweeper server, add the powershell script 'tv.ps1' which contains the following commands: Empodera a tus trabajadores de primera lnea y optimiza las operaciones de produccin con nuestra plataforma de realidad aumentada industrial. Powershell -noprofile -executionpolicy bypass -command Ĥ. Escala, gestiona y protege las experiencias de asistencia en toda tu empresa de forma eficiente con nuestra plataforma de conectividad remota. Add a custom action called 'TeamViewer' which runs the following action: Where tblAssetCustom.State = 1 And tblRegistry.Valuename = 'ClientID'ģ. Inner Join tblRegistry On tblAssets.AssetID = tblRegistry.AssetID Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID Create a custom report that exports the hostname and TeamViewer ClientID to a CSV file called 'TeamViewer_DeviceID.csv': Set up registry scanning for the registry value 'ClientID' from SOFTWARE\WOW6432Node\TeamViewerĢ. I managed to create a custom TeamViewer action using this small workaround (currently only for 64 bit TeamViewer clients, but can easily be expanded to support 32 bit TV or older TV versions too, using the registry keys mentioned earlier in this topic):ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |