When they're plugged in at their final destinations, they generally do not have a keyboard/mouse and the only variables are the Monitors and/or Internet Service Providers.īut they're always connected via LAN with DHCP or a pre-configured and hidden WLAN AP that is already stored in the device settings. But does the protocol have anything to do with the ID? I use the same device policy to force settings on all systems to be the identical in TeamViewer. Something to note, I have my policy set to prefer UDP connections, but I notice in the log files it tries to connect via TCP. When they arrive and are turned on, I've noticed that whenever a device is behind a highly secure network it causes the ID to change after it is rebooted or even before at times. Sometimes they will be offline for days, sometimes weeks, sometimes hours. They get added into our account via the deployment installation tool assigned, grouped and renamed before leaving our warehouse via UPS/Fedex and never have any issues when they're in our hands. I always rename the computer to its hardware serial number before it hits the WAN and I attach/associate the device to my account so that the ID will always be different.and avoid the 'cloning' issues some experience. I use a custom image of a single device on the same/similar hardware time after time after time. Never had this many issues until this year. We've been doing this for nearly 10 years and using TeamViewer for almost half of that time.

Dealing with custom built and managed Digital Signage device endpoints. I deal with hundreds of devices on a daily basis, sometimes send out 10 machines to a single site and restart them several times before they arrive at their final destination.

Used to happen once a year, but now its happening every week.

Teamviewer 13 how to get new id