Force Update via Policy - After Bulk Install
Hi All.
We have rolled out a little while ago 15.50.5.0 as bulk custom using MSI.
I am wanting to force all installs (host) to a specific version.
I have updated policy with the following:
Check for new version - Daily *Enforce
Install new versions automatically - All Updates (includes new major versions) *Enforce
Update to specific version - {chosen version} *Enforce
Now on clients host installs, it presents saying there is new version but wont actually install it.
I have searched quite a fair bit, have been unable to find exact reason why.
Yes we did bulk install using MSI, we are on tensor. Surely doing MSI is not the cause for it to not auto update?
I do not want to have to push out via InTune or SCCM another update when this option is meant to work.
Can someone help and provide any examples if they have got it to work some how?
I have also created a test Device Group to see if i can do it via that but nope there is no option to. Why can't we select all and force to update instead of having to remotely jump on and update them or run a powershell / cmd etc.
Best Answer
-
Hi @Tom76dc,
I can confirm that to update your clients via TeamViewer policy, you only need the following two policy settings:
- Check for new version: Enabled and enforced
- Install new versions automatically: Enabled and enforced
I spoke with our engineers just to double-check the "TeamViewer Shutdown" setting, and I was told that it is not needed. This parameter won't impact the update process.
All the best,
/JeanK
Community Manager
0
Answers
-
Greetings. I have deployed custom hosts with the configuration to auto-update.
This is not occurring.
These machines are on my domain and the end users do not have admin rights to install software.
Is there a way to allow these workstations to be able to auto update?
0 -
Is there any update? Does the automatic host update work on win11 clients if the policy is set? is their any need for local admin rights? do the user has to push the updates manually? i dont understand why we cant find any hints to this important topic für the business :-(
0 -
Hi all,
I checked with our R&D team and I can confirm that this is a known issue.
Our teams are working on a resolution.
I'll make sure to update the thread once I get more information to share!
Thank you in advance for your understanding.
/JeanK
Community Manager
0 -
Hello,
did you find a solution for your problem?
We're experiencing a similiar problem with the MSI Rollout and the Teamviewer Policys,
but without any solution that doesnt need additional powershell scripting.0 -
Thank you for bringing this up again, @TimoPrz.
We are sorry that you and @DarrynH are having issues installing the new versions automatically via policy.
Since it's difficult to determine why the policy does not work as expected without further information, we recommend contacting our support team. Our support teams will be happy to take a close look into your cases.
In your specific cases, we recommend submitting a ticket and attaching the support collector's data.
Please keep us and the other Community members posted on how it goes.
Best,
NadinGerman Community moderator 🖤 Moderatorin der deutschsprachigen Community
0 -
Hello.
Do you have any new information on this? We've also installed the HOST and want to enable auto-update on devices that have been with users for a while. Ideally, we'd like to do this via a registry entry that we can provide. Users typically work without admin rights.
When I set the auto-update to ON, I do see a new Reg Key. If I restart TeamViewer now, I only receive a notification when I actively open the TeamViewer window and then see that an update is available. However, I still have to click on the update notification to install it. To me, that doesn't seem like auto-update. How long does it take for the update to be automatically applied?
I'm also very interested in why auto-update isn't turned on by default. What's the reasoning behind that? A software like TeamViewer should always be up to date, shouldn't it?
1 -
Hi guys,
same issue here. During the installation of a client we're using the the .msi for installing our edited TV-Host and assigning the client to our company account + group (with automatic policy assignment). Our employees don't have local admin rights on their devices.
In our assigned policy we enforced the automatic update + the daily search for new updates. No client can update automatically so i am searching for a solution too. How we can handle this? We need to update hundreds of TV-Host clients to be up to date.
Thanks in advance and looking forward to your support/ideas 😊
Best regards and enjoyPhil
1 -
-
Did you ever find a solution?
We are in the same boat. We install the host with and None of the 'update' related options work for us.
We use tensor.
The teamviewer knowledgebase is really unhelpfull about this topic. Loosing too much time on this.
Not in the policy reference, neither specific page about how to update the teamviewer clients in the enterprise.
Regards,
Tom
0 -
I've spent several frustrating days trying to figure this out. I'm running into conflicting information regarding TeamViewer's policy for updating clients.
TeamViewer support claims the policy should work, but community feedback suggests it doesn't. The TeamViewer policy knowledge base is unhelpful; it simply lists the available policies without explaining any limitations or constraints on their functionality. I haven't been able to find any documentation (blog posts, knowledge base articles, etc.) that clearly explains the process for updating TeamViewer clients via policy.
If this policy is genuinely ineffective, I'm confused as to why it's even offered in the production environment. Is there something I'm missing?
0 -
@Tom76dc @TimoPrz
Hi all,
So I have finally got this working. Sorry for delay and not replying.- Initially I found our firewall was blocking the download, although the devices registered stating new update available, I checked logs and found FW was blocking the physical download
- I then created a new Policy, cloning the existing settings from the current active one. I then modified the below….. and then tested on a few devices and once confirmed working then a device group at a time.
- I then found that because I had 'Disable TeamViewer Shutdown' set to Enable and Enforce. This was stopping TeamViewer from being able to shut itself down to complete the install.
— So I turned this off (ie. deleted) until all devices were updated and then added it back in to the policy later..
— I no longer have to change this setting as TeamViewer now can shut itself down to do the update even with this setting Enabled/Enforce - I then changed the 'Install new versions automatically' to ALL UPDATES (includes new major versions) and set to Enforce
- I then changed 'Check for new version' to DAILY and set to Enforce
- I let TeamViewer do it's thing over a 10day period… Reason for this was because the previous settings in TV seemed to cycle over a 7day period especially with the weekly setting on Updates.
- I made sure that I did NOT have the 'Update to specific TeamViewer version' option in the policy.. Make sure this is deleted.
Once I found that all of my devices were updated to the latest (over 15.60), I then modified the policy and added 'Update to specific TeamViewer version' and chose my 15.61.** version I wanted.
May seem weird that the above worked, but this is how I now have all of our organisation devices updated.
I have since upgraded all devices to another version just by changing the selected version in the drop down. That is all I do now and it works seamlessly. Although I still have the check daily option, it still may take a few days for all devices to update.
Just to Clarify: Once I got the above working, I don't create a new policy each time. I just change the 'Update to specific TeamViewer version' drop down to my chosen version and the policy syncs automatically to all devices. The end users don't get any pop ups that I have seen or been advised of. The application just updates by itself.
Hope this helps you out
I only had a handful of devices (out of over 1200) that didn't do the update. So I pushed out a task sequence via Intune/SCCM to force uninstall and force install the version I wanted (15.60.** or newer) and the policy automatically kicked in and updated accordingly to my version I set in the above steps.2 -
It's great to hear it's working for you!
Before your reply, I contacted TeamViewer support yesterday, and they provided some crucial information. They stated that the client update process only initiates when a user/device has been idle for at least five minutes (no mouse movement, keyboard input, etc.).
It's interesting that your TeamViewer clients started updating within 10 days. Perhaps the "Check for new version of 1 week" policy's timestamp was preventing daily update checks from occurring.
Could you confirm that the following policy configuration is correct for updating TeamViewer clients?
Required Policies:
- Policy - Check for new version: Daily (enforced)
- Policy - Update to specific TeamViewer version: 15.60.** or newer (enforced)
Important Note: These policies should not be combined with:
- Policy - Disable TeamViewer Shutdown: Enabled
i'm looking forward to your answer,
Tom
0 -
Hi @JeanK ,
Thanks for the link to the other blog post; I've posted my reply there.
I think that TeamViewer could significantly improve their documentation on this. A dedicated KB article explaining the update process in detail would be invaluable. Enterprise application lifecycle management is critical, and the current lack of clear guidance from TeamViewer on this topic is frustrating.
I'll be sharing any further findings I have here as well.
Kr,
Tom
1 -
Hi @Tom76dc,
I can confirm that to update your clients via TeamViewer policy, you only need the following two policy settings:
- Check for new version: Enabled and enforced
- Install new versions automatically: Enabled and enforced
I spoke with our engineers just to double-check the "TeamViewer Shutdown" setting, and I was told that it is not needed. This parameter won't impact the update process.
All the best,
/JeanK
Community Manager
0
