
I asked about this from TV support, and they replied that the only way to get the hostname updated at the Management Console is to: TeamViewer Host registers the hostname to TMC (TeamViewer Management Console) with this temporary hostname (MININT-xyzetc).īUT, when the host is renamed at Windows, the changes do not reflect to TeamViewer Management Console. The computer gets a temporary name from SCCM/AD until it gets physically deployed to the field, in which stage it gets renamed with it's correct naming convention. We roll out our Windows desktop images through SCCM and deploy all applications at this stage, including TeamViewer Host component with predefined settings. However we ran into issues in testing phase with the way TeamViewer handles hostnames.

We are using TeamViewer 12 and are planning on deploying it on larger scale as a remote support and remote control solution.
