Aquesta és una versió anterior. La versió actual és la 15.82.6. TeamViewer 15.82.6 · Data de publicació:
Fitxers d’instal·lació 15.78.3
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE (NSIS) | Tots els usuaris | 82,8 MB | download.teamviewer.com | VirusTotal |
| 64 bits | ZIP → MSI | Tots els usuaris | 92,7 MB | download.teamviewer.com | VirusTotal |
| 32 bits | EXE (NSIS) | Tots els usuaris | 78,5 MB | download.teamviewer.com | VirusTotal |
| 32 bits | ZIP → MSI | Tots els usuaris | 88,6 MB | download.teamviewer.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
New Features
- Users can now assign a service case directly from the device page in TeamViewer Remote.
- The view for creating Conditional Access rules has been streamlined and is now available as a full‑page view. Company‑based Conditional Access rules (now called internal rules) can be created on a single page instead of through multiple steps.
- Feature‑level permissions in Conditional Access have been expanded to include: Chat, Manage virtual monitors, Port forwarding, Session Insights logging.
- Multitenancy with Conditional Access is now available, enabling organizations to manage and securely connect data sources across multiple companies within a single framework. Organizations with access to both Conditional Access and Multitenancy can control data sources across multiple entities and create Conditional Access rules for external partners or subsidiary companies.
- Supporters now receive an automatically assigned virtual IP address for tunneling during agentless access, enabling secure access limited to the configured port from the supporter’s device.
- In‑app notifications are now displayed in TeamViewer Remote when a service case is created or assigned, and when an end user comes online with an active service case. This enables faster and more responsive handling of service requests.
- It is now possible to configure, for all outgoing Session Summary types, whether the supporter and/or the remote user can stop logging.
- The dashboard button has been removed from the Quick Actions in the in‑session toolbar. The functionality remains available from the Files & Extras menu.
Improvements
- Users can now connect to a session using Windows Authentication directly from the device page in TeamViewer Remote.
- Users can now close a session directly from the device page in TeamViewer Remote.
- The UI toggle in the Classic client is now visible to Tensor‑licensed admins to support early exploration and onboarding of the TeamViewer Remote interface.
- Automatically created custom modules and rollout setup configurations are now filtered out from the client, reducing UI clutter and preventing potential performance impact.
- Tooltip styling in the port forwarding user interface is now consistent across all areas and aligned with the overall TeamViewer design.
- The device management page in Settings has been enhanced to provide a clearer overview of device permissions. For company‑managed devices, internal members are now grouped as Company, while external users are listed separately with their respective permissions.
- The way the client receives updates about changes to devices and device groups has been improved.
Bugfixes
- Fixed a bug where connections started via contacts were blocked because of an invalid connection type check.
- Fixed a crash that could occur after switching sides during a remote control session when sending an in‑session chat message.
- Fixed a bug where Session Insights data downloads failed in the client and were instead redirected to the web client.https://community.teamviewer.com/English/categories/change-logs-en