Given this situation, it is needed to check more background information such as log analysis to find the root cause.

From the information that you provided, the win32 app is installed successfully during the Autopilot phase, but it has someting wrong when launching the app. Where should I look to troubleshoot this? Thanks for the update.īased on my experience, if the win32 app is installed successfully, it means that the deployment method is correct. Which makes me think that, the install is occurring during device ESP and something causes it to not set it up correctly. If I manually uninstall TV from Windows 10, then allow Intune to install it again, with no other actions, it installs fine and is registered into the TV console fine. When launching TV manually from the Start Menu, it operates as if it is standalone, and none of the CUSTOMCONFIGID or APITOKEN or ASSIGNMENTOPTIONS were passed through, which would add it into the relevant area in TV, and inherit policy etc, turning off the password. The part that it is getting wrong, seems to be between Intune executing this install command, and TV operating with it. Msiexec /i 'TeamViewer_Host.msi' /q CUSTOMCONFIGID=a1b2c3d APITOKEN=12345678-AbCdEfGhIjKlMnOpQrSt ASSIGNMENTOPTIONS='-grant-easy-access' DESKTOPSHORTCUTS=0 ENABLEOUTLOOKPLUGIN='false'ĭevice restart behavior: No specific action

TeamViewer_Host.msi is packaged and deployed as a Win32 app, to a group of Devices.ĭevice goes through Autopilot, TV is installed, you can launch it from start menu.ĭevice has ESP which specifies one app as required (Microsoft Edge for Windows 10). I am having an issue with a Win32 app deployment, which I think is during the Autopilot phase.

Teamviewer 15 host