Blog

How to Change TeamViewer ID after cloning

If you’ve cloned a machine that already has team viewer installed, the clone will have the same ID as the source machine.  Each machine needs it’s own unique ID.  To get the clone to pick up a new ID by deleting 2 registry keys, ClientIC and ClientID.

for 64 bit Windows 7 I found the key here…
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeTeamViewerVersionX
for 32 bit Windows 7 and XP the keys are here…
HKEY_LOCAL_MACHINESOFTWARETeamViewerVersionX

Notes:
This won’t work on the source machine.  The calculation that determines the ID uses hardware identifiers which haven’t changed and TeamViewer will therefore produce the same ID as before.

 

Source http://eatrocks.com/?p=166

 

Posted in: Blog

Leave a Comment (6) ↓

6 Comments

  1. Coast Ranger January 24, 2013

    Thanks man, that worked the first time.

    reply
  2. Liam February 6, 2013

    The new solution for TeamViewer 8 (Provided by Teamviewer support) is:

    Please ensure you have updated TeamViewer to the latest version 8 from our homepage. After you have installed TeamViewer, please open the registry editor.

    Locate the registry path: HKEY_LOCAL_MACHINE\SOFTWARE\TeamViewer\Version8 (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TeamViewer\Version8 on 64-bit versions of Windows).

    Create a new DWORD (32-Bit) “MIDForceUpdate” with value 3.

    After this, please restart the TeamViewer service.

    Please do these steps on all machines with the same ID.

    Regards
    Liam

    reply
    • ARIK November 12, 2013

      i habe win 7 32 bit (X86)
      i use version 8
      i add the DWORD but still getting the some ID…
      what to do ??

      reply
      • Andrew January 7, 2014

        Are you doing it in the Source machine or the clone?

        reply
  3. Eugene February 22, 2013

    This is also good.
    Works well, doesn’t require installation or specific config, works behind gateways NAT as well as within one LAN. http://www.ammyy.com/en/solutions.html

    reply
  4. David Jeffrey November 2, 2013

    This cloning issue is a perfect example of why one should be extra careful about security when it comes to remote access and support. To help me sleep better at night, I started using RHUB’s appliance, which works from behind my firewall (as opposed to outside of it).

    reply

Leave a Comment