11/11/2022 0 Comments Teamviewer 9 account assignment![]() ![]() ![]()
CMD file): msiexec /i "%~dp0TeamViewer_Host.It appears (from reading the TeamViewer Log file at C:\Program Files (x86)\TeamViewer\TeamViewer12_Logfile.log) that the PC is being blocked by TeamViewer. This is my current one-liner for version .0 (in a. At one point we had computers registering in a completely different account/group and that's why we couldn't find them. My memory is a bit hazy now but I do remember that this was important, especially when adding computers to the right group. Our team had several logons and I had to be careful to use the right one when modifying the policy - and that tied in with the GROUPID. I also remember some confusion over the email account used to create the policy. I haven't had a failure-to-register since then. It's been a while now but I do recall that as soon as I started specifying the GROUPID the machines started registering perfectly. I just had a look at the current installation line I use and it hasn't changed much since I posted that last one-liner. Obviously this is only a workaround, not a solution. In this way the AssignmentData.json will appear (until the next TeamViewer problem.). Start-Process -FilePath "msiexec.exe" -ArgumentList "/i C:\temp\TEAMVIEWER\TeamViewer_Host.msi /L*V C:\temp\TEAMVIEWER\TeamViewerInstall.log /qn CUSTOMCONFIGID=`"xxxxx`" APITOKEN=`"xxxxxx-xxxxxxxxx`" ASSIGNMENTOPTIONS=`"assign -grant-easy-access -reassign -alias %COMPUTERNAME%`" IMPORTREGFILE=1" -Wait -PassThru #Teamviewer 9 account assignment code#If you don't have the AssignmentData.json file you have to re-install TV14 with the following code (also in this case PowerShell): Start-Process -FilePath "C:\temp\TeamViewer_Assignment.exe" -ArgumentList "-apitoken `"xxxxxxx-xxxxxxxxxx`" -datafile `"C:\Program Files (x86)\TeamViewer\AssignmentData.json`" -groupID `"gxxxxxxxxx`"" -Wait -PassThru The groupID has been retrieved with the RCT_IT solution. The solution posted by RCT_IT won't work in my case (sadly -()īTW, i've tested the TeamViewer_Assignment.exe's solution and that worked (below the Powershell code). #Teamviewer 9 account assignment mac osx#Assignmentdata.json is never created with the custom install (and yes, the checkbox is marked in the panel )Īny help would be GREATLY appreciated in trying to get the Mac OSX Teamviewer 14 to assign! But that doesn't seem to be documented anywhere and would be a complete custom approach.Įither way. My last step is to create a folder with a postinstall script, teamviewerhost and the teamview_assignment and see if it works. As I have tried nearly everything I can think of to get the assignment to work. The documentation from Team Viewer states The API encountered an error. Which according to standard API rules means "success". Either way, I run the assignment tool that way and I get an error 204. When running this tool -apitoken is changed to -api-token. However, this tool does not take the -datafile param. I then chmod -x /Applications/TeamvViewerHost.app/Helpers/Teamviewer_Assignment. #Teamviewer 9 account assignment download#The second attempt used curl to download the agent, I then installed the application ( all worked great ). This was of course validated when I went to ~/Library/Application Support/Teamviewer Host When I do it that way, I get an error that AssignmentData.json is not found. First, I downloaded the tool ( as guided in the management panel ) and used the -apitoken -datafile params when running the script. The problem is when I run the assignment tool. It shows up in the correct computer group and I am able to remote in. I have successfully deployed the custom host application using both jamf, and a shell script that uses curl to download the host. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |