"3 11:55:04.143 43756 43760 C1!! AssignmentTrigger::Set: can't open event (lastError=2), Errorcode=2ģ 11:55:04.143 43756 43760 C1 DeviceAssignment::TriggerAssignmentAction - Try triggering the assignment event for the next 30 secs." I did however dig down in the local roaming folder to find what looks like an error message. I still didn't get any sort of feedback when inputting the command. Still, I attempted to copy and past your suggestion to make sure I wasn't accidently pressing other keys when typing, and I made sure to change the api token portion to the api token that I have from the deployment module. On that note, I seem to have forgotten the assign command when I was typing what I've tried out. Sorry I've been kind of pulled away to another project for the moment, but I was able to try what you had typed down. The PC doesn't assign to my TeamViewer account nor do I recieve an error that the command is wrong.Īm I misstyping or not seeing something that is missing from the KB article? So far, everytime I run the command I have no output. I've tried running the command a few times with the -group option or the -reassign option to see if that might give me another outcome. I'm stuck once again trying to run commands such as "C:\Program Files (x86)\TeamViewer\TeamViewer.exe -api-token deployapitoken -grant-easy-access". Right now I'm trying to figure out how to use the assign option along with the exe to automatically throw new PCs into my account like how I do with the MSI version.Īfter sometime of fighting and talking to support I finally figured that I needed to install TeamViewer then run the commands from the KB article. I was able to find a work around changing some registry values, but that ended up being messy in the long run.
Recently I've switched from using the MSI version of TV to the exe version to have the auto update feature.
0 kommentar(er)
