Autoassignment Tool with TeamViewer 12 and proxy

damienghandour
damienghandour Posts: 3 ✭✭
in General questions

Hi, 

We're trying to deploy TV v12 with Autoassignment tool.

When we tried to register the device with the tool, we meet that issue : 

C:\Users\administrateur\Desktop>TeamViewer_Assignment.exe -apitoken MY_ID  -datafile "C:\Program Files (x86)\TeamViewer\AssignmentData.json"
TeamViewer_Assignment (r341)

=> Assignment failed with:
Get https://webapi.teamviewer.com/api/v1/devices?remotecontrol_id=r962270909: di
al tcp 65.52.140.72:443: connectex: Une tentative de connexion a échoué car le p
arti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une
connexion établie a échoué car l’hôte de connexion n’a pas répondu.

The tool need to go through a proxy to connect to Teamviewer webapi.

Is there a way to add an option to indicate to the tool that we need to use a specifific proxy server. 

Note : The device used is already connected with the proxy in Windows Proxy options for http and https connections (its works already with browsers).

Thanks for your help.

DG

Comments

  • damienghandour
    damienghandour Posts: 3 ✭✭

    Hi

    UP ...

    any idea ?

    How to make to autoassignment tool work with manual proxy ?

    ThanX.

     

  • christian-j
    christian-j Posts: 54 Staff member 🤠

    Hello,

    the current Assignment tool doesn't support a connection via proxy server automatically.
    We are planning to release a new version of it which will support this.

    Please try it this way:

    TeamViewer_Assignment.exe -apitoken {YourToken} -datafile "%ProgramFiles(x86)%\TeamViewer\AssignmentData.json" -verbose -proxyurl https://{Proxy_Username}:{Proxy_Password}@{Proxy_Host}:{Proxy_Port}

    Christian

    Team Lead Product Development (Enterprise)

    Did my reply answer your question? To help others, please accept it as solution. Thanks!
  • damienghandour
    damienghandour Posts: 3 ✭✭

    Hi Christian,

    Thanks for your reply.

    The option -proxyurl does't doesn't seem to work. Besides this, there are no credentials on our proxy . I get this result when I tried to execute it :

    (I tried with and without quotes surrounding proxyurl parameter)

     

    C:\Users\admin>\\domain.local\netlogon\TeamViewer_Assignment.exe -apitoken XXXXXXXXXXXXXXXXXXXXXXX -datafile "C:\Program Files (x86)\TeamViewer\AssignmentData.json" -verbose -proxyurl https://192.168.1.210:8080

     

     

     

    TeamViewer_Assignment (r341)
    flag provided but not defined: -proxyurl
    Usage of \\lsa.local\netlogon\TeamViewer_Assignment.exe:
    -allowEasyAccess
    Allows easy access (optional) (default true)
    -apitoken string
    Token for API-Access (optional, if not contained in AssignmentData.json)
    -apiurl string
    Root-URL of the TeamViewer-API (optional) (default "https://webapi.teamviewer.com/api/v1/")
    -datafile string
    Path to JSON-File 'AssignmentData.json' (required, environment variables are resolved when specified in the form of ${var})
    -devicealias string
    Alias for the new device in the partnerlist (optional, if omitted the host name is used, if "" is passed the TeamViewer-Id is used, environment variables are resolved when specified in the form of ${var})
    -verbose
    Verbose output (optional)
    -wait int
    Time to wait in seconds for the file specified with the -datafile parameter (optional, default is 10 seconds) (default 10)

     Any idea why the option -proxyurl is not active ?

    thanks !

  • christian-j
    christian-j Posts: 54 Staff member 🤠

    Hi damienghandour,

    we released a new version of the Assignment Tool this week, please download the latest version and try it again.

    Christian

    Team Lead Product Development (Enterprise)

    Did my reply answer your question? To help others, please accept it as solution. Thanks!
Trustpilot

Categories

This Week's Leaders