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 !
... View more
