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.). As a general rule, if someone has flair, they almost definitely know what they're talking about.

Microsoft employees typically have MSFT Official flair, and MVPs usually have MSFT Enterprise Mobility MVP with a link to their personal site/blog.

Please send mod mail if you qualify and would like flair set for your account.

Flair is reserved for Microsoft employees and MVPs.

System Center Configuration Manager and Endpoint Protection.Listing of Local ConfigMgr-related User Groups (largely outdated) URL shorteners cause this almost every time, but so do strings of apparent gibberish like WSUS and PXE sometimes. It might have been caught by the spam filter. Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up?

Teamviewer msi