So I wrote a PowerShell script to reassign devices and enable easy access. They suggest running a cmd to reassign all the devices to our account and enable all the new stuff we bought for COVID patching until I could get a cloud gateway finished up. They tell me to generate a new custom package, create a new application in SCCM (with a new API) on version 15 and redeploy. Why would it do this? After all, I used the new API key from the new version 15 installer I made.īack and forth with TeamViewer support for like a month. All clients that got the upgrade are inaccessible without the password.

I download a new version 15 and update all my clients with this new command, but it's not assigning the computers to our account and enabling easy access. I thought, maybe some group policy change from security bonked the msi functionality, so, testing directly with the command line on a machine without TV I find that when I run it, the MSI help box just pops up - weird - I remove the /a switch and run again. Then, out of the blue, the installer quits working from Software Center on available installs. This worked without any problem for several months. Msiexec /a /i 'TeamViewer_Host.msi' /qn CUSTOMCONFIGID=xxxxxxx DESKTOPSHORTCUTS=0 APITOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ASSIGNMENTOPTIONS='-grant-easy-access' It looked something like this in SCCM - and it worked flawlessly for required deployments and available: I created my custom installer package in the TeamViewer console, downloaded the MSI package, created the app in SCCM and added all the switches in the command line for the options we were using at the time. When I first deployed it, probably a year ago on version 14, it was pretty simple. We've had a, how do I say this, 'bumpy' experience with deploying TeamViewer with all the bells and whistles (account assignment via API, easy access, monitoring and patching, policies etc.).

Old teamviewer versions