The machine-id change in Raspbian has also cause problems with other packages. I was able to workaround the problem with the following steps. Seems as if the machine-id tmpfs filesystem (which is what's causing the machine-id to change on every reboot) is only created if the actual file doesn't exist in the filesystem. 1. back up the current machine-id: sudo cp /etc/machine-id /etc/machine-id.old 2. unmount the machine-id tmpfs filesystem (recently introduced in raspbian): sudo umount /etc/machine-id 3. replace the unmounted filesystem with the backup: sudo cp /etc/machine-id.old /etc/machine-id 4. Reboot the pi and reset the teamviewer password one last time. I've tried this on a few Pis running the latest Raspbian update, both the IDs and Passwords are now preserved between reboots. More details on the machine-id issue here: https://raspberrypi.stackexchange.com/questions/66364/constantly-changing-etc-machine-id/66469
... View more
Make that four - we're experiencing the same behaviour with the latest version for the Pi. Even attaching it to a TV account didn't work for long -- it appeared and was accessible from the account as expected, at least until the Pi rebooted. Once it started back up, the ID and password were different -- as soon as I re-added the ID to my account and reset the password on the Pi, I was able to connect again.... until the next reboot. Running it as a daemon or from the console doesn't seem to make a difference. I downloaded the latest version of 11 for ARM and while you can't link that one to an account as indicated, I added it manually. The ID changed after the first reboot but not afterward. The password seemed to be preserved as well. I reverted back to teamviewer-host_11.0.63329 which doesn't have these symptoms. I should add that I'm using an up-to-date version of Raspbian Jessie -- both Lite and Pixel distros seem to be affected.
... View more