![]() $header. PS C:\> Get-TVDeviceInfoFromAlias -alias $value1 With that setting off, the remote party wouldnt have access unless you are in front of your computer to approve their acce. It takes a few steps to enable in the settings so you wouldnt do it accidentally. Is the User Level Token that you can create from the Teamviewer Management ConsoleĬan use Set-TVToken Function will then not be nessessary to use this paramameter Answer (1 of 6): There is a setting to allow unattended remote access and start at bootup. Is the Name of the Device seen in all console Get all possible information of a Device from it's alias In some cases, the remote user interface is not displayed properly. ![]() After installing TeamViewer, unattended access is possible with the personal TeamViewer password of the remote device. Gets All Teamviewer Device Info from Alias Can be Portion of the alias TeamViewer can usually be used on headless systems. Write-Output "Teamviewer Token not working" Write-Output "Teamviewer Token Is Working and Set" $TokenTest = Invoke-RestMethod -Uri "" -Method GET -Headers $header -ContentType application/json $header.Add("authorization", "Bearer $UserToken") PowerShell Script request: Set-TVToken -UserToken $value1įor more Details see Teamviewer API token Documentation You'll need to sort the authentication which involves oAuth, but based on this API documentation, it should be possible using PRTG's support for custom sensors: ![]() I believe that this is the information you're after. That returns a list of sessions, which reports among other things: Specifically, in the TeamViewer_API_Documentation.pdf available in the second link documents the following function: GET /api/v1/sessions (list session codes) There are currently no plans for a team-viewer specific sensor at the present time, but by checking their documentation this should be possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |