2 Teamviewer Versionen Auf Einem Rechner

TeamViewer Dual-Version Calculator

Calculate system requirements and compatibility for running two TeamViewer versions on one computer

Compatibility Results

Complete Guide: Running Two TeamViewer Versions on One Computer

Running multiple versions of TeamViewer on a single machine can be essential for IT professionals, system administrators, or users who need to maintain compatibility with different client systems. This comprehensive guide covers everything you need to know about installing, configuring, and managing two TeamViewer versions on one computer.

Why Run Multiple TeamViewer Versions?

  • Legacy System Support: Maintain connections with older systems that can’t upgrade
  • Testing Environments: Test new features while keeping a stable version
  • Client Requirements: Meet specific version requirements from different clients
  • Feature Comparison: Directly compare functionality between versions
  • Security Testing: Evaluate vulnerabilities in older versions

System Requirements for Dual Installation

The calculator above helps determine if your system can handle two TeamViewer versions. Here are the general requirements:

Component Minimum Requirements Recommended
Operating System Windows 7 SP1 / macOS 10.12 / Ubuntu 16.04 Windows 10 21H2+ / macOS 12+ / Ubuntu 20.04+
CPU Dual-core 1.5GHz Quad-core 2.5GHz+
RAM 2GB (4GB for concurrent use) 8GB+
Storage 500MB free space 2GB+ free space
Network 1 Mbps stable connection 10 Mbps+ for HD sessions

Step-by-Step Installation Guide

  1. Backup Your System:
    • Create a system restore point
    • Backup TeamViewer configuration files (if upgrading)
    • Export your TeamViewer account settings
  2. Install Primary Version:
    • Download the latest stable version from TeamViewer’s official site
    • Run the installer with default settings
    • Complete the setup and test basic functionality
  3. Prepare for Secondary Installation:
    • Download the legacy version installer
    • Create a new installation directory (e.g., C:\Program Files\TeamViewerLegacy)
    • Temporarily disable antivirus software (may interfere with installation)
  4. Install Secondary Version:
    • Run the legacy installer with custom settings
    • Select your custom installation directory
    • Choose “Portable installation” if available
    • Disable automatic updates for the legacy version
  5. Configure Port Conflicts:
    • Edit configuration files to use different ports
    • Primary version: Default ports (5938 TCP, 5938 UDP)
    • Secondary version: Custom ports (e.g., 5940 TCP, 5940 UDP)
  6. Create Separate Shortcuts:
    • Modify shortcut targets to include version-specific parameters
    • Example: “C:\Program Files\TeamViewerLegacy\TeamViewer.exe” –id 2
  7. Test Both Versions:
    • Verify both versions launch without conflicts
    • Test remote connections from both versions
    • Check that settings are maintained separately

Port Configuration for Multiple Instances

One of the most critical aspects of running multiple TeamViewer versions is managing port conflicts. TeamViewer uses several ports for different functions:

Port Protocol Purpose Default Value Recommended Alternative
5938 TCP/UDP Main connection port 5938 5940
443 TCP HTTPS/Proxy fallback 443 8443
80 TCP HTTP fallback 80 8080
5800-5810 TCP VNC compatibility 5800 5820-5830
5900-5910 TCP VNC compatibility 5900 5920-5930

To change ports, you’ll need to edit the configuration files:

  1. Navigate to the configuration directory (typically in %APPDATA%\TeamViewer)
  2. Locate the Client.config file
  3. Add or modify these entries: 
    [ConnectionIncoming]
TCPPortIn = 5940
UDPPortIn = 5940

[ConnectionOutgoing]
TCPPortOut = 5940
UDPPortOut = 5940
  4. Save the file and restart TeamViewer

Performance Optimization Tips

  • Resource Allocation:
    • Use Windows Task Manager to set different CPU affinities
    • Limit background processes for the legacy version
    • Allocate more RAM to the primary version via process priority
  • Network Optimization:
    • Configure QoS settings to prioritize the primary version
    • Use different network adapters if available
    • Limit bandwidth for the secondary version
  • Storage Management:
    • Install versions on different physical drives if possible
    • Regularly clean temporary files from both versions
    • Disable logging for the secondary version if not needed
  • Security Considerations:
    • Keep the primary version always updated
    • Isolate the legacy version with firewall rules
    • Use different TeamViewer accounts for each version

Common Issues and Solutions

Running multiple TeamViewer versions can lead to several common issues:

  1. Port Conflicts:

    Symptoms: Neither version can establish connections, error messages about ports in use

    Solution: Carefully configure different ports as shown in the table above. Verify no other applications are using your chosen alternative ports.

  2. Automatic Updates:

    Symptoms: Legacy version gets automatically updated to match the primary version

    Solution: Disable automatic updates in the legacy version settings and configure firewall rules to block update servers for that specific executable.

  3. Configuration File Conflicts:

    Symptoms: Settings from one version affect the other, lost connections

    Solution: Use separate configuration directories by launching with the –configdir parameter or using portable installations.

  4. Performance Degradation:

    Symptoms: Slow system response, laggy remote sessions

    Solution: Limit the secondary version’s resource usage, prioritize the primary version in Task Manager, and consider upgrading hardware if needed.

  5. License Issues:

    Symptoms: License errors, prompts to purchase when already licensed

    Solution: Ensure each version uses a separate license file or account. Contact TeamViewer support if issues persist.

Security Best Practices

Running multiple versions of remote access software increases your attack surface. Follow these security best practices:

  • Network Segmentation:
    • Place the legacy version on a separate VLAN if possible
    • Use firewall rules to restrict the legacy version’s network access
  • Authentication:
    • Use different, strong passwords for each version
    • Enable two-factor authentication on both versions
    • Consider using different TeamViewer accounts
  • Monitoring:
    • Set up logging for both versions (separate log files)
    • Monitor for unusual connection attempts
    • Use network monitoring tools to detect anomalies
  • Regular Maintenance:
    • Check for security updates for both versions
    • Remove unused legacy versions when no longer needed
    • Regularly review connection logs

The NIST Digital Identity Guidelines (SP 800-63B) provide excellent recommendations for authentication systems that apply to remote access software like TeamViewer.

Alternative Solutions

If running multiple TeamViewer versions proves too challenging, consider these alternatives:

  • Virtual Machines:
    • Run the legacy version in a VM with network isolation
    • Use VM snapshots for easy rollback
    • Allocate resources dynamically based on needs
  • Containerization:
    • Use Docker containers for each TeamViewer version
    • Easier to manage dependencies and isolation
    • Can be deployed on-demand when needed
  • Separate Physical Machines:
    • Dedicated machine for legacy version
    • Use KVM switches for easy access
    • Most secure option but highest cost
  • TeamViewer Portable:
    • Use portable versions that don’t require installation
    • Can run from USB drives or network shares
    • Easier to manage multiple versions

Legal and Compliance Considerations

Before implementing multiple TeamViewer versions, consider these legal aspects:

  • Licensing:
    • Verify your license allows multiple installations
    • Check if legacy versions require separate licenses
    • Consult TeamViewer’s End User License Agreement
  • Data Protection:
    • Ensure compliance with GDPR or other data protection laws
    • Implement proper logging for audit trails
    • Consider data residency requirements
  • Industry Regulations:
    • Healthcare: HIPAA compliance for remote access
    • Finance: PCI DSS requirements for remote sessions
    • Government: FISMA/FedRAMP considerations

The U.S. Department of Health & Human Services HIPAA FAQ provides guidance on remote access software in healthcare settings.

Advanced Configuration Options

For power users, these advanced configurations can enhance your dual-version setup:

  1. Custom Installation Parameters:

    TeamViewer supports several command-line parameters for custom installations:

    TeamViewer_Setup.exe /S /CustomInstallDir="C:\TeamViewerLegacy" /Portable
TeamViewer_Setup.exe /S /CustomConfigDir="%APPDATA%\TeamViewerLegacy"
  2. Registry Modifications:

    For Windows systems, you may need to modify registry keys to prevent conflicts:

    [HKEY_CURRENT_USER\Software\TeamViewer]
"ClientPath"="C:\\Program Files\\TeamViewer\\"
"LegacyClientPath"="C:\\Program Files\\TeamViewerLegacy\\"
  3. Service Configuration:

    Configure Windows services for each version:

    sc create "TeamViewerLegacy" binPath= "C:\TeamViewerLegacy\TeamViewer_Service.exe" start= auto
sc config "TeamViewerLegacy" obj= "NT AUTHORITY\LocalService" password= ""
  4. Firewall Rules:

    Create specific firewall rules for each version:

    netsh advfirewall firewall add rule name="TeamViewer Legacy" dir=in action=allow program="C:\TeamViewerLegacy\TeamViewer.exe" enable=yes
netsh advfirewall firewall add rule name="TeamViewer Legacy" dir=in action=allow protocol=TCP localport=5940

Performance Benchmarking

When running multiple TeamViewer versions, it’s important to benchmark performance impact. Here are typical performance metrics:

Metric Single Version Dual Version (Idling) Dual Version (Active)
CPU Usage (%) 1-3% 3-6% 15-30%
Memory Usage (MB) 100-150 200-300 400-800
Network Bandwidth (Mbps) 0.1-0.5 0.2-1.0 1.0-10.0
Session Latency (ms) 30-80 40-100 80-200
Disk I/O (KB/s) 5-20 10-40 50-200

For more detailed performance analysis, consider using tools like:

  • Windows Performance Monitor
  • Process Explorer (from Microsoft Sysinternals)
  • Wireshark for network analysis
  • TeamViewer’s built-in connection quality reports

Troubleshooting Guide

When issues arise with your dual-version setup, follow this troubleshooting flowchart:

  1. Identify the Problem:
    • Is the issue with one version or both?
    • Does it occur at startup or during operation?
    • Are there any error messages or codes?
  2. Check Basic Requirements:
    • Verify system meets minimum requirements
    • Check for sufficient free disk space
    • Ensure network connectivity is stable
  3. Review Log Files:
    • Check TeamViewer log files in %APPDATA%\TeamViewer
    • Look for errors in Windows Event Viewer
    • Examine network logs if connection issues
  4. Test Isolated Components:
    • Try running each version separately
    • Test with different network configurations
    • Create a new Windows user profile for testing
  5. Apply Fixes:
    • Reconfigure ports if conflicts detected
    • Reinstall problematic version
    • Update drivers and system software
  6. Escalate if Needed:
    • Contact TeamViewer support with detailed logs
    • Consult TeamViewer community forums
    • Consider professional IT support for complex issues

Future-Proofing Your Setup

To ensure long-term viability of your dual-version setup:

  • Documentation:
    • Maintain detailed records of your configuration
    • Document all custom ports and settings
    • Keep a changelog of modifications
  • Regular Maintenance:
    • Schedule monthly reviews of your setup
    • Test both versions after system updates
    • Monitor for security vulnerabilities
  • Upgrade Planning:
    • Develop a migration plan for when legacy support ends
    • Stay informed about TeamViewer’s version support timeline
    • Test new versions in a sandbox before production use
  • Disaster Recovery:
    • Maintain system backups
    • Create restore points before major changes
    • Document recovery procedures

Expert Recommendations

Based on extensive testing and professional experience, here are our top recommendations:

  1. For Most Users:

    Use the latest stable version as your primary and maintain one legacy version only when absolutely necessary. The performance impact of two versions is generally acceptable on modern systems with 8GB+ RAM and quad-core CPUs.

  2. For IT Professionals:

    Consider virtual machines for complete isolation. This provides better security and easier management, though with slightly higher resource usage. VM snapshots make it easy to maintain different versions.

  3. For Enterprise Environments:

    Implement a centralized management solution. TeamViewer’s ITbrain or similar tools can help manage multiple versions across an organization.

  4. For Developers:

    Use containerization (Docker) for maximum flexibility. This allows you to spin up specific versions on demand and ensures complete isolation between instances.

Conclusion

Running two TeamViewer versions on one computer is entirely feasible with proper planning and configuration. The key factors for success are:

  • Careful port management to prevent conflicts
  • Adequate system resources (especially RAM and CPU)
  • Proper isolation between versions
  • Regular maintenance and monitoring
  • Clear documentation of your setup

While there are some performance and security considerations, the benefits of maintaining compatibility with different systems often outweigh the challenges. For most professional use cases, the calculator at the top of this page will help determine if your system can handle the dual-version setup.

Remember that TeamViewer’s official position is to use only the latest version for security reasons. Running legacy versions should be a temporary solution while you transition clients to supported versions. Always prioritize security and stay informed about vulnerabilities in older software versions.

For the most authoritative information on TeamViewer’s version support policies, refer to their official community forums and support documentation.

Leave a Reply

Your email address will not be published. Required fields are marked *