This thread has been difficult to follow, mostly because the two most active participants (recently) seem to be ESL, and one of them insists on analyzing the psychology instead of the technology..
Here is how I see the issue:
Same problem here. I thought I made a mistake a while ago when storing the Teamviewer ID's of about 6 Windows 2012 R2 servers in our password database because I couldn't connect anymore with the ID's. Logged in to each server via another way and found out the ID was different from what is stored in our password database. Fine, noted all ID's and stored them again in our password database. Did a check today, tadaaaaaah....ID's changed again. This is pretty problematic in a business environment. How can you not get such basic stuff right Teamviewer? Do you think I have time for this stuff?
We use a premium license btw.
This happened once on a server machine for a client. As a backup, I install DWSERVICE.NET and so far never had another issue as I'm able to log in via DWSERVICE. You create an account, then download the client and install. It's a bit basic but works as a web app and can do dual monitors, transfer of files and is for most part, free.
I do know that you can not clone a hard drive and expect to have the same ID. Also, virtual machines tend to be a problem.
When Teamviewer came out for me, it was version 7 and worked great. Problems started with Version 11 and up and got worst with subscripton based products. I don't expect them to be free forever but the new pricing model prices me out of updating.
The problem still exists in April 2019. And it is not related to cloning or HW changes at all. (Here are two small office PCs (Win) which are about 5 and 10 years old and the last HW change for one of them was a SSD several years ago).
I guess we are lucky, that we live in a perfect enough world that at least birthdays, social security numbers, number plates of cars etc. are not changing that randomly.