Hi Guys,
i tried to installed Teamviewer Company Version MSI with the specific parameters to assign the device.
And it ended up not very well because i wrote my own script which worked fine instead of the PSDeploymentToolkit.
I’m still not sure where and how it happened but what i can see is, that the parameter parsing is fine in the PSDeployment Log but it somehow doesn’t parse correctly to the MSI installation.
Sadly i missed to save the log files because it was a customer environment and i dont have access now but i used two methods provided by teamviewer:
OLD one:
Execute-MSI -Action install -Path "TeamViewer_Host.msi" -Parameters '/qn ADDLOCAL=ALL REMOVE=f.DesktopShortcut CUSTOMCONFIGID=6a9xxx APITOKEN=9277945-xxxx ASSIGNMENTOPTIONS="--grant-easy-access"'
NEW one:
Execute-MSI -Action install -Path "TeamViewer_Host.msi"-Parameters "/qn ADDLOCAL=ALL REMOVE=f.DesktopShortcut CUSTOMCONFIGID=6b9xxx"
Start-Sleep -Seconds "30"
Execute-Process -Path "C:\Program Files\TeamViewer\TeamViewer.exe" -Parameters "assignment --id 0001CoABChCGMEiwmnAR7odLHLLIcvTAEixxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
I mean my experience with teamviewer are such bad that i cant be sure if its not something they implemented bad but it confused me over 4 hours to figure out that the assignment problem caused from the toolkit.
In every try the assignment wasn’t successful. It seems the CUSTOMCONFIGID was assigned because the company branding appears but the apitoken and the newer method with .exe -id didn’t work out.
Just to let you know. Perhaps its a kind of declaration problem with ’ ".
If i can help with more details let me know because i’m sure that’s not easily to figure out (especially if there is no access to that MSI).
Greetings
Moritz