I deploy a teamviewer host client , but have assignment message need to acept by manual, can I automatic allow this ?
Hello @NGPIT and a big welcome to the TeamViewer Community family!
We recommend following our Mass deployment on Windows - User guide.
In step 9, you'll find the command line we recommend using:
start /wait MSIEXEC.EXE /i "PATH_TO_MSI_FILE\TeamViewer_Host.msi" /qn CUSTOMCONFIGID=YOUR_CUSTOM_CONFIG_ID timeout /t 30 /nobreak "C:\Program Files (x86)\TeamViewer\TeamViewer.exe" assignment --id YOUR_ASSIGNMENT_ID
The /qn parameter will ensure that no assignment confirmation message will pop up.
Let me know if this has worked for you!
/JeanK
Hi @NGPIT,
Sorry, we didn't clarify this in the first place.
Indeed, deployment capabilities are only available for Corporate license holders.
Correct, in this scenario, the .exe cannot be used.
We thank you in advance for your understanding.
Hi @Metisak,
You should get the assignment ID from the "Rollout set-up" menu:
It looks like "0004CoHRChDj44qAJ7kR76FVkAVnlRS4EigIACAAAgAJAD05CYhz_bauIxw8Htn9MVB5Yrjj4hA93I4X5c5wwh9IGkAAAgojXYZss4ZHX4TwSHAPbFIikDjGHjnA0YTfcOhN4X8WMsRW4J57WKpp2sU3btBeZJ6bw1Aj0oL9KZ1JmJFuIAEQyLfNuQM=" I hope this helps you!
The following solution has now worked completely for me and I have adopted it in my Intune installation routine. The installation is carried out via a PowerShell script:
$TeamViewerHost = ".\TeamViewer_Host.msi" $TeamViewerCustomConfigID = "XXXXXX" $TeamViewerAssignmentID = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
Write-Output "Installing TeamViewer Host..." #Start-Process -FilePath "msiexec.exe" -ArgumentList "/i "$TeamViewerHost" /quiet /norestart" -Wait -NoNewWindow
"$TeamViewerHost
Start-Process -FilePath "msiexec.exe" -ArgumentList "/i "$TeamViewerHost" /quiet /norestart CUSTOMCONFIGID=$TeamViewerCustomConfigID" -Wait -NoNewWindow
Write-Output "Wait 30 seconds to ensure that the installation is complete." Start-Sleep -Seconds 30
if (Test-Path "$env:ProgramFiles\TeamViewer\TeamViewer.exe") { Write-Output "TeamViewer installed successfully."
# TeamViewer rollout configuration Write-Output "Configuring TeamViewer Host with Config ID: $TeamViewerAssignmentID" Start-Process "$env:ProgramFiles\TeamViewer\TeamViewer.exe" -ArgumentList "assignment --id $TeamViewerAssignmentID" -Wait -NoNewWindow Write-Output "TeamViewer Host configuration successfull."
} else {
Write-Output "TeamViewer Host configuration failed."
}
If you use Intune and use the command /qn CUSTOMCONFIGID=xxxxxx you would get the pop-up message and be required to accept it.
It would be nice if you could assign it with just the assignment ID after the customconfig.
Like; /qn CUSTOMCONFIGID=YOUR_CUSTOM_CONFIG_ID assignment --id YOUR_ASSIGNMENT_ID
Hi all,
I've talked with our engineers and come back with (hopefully) the solution. 🙂
When using the new interface and deploying TeamViewer via script, the rollout configuration in the module's settings must be set to None.
Please give it a try. You shouldn't see the pop-up; the installation should occur without user interaction.
Looking forward to hearing from you.
Dear TeamViewer Support Team,
I want to deploy the TeamViewer Host for unattended remote support on my Microsoft Teams Room systems (Windows 11) via Microsoft Intune.
The installation should be completely automatic on the device level without any subsequent intervention. After the installation, the device should be assigned to a TeamViewer device group so that authorized users can easily connect to the device.
I have created the script installation via Intune as described in the instructions. The .bat file executes the following during installation:
start /wait MSIEXEC.EXE /i "%~dp0\TeamViewer_Host.msi" /qn CUSTOMCONFIGID=***** timeout /t 30 /nobreak "C:\Program Files\TeamViewer\TeamViewer.exe" assignment --id **************
The software installs without any issues, but after the installation, it is still necessary to start/open the Host once and confirm the assignment. Only then does the device appear in the TeamViewer device management group. Since the devices are distributed and not on-site, someone always has to be there.
What is the solution to make everything run automatically so that I don't have to touch the device after installation and can simply access the device through the device group it is assigned to? Please support.
Quite normally from our TeamViewer Admin Portal under “Rollout configuration”. I should perhaps add that we have a Tensor Basic subscription.
Are you making two different options? One with ConfigID and one without?
Install TeamViewer Host Write-Output "Installing TeamViewer Host..."
#Start-Process -FilePath "msiexec.exe" -ArgumentList "/i "$TeamViewerHost" /quiet /norestart" -Wait -NoNewWindow
I see the first one is commented out, but this can be confusing for someone who may not know what they are looking at
I've tried your script and it's not fixing the issue:
First of all, this line needs to be fixed:
It still asks to "Accept and Finish" ("Zulassen und Fertig stellen")
Also, in my case it's not assigning the computer to the group and easy/unattended access also needs to be manually configured. What's going on?
That's a new one for me bud… if it works for you, then keep doing it! Personally, I think creating multiple variables in a script only guarantees that you will have multiple scripts / prompts to use when running it for various situations… This may be fine for you, but I needed a way to do mass installs and only make minimal changes when updates occur.
OK.
For the next install/upgrade test, I added an extra restart, and also let the computer sit a bit longer.
The message did not display.
So, just wait a bit longer and you won't get it :)
We IT folk can be a bit impatient sometimes.
I have same question.
When run this command "C:\Program Files (x86)\TeamViewer\TeamViewer.exe" assignment --id YOUR_ASSIGNMENT_ID
there is a popup windows that prompts to Allow and Finish or Cancel.
Looking for option to not show that window and to Allow assignment.
I believe the file name doesn't matter.
When installing with the given .MSI package I had some issues, though now can't remember what exactly. Also, I think .MSI was installing outdated TeamViewer so I suppose it's outdated.
Where did you get .MSI installer?
Hi @elbcloud_casi,
With the process we described in Mass deployment on Windows - Overview, there shouldn't be any negative implications.
If so, would you tell us which negative implications exactly you mean?
Hello @Mykyta_Makovetskyi, i am trying same as you. Installation of EXE is okay, silent etc all good. But assigment is not working as expected i think. We have just Premium license. In our portal there is no visible assigment ID but i think it is visible in weblink of assigment policy edit. Could you just confirm for me, that ID is in format - 8digitis-4digits-4digits-4digits-12digits so i am looking for right parametr?
i also dont have option to select "roll-out setup to "None"" in my portal :/ is it still think of license topic?
Hello @JeanK
It seems that my authorization only allows installation using an executable (exe) file. If that's the case, is there any other way?
Hi @Kplatte, hi @NGPIT,
Exactly - and this is expected, as your command line does not contain "/qn".
To make sure no window pops up, you must use the /qn parameter in your command line, as in the example I shared:
Let me know if it worked with a command line including /qn.
I don't want to step on @FlorianO93 's toes, but I feel like my script gets the job done a little better…
I'm using Intune, but the scripts can be used individually / manually too… go through it and let me know how it goes for you… I have TeamViewer installing silently and updating into the correct groups without any user input. So far, so good.
Like this
So that was just the solution that worked for me and I shared it :) I don't know which one is "better" or "more sensible", but it led me to my goal. 😚
True. My clients are manageable as of now but I'll be coming back to this thread some day I believe 😂
Huh, that's not good we get the popup like that… Which settings are you doing in the backend? Our command in Intune is: msiexec /i "TeamViewer_Host.msi" /qn CUSTOMCONFIGID=<ID> APITOKEN=<API_TOKEN> ASSIGNMENTOPTIONS="--grant-easy-access"
The above is my teamviewer host (choose your policy in the dropdown)
These are my commands in intune:
Install command powershell.exe -ExecutionPolicy Bypass -File .\install_teamviewer.ps1 Uninstall command msiexec /x "{PRODUCT_ID}" /qn
Install command powershell.exe -ExecutionPolicy Bypass -File .\install_teamviewer.ps1
Uninstall command msiexec /x "{PRODUCT_ID}" /qn
install_teamviewer.ps1 has the above mentioned code in it. it's packed with intune prep tool.
$currentDirectory = Get-Location msiexec /i "$currentDirectory\TeamViewer_Host.msi" /qn APITOKEN="API_TOKEN" CUSTOMCONFIGID="CFG_ID" ASSIGNMENTOPTIONS="--grant-easy-access"
prep tool:
.\IntuneWinAppUtil.exe -c path\to\source\ -s path\to\teamviewer_host.msi -o path\to\output\
Hi @JeanK .
Regarding this.
I am getting the same behaviour, and I can assure you I am using /qn for the install.
And indeed, the install is silent and respecting the /qn switch, but when the customer opens the remote support app for the first time, that is when we see the prompt to confirm the company assignment.
Is there an option in the policy that can stop it from appearing?
Additionally, this used to work with the old script (using the API). It seems the new script behaves differently.
More information.
I only get that additional window when I sign in as Local Admin and open the Host application.
I do not get it when I sign in as a standard domain user.
Interestingly, it says the machine has easy access for 5 managers - great. It says it belongs to an organisation. But it does not say it is assigned to an account.
Is that normal?
I do seem to have easy access control to it, but I assumed it would be assigned to an account.
I'm using this method in the batch file: "C:\Program Files\TeamViewer\TeamViewer.exe" assignment --id <MY_ID> --device-alias=%ComputerName%"
@TeamMngr I'm glad you could fix this by adding an extra restart. 🙂
Also, thank you so much for sharing your solution with the community!
Hope to see you posting here soon,
I have packaged the custom module Host MSI that I downloaded from Teamviewer Full Desktop > Admin Settings > Custom Modules.
I packaged it as a Win32 Intune package along with a BAT file (command below), with my customconfigid and apitoken.
@echo off start /wait MSIEXEC.EXE /i "%~dp0\TeamViewer_Host.msi" /qn CUSTOMCONFIGID=[My_CustomConfig] APITOKEN=[My_APIToken] ASSIGNMENTOPTIONS="—alias %COMPUTERNAME%_%USERNAME% --reassign --group UK-Computers" DESKTOPSHORTCUTS=0 AUTOACCEPT=1 /L*v C:\Temp\TVHostCompInstall.log
It installs fine, the config is listed in logs and is saved in the Teamviewer install folder (C:\Program Files\Teamviewer), but it does not appear in management console.
I need to terminate the running Teamviewer task on the device, re-run it with an account that has local admin privileges. The device then appears in my management console. This is the ONLY way I can get devices to appear in my console if I push out the app via Intune.
This is crazy stupid, Teamviewer please sort this out, it's literally been happening for years.
I went back to using API Tokens without the "Managed Group Assignment". It works well for me using this:
