TeamViewer
Overview
CPE
cpe:2.3:a:teamviewer:teamviewer:*:*:*:*:*:*:*:* Version & Lifecycle
Community Notes
TeamViewer – Command-line note
For silent deployment of TeamViewer Host via MSI in enterprise scripts, use: msiexec.exe /i "TeamViewer_Host.msi" /qn CUSTOMCONFIGID=YOUR_CUSTOM_CONFIG_ID ASSIGNMENTID=YOUR_ASSIGNMENT_ID. Replace the IDs with values from your TeamViewer management console policy and assignment configuration for automated device provisioning without UI prompts. This ensures scalable, unattended installation matching your Corporate or Tensor license module.
For MSI package sourcing, plan for a licensed TeamViewer deployment workflow rather than a generic public EXE download. TeamViewer documents MSI mass deployment for the full client and Host, including deployment with CUSTOMCONFIGID and assignment values from the management console; use the official TeamViewer mass deployment guide as the source of record when collecting MSI media and packaging parameters.
For TeamViewer MSI deployments, source the Windows MSI package from TeamViewer’s official download channel and stage the licensed installer in managed content. Keep Host/full-client and x86/x64 choices explicit so updates target the intended TeamViewer installation.
Official source: TeamViewer official documentation/download page.
For managed TeamViewer packaging, expect some account-specific downloads and assignment artifacts to require the TeamViewer portal rather than an anonymous static installer URL. Keep the source package and assignment configuration together in your local software repository so update jobs do not depend on an unauthenticated browser session.
Official source: TeamViewer portal.
For TeamViewer packaging, use TeamViewer’s official Windows download page as the installer source and confirm whether the staged package is the intended EXE/MSI and architecture before deployment. Refresh cached TeamViewer content from that vendor page rather than reusing an older installer.
Source: TeamViewer official source.
MSI For Corporate-Licensed Customers Only
TeamViewer’s vendor provides MSI installers only to eligible corporate-license customers; basic-license users are generally left with the public EXE, which has much less enterprise assignment/customization capability. If you are packaging TeamViewer or TeamViewer Host, use the official TeamViewer Windows download page or the licensed TeamViewer management/download portal as the source, and record whether the staged installer is the public EXE, TeamViewer MSI, or TeamViewer Host MSI.
The public Windows setup can be run silently with TeamViewer_Setup_x64.exe /S /norestart, but automated account/device assignment for managed deployments normally depends on the corporate MSI plus values from your TeamViewer management console. Keep the MSI entitlement and download date with your package record so ConfigMgr/Intune update mismatches can be traced back to the exact vendor-sourced installer.
Release Notes & Updates
Known Vulnerabilities
- CVE-2019-18988 7.0
- CVE-2018-16550 9.8
- CVE-2010-3128 9.3
Also known as
Other names people use for this app — helps search and matching.
Sign in to suggest a name.
