Has anyone found a way of getting the "New Teams" to work within their images? I've installed into our image VM using the teamsbootsrapper.exe as per Microsoft's documentation, but when I power off and set as image it looks like sysprep makes the New Teams app unusable.
I need a way of ensuring it's in the image so we can add hosts to pools and have Teams ready to go. Right now we're having to run a scripted action after hosts are added to install New Teams but this is not practical.
Kevin Halstead so does running the entire new Teams script as is on a host now properly install new Teams without having to remove or edit any reg key and it all works?
Hello, I have successfully deployed the New Teams script (with sleep added) to 2 out of 3 hostpools. For some reason New Teams doesnt install on 1 of the hostpools (the script runs successfully). The 3 host pools use the same image, are all identical apart from fslogix profile location and an extra tag on the VMs in the hostpool that doesnt work. Any ideas? It is Windows 10 multi session.
Riordan Glarvey I am currently encountering that issue. Any fix?
By chance, does Teams also minimize to taskbar instantly and the "About" panel show "AVD Media Not Connected" while the sign-in error is there?
I know this is an old thread, but here's my script for installing the new Teams and the Outlook add-in. Tested on Windows 11, but should work on other versions as well: https://github.com/aaronparker/nerdio-actions/blob/main/scripts/image/201_MicrosoftTeams.ps1
I had the same issue with New teams, Explored lot of alternatives,
Below is the powershell script i used inside golden image and added to system startup via local computer policy under windows component - script -startup- powershell.
C:\temp\teamsbootstrapper.exe -p
If (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator') ){
Write-Error "Need to run as administrator. Exiting.."
exit 1
}
# Get Version of currently installed new Teams Package
if (-not ($NewTeamsPackageVersion = (Get-AppxPackage -Name *MSTeams*).Version)) {
Write-Host "New Teams Package not found. Please install new Teams from https://aka.ms/GetTeams ."
exit 1
}
Write-Host "Found new Teams Version: $NewTeamsPackageVersion"
# Get Teams Meeting Addin Version
$TMAPath = "{0}\WINDOWSAPPS\MSTEAMS_{1}_X64__8WEKYB3D8BBWE\MICROSOFTTEAMSMEETINGADDININSTALLER.MSI" -f $env:programfiles,$NewTeamsPackageVersion
if (-not ($TMAVersion = (Get-AppLockerFileInformation -Path $TMAPath | Select-Object -ExpandProperty Publisher).BinaryVersion))
{
Write-Host "Teams Meeting Addin not found in $TMAPath."
exit 1
}
Write-Host "Found Teams Meeting Addin Version: $TMAVersion"
# Install parameters
$TargetDir = "{0}\Microsoft\TeamsMeetingAddin\{1}\" -f ${env:ProgramFiles(x86)},$TMAVersion
$params = '/i "{0}" TARGETDIR="{1}" /qn ALLUSERS=1' -f $TMAPath, $TargetDir
# Start the install process
write-host "executing msiexec.exe $params"
Start-Process msiexec.exe -ArgumentList $params
write-host "Please confirm install result in Windows Eventlog"
Copy above script and create Powershell script and save in temp folder. Download the teamsbootstrapper.exe and copy to same folder.
All the issues regarding New team are gone.
NOTE:- we also run registry settings via Nerdio script to disable updates
Please sign in to leave a comment.
Comments (36 comments)