Just letting you know that I got an answer from TeamViewer and they said the quotes should still work but it seems Intune is truncating the command line and that causes problems.
RIGHT METHOD: ASSIGNMENTOPTIONS=-grant-easy-access WRONG METHOD: ASSIGNMENTOPTIONS="-grant-easy-access" TL DR, anyone facing the same problem, try leaving out the quotes in command line from ASSIGNMENTOPTIONS parameter and it should work. Still haven't gotten an answer to that but I'm quite sure that it's as intended/designed these days.
I got an answer from TeamViewer support just a few minutes ago and wrote to them about my solution and asked them to confirm if that really is how it's supposed to work (instead of some glitch). I tried the uninstall/redeployment cycle a few times again with and without the ASSIGNMENTOPTIONS -parameter and I consistently got the same result every time, so it really seems to be the solution to use the parameter without the quotes. All the official guides and older tips, tricks and forum posts tell you to use ASSIGNMENTOPTIONS="-grant-easy-access" but I tried "just for the heck of it" without the quotes so I used ASSIGNMENTOPTIONS=-grant-easy-access and it deployed without problems and the easy access/unattended access was enabled and all my host customizations and policies worked like a charm. We have the correct licenses in use.Īfter a lot more researching, googling, diagnosing and experimenting I found the solution myself by accident. I have also sent a ticket to TeamViewer support about the problem but I have not gotten any answers yet. I've not yet tried the deployment without that parameter, because I really need to have the easy access enabled on deployment. What might be the problem? I've tried researching and googling and I've found some indications that others have had the same kind of errors that ended up being caused by the ASSIGNMENTOPTIONS parameter. My command line for the host installation msi in Intune is like this: /qn APITOKEN=%YOURAPITOKEN% CUSTOMCONFIGID=%YOURCUSTOMCONFIGID% ASSIGNMENTOPTIONS="-grant-easy-access”Īnd I of course replaced the %YOURAPITOKEN% and %YOURCUSTOMCONFIGID% with the correct strings from the TeamViewer management console. I researched that error and Microsoft says it maps to ERROR_INVALID_COMMAND_LINE so it looks like there is something wrong with the command line parameters? This got me stumped because I carefully followed the guide and still got this error. At first everything seemed fine, installs were pending and now some are still pending but some have gotten an installation error 0x80070667. I tried to deploy the TeamViewer host via intune following the official guide.
0 kommentar(er)
