![]() This applies to those of us who deployed Teamviewer 15 or newer and who are using "Device Groups" to control their managed devices instead of Computers and Contact. Here is an updated remediation for the above proactive remediation that uses the new Managed Devices endpoint. I used the token that we use to install the client, instead of creating an app/script token in the management console. Tweaked it a bit to remove the $USERNAME part as I don't want that functionality, and detect if the ClientID is in WOW6432Node or not. Using the script above and the comments, i created a detection and remediation scripts to run weekly using proactive remediation. Our shared devices we do set a specific name so we can locate them physically, so our techs would have to not only rename on the device but also in the TeamViewer console which is a pain. We got around that by deploying to all devices and excluding a dynamic device group that targets the temp name. You can read more about some of that here - Teamviewer Account Assignment. If you dont have a sleep period long enough (I personally use 60 seconds) or have a retry statement the account assignment will fail. We struggled with TeamViewer & Intune where if the host gets installed during pre-provisioning, the alias would be set to DESKTOP-%RANDOM% instead of the device naming template used which gets applied after the user provisions the device. The reason for this is the TeamViewer services need to be started and if you try before that it wont work. Thank you for this! This has been annoying me that they don't have this functionality built in. From what it seems it does look like if this can get on the machine it would actually solve the naming issue. Let me know if you guys can see anything I missed or I got incorrect. Then it's calling out to the TV Update Server or some TV Server that's hosting our instance of machines and presumably updating the machine names based off of what it grabbed from the device using the $env commands. and is then doing something with the TV Client ID, but I'm not sure what "r" is. $rid is going to the TV Installation in the Registry. Token would be the token of your TV Installation Package. I believe the $header is creating a new default Registry Object with the login credentials needed for accessing your TV Account. What I need help with is what exactly the commands are asking for and what exactly it's doing. I'm using the manual method to apply this now, as I simply can't wait : ) From talking with the TV Technician, I was informed that this is an ongoing feature request with them and they are most likely going to incorporate this with their client somehow in the future. I'm not sure exactly how this will interact with the TeamViewer client in the future but as of now, I plan to deploy this script via Intune.if I can get it tested and working. For those who haven't already found a solution for this, when I had called for support last week, someone at TeamViewer was nice enough to give me the script they are currently bouncing around amongst themselves that addresses this issue. If your reading this and you have TeamViewer deployed in your organization then you'll understand the pain of TeamViewer not having machine name auto updating capabilities.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |