Your device will be assigned to Company ...message

Hi @JeanK,

we have the same issue. We actually use the /qn parameter as seen in this screenshot:

We are still getting the same question that @NGPIT showed in his screenshot.

Our license is Tensor Basic, so we have the actual license requirements. How do we fix this? We want to be able to roll out the host and apply customizations and policies during the rollout.

Hi @JeanK thank you for checking.

Unfortunately, this is not the fix we need. If we disable the managed group assignments, this has other negative implications.

Is it planned to have a way to silently roll out the TV Host without getting the prompt, like the old way?

Best regards,

Carsten

Hi @JeanK,

thank you. The issue is, that the Computers get created in Groups that afterwards need to be updated as mentioned in the Admin Portal.

Also, we need to manually manage permissions for every group that is created by manually adding agents with the corresponding permissions. Using managed group assignments, we have none of these pains, but the initially mentioned account assignment pop-up.

The "use managed group assignment" toggle (per your screenshot) only exists for the old custom module accessible via the old web Management Console. It does not exist in the new custom module interface accessible via the new web Management Portal. This has been an issue for a very long time.

This is the command we are using:

start /wait MSIEXEC.EXE /i "Teamviewer_Host.msi" /qn CUSTOMCONFIGID=xxxxxx

It does have the /qn flag and we are getting the end user pop-up to "Allow and Finish or Cancel" when deploying.

I have checked the custom module and there are no settings for group assignment to untick.

We are facing the same issue and cannot find your additional configuration / select the Rollout configuration / 'None'.

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.

@Mykyta_Makovetskyi

Thank you for your answer. ☺️

I have one question:
Did you really just name the TeamViewerHost.exe file “”TeamViewer_Host_Setup NO ROLLOUT.exe” and run it? Is the naming of the EXE file really important? I would have expected it to be in an installation parameter?

I would have distributed the application with the .MSI packages and the link to the custom module. Is that not possible or where is the problem? the .MSI or the custom module?

@Mykyta_Makovetskyi

So the script you shared doesn't work for me. The installation doesn't even run silently and I have to press everything.

My goal is that the installation and the assignment of the rollout configuration runs completely automatically and the device is then simply in the TeamViewer device list.

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

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."

}