‎01-14-2016 05:15 PM
Solved! Go to Solution.
‎12-10-2018 01:16 PM
Select Top 1000000 tblAssets.AssetID,
tblAssets.AssetName,
tblRegistry.Value
From tblAssets
Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID
Inner Join tblRegistry On tblAssets.AssetID = tblRegistry.AssetID
Where tblAssetCustom.State = 1 And tblRegistry.Valuename = 'ClientID'
$server = $args[0]
$ARG = import-csv "\\<LansweeperServer>\export\TeamViewer_DeviceID.csv" -Delimiter ';' |where-object assetname -like $server | select value -ExpandProperty value
start-process -filepath "C:\Program Files (x86)\TeamViewer\TeamViewer.exe" -argumentlist "-i $ARG"
‎01-08-2019 02:43 AM
Hendrik.VE wrote:
Hi all,
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):
1. Set up registry scanning for the registry value 'ClientID' from SOFTWARE\WOW6432Node\TeamViewer
2. Create a custom report that exports the hostname and TeamViewer ClientID to a CSV file called 'TeamViewer_DeviceID.csv':Select Top 1000000 tblAssets.AssetID,
tblAssets.AssetName,
tblRegistry.Value
From tblAssets
Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID
Inner Join tblRegistry On tblAssets.AssetID = tblRegistry.AssetID
Where tblAssetCustom.State = 1 And tblRegistry.Valuename = 'ClientID'
3. Add a custom action called 'TeamViewer' which runs the following action:
powershell -noprofile -executionpolicy bypass -command {actionpath}tv.ps1 {computer}
4. In the Actions folder of your Lansweeper server, add the powershell script 'tv.ps1' which contains the following commands:$server = $args[0]
$ARG = import-csv "\\<LansweeperServer>\export\TeamViewer_DeviceID.csv" -Delimiter ';' |where-object assetname -like $server | select value -ExpandProperty value
start-process -filepath "C:\Program Files (x86)\TeamViewer\TeamViewer.exe" -argumentlist "-i $ARG"
5. See the magic happen when clicking on the TeamViewer action.
‎12-10-2018 06:34 PM
Hendrik.VE wrote:
I managed to create a custom TeamViewer action using this small workaround...
‎07-10-2018 09:17 PM
‎10-26-2017 03:55 PM
‎11-01-2017 11:52 AM
esr wrote:
Hi Kay
tblAssetCustom is one of the primary tables used by Lansweeper, not sure why it would tell you that table name is invalid.
I typically interact via SSMS, but in an effort to replicate your symptom I jumped onto my DEV server and used the database maintenance tool to run the update- worked fine- see screenshot attached.
I'm presuming you've set the custom scan required?
‎07-07-2017 01:38 PM
‎10-23-2017 07:42 PM
esr wrote:
UPDATE dbo.tblAssetCustom
SET dbo.tblAssetCustom.Custom1 = dbo.tblRegistry.value
FROM dbo.tblAssetCustom INNER JOIN dbo.tblRegistry
ON dbo.tblAssetCustom.AssetID = dbo.tblRegistry.AssetID
WHERE tblRegistry.Regkey LIKE '%teamviewer%'
‎07-07-2017 01:47 PM
esr wrote:
What you quoted is the whole deal 🙂
The custom scan gets the Client ID into the Lansweeper database. You'll be able to create reports with it or to see the ID, if found, on an asset page, under Config>Scanned Info>Registry Keys.
The UPDATE is just a tiny bit of code you can run to copy the Client ID over to the Custom Field of your choice so it's on the assets summary page and easy to see.
If your version of Lansweeper is old enough you can go to Configuration>Database Scripts and run the update there. New versions will have a DatabaseMaintenance.exe tool in the Lansweeper\Tools folder, or you can use SSMS regardless of Lansweeper version.
I strongly encourage backing up your database before any changes are made. I also encourage having a DEV environment where you can play & learn without impacting your PROD version. Lansweeper Support typically does not offer support for playing with your database.
‎06-12-2017 07:04 PM
‎06-12-2017 05:33 PM
UPDATE dbo.tblAssetCustom
SET dbo.tblAssetCustom.Custom1 = NULL
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now