Teamviewer deployment via Intune - MSI and Win32 not deploying
Hi all,
I have see a few discussions on this forum where a few workarounds have been found around the documentation which seems to not be to accurate.
In the first place, it seems there are 2 guides which can be followed to deploy Teamviewer via Intune:
1)Deploy TeamViewer on Device Groups via Microsoft Endpoint Manager - TeamViewer Support
2)Intune Integration - Installation and User Guide - TeamViewer Support
These use different methods, MSI and Win32, which I totally understand can be used and SHOULD be working, however they lack of details.
The MSI guide, which seems to be also the easiest to follow (due to the few steps on it) would just require to put the API token and the Config ID in the script, get the MSI uploaded to Intune and assign the App to a group.
This doesn't work all the time, and by looking at other forums, this seems to be a common issue.
The second method involves a repackaging of the MSI + into a IntuneWin file + additional setup on Intune.
In both cases there are a lot of details lacking, like:
1) Managed groups don't have an API token when creating a custom configuration, can we then deploy this without the API token and just the config ID?
2) Is the MSI in the configuration page a re-packaged MSI file which is ad-hoc configured for that specific setup(highly doubt)
In the few successful cases of deploying the app as Win32 package, I got the following errors:
1) App was deployed, but this didn't have any configuration applied
2) The app ends up not installing due to the long installing time (timeout set to 3 hours).
Does anyone have a solution to this?
Comments
-
Hi again,
I have now found another guide which seems to be the same, again, but is more updated.
Still lacking of details, as there is another discussion on this forum mentioning this. Auto Device Assignment (Modern) — TeamViewer Support.
Can we please have a detailed list of steps we can follow to deploy this?
0
