Client installations and device group assignments

Keppslock

I've created a device group called "Asia Laptops," an assignment to put laptops into this group, and a custom host installer for this where I have chosen the correct assignment. (I don't want these endpoints to be able to remote into other endpoints)

I download the installer, run it on a laptop, and the device does not show up anywhere. Not in my "Asia Laptops" device group or in "All." I have a group of about 5 technicians who will need access to about 200 laptops. We have a TeamViewer Corporate account with 30 users / 500 devices.

When I ran the install it prompted me to create an account which I skipped. I don't want the endpoints to be associated to any user accounts because they'll never initiate remote connections. We just want their laptops to be able to be connected to by our technicians.

What am I doing wrong?

WillOoaJ

We have this issue frequently as well, with seeming randomness. We have several dozen different device groups, all with host installers created. We download and install via the custom installer for the specific host. Much of the time, this works fine. Some of the time, the devices do what the OP describes here-- they do not seemingly show up anywhere. What we have found is that our main super admin can often locate them in the wrong group, for unknown reasons. The group they default to does not seem to be consistent. The instances of this occurring does not seem to be only within specific device groups. We're continuing to collect data.

OP-- workarounds we've had success (sort of?) with:

• We can sometimes locate the device in the wrong group within our own TeamViewer client apps or within the management console, but sometimes not both. If located, the devices can be correctly assigned to the right location. (Sometimes it doesn't show up in "All" even though it IS indeed in a group-- It's weird.)
• Sometimes only the super admin (eg the overarching account owner, for us) can do the above. In that case, the super admin may have to make sure techs are assigned permission to see the device in their own apps, regardless of which group the device ended up in.
• We will note the TV ID for all new devices as a fall back. Even if a device does not show up, the custom credentials set up during installation will of course apply.
• Sometimes even if we install from a custom host installer, we'll end up with a generic TeamViewer host install, not connected to our account at all. In this case we go into TeamViewer preferences on the device and add the device to our account. This definitely seems to result in a **bleep** of which group the device ends up in, and often can again only be seen by the super admin.
• Sometimes we have luck during the process if we go to the group in question in the TeamViewer app on our side and choose to "add computer," and then add the device with the ID and configured password. If the computer is in the wrong group, you'll get an error saying that the device is already added to the account owner's Computers and Contacts. In this case it's back to the first thing on this list.

We've probably had some errors or confusion in how we've set up our host installers-- It's something we've been doing for many years and have probably implemented various procedures along the way. We're trying to untangle everything, but if any of these things are known glitches or experiences for other business account holders, would appreciate hearing of solutions or workarounds, or things to target. OP, it sounds like your setup is less complicated group-wise than ours, but maybe some of our steps will lend some clues.