Teams add-in for Outlook breaking from my Classic Teams to New Teams
selahattin şadoğlu
I'm aware I can fix this on an individual basis by manually running the regsrv32 command to register the appropriate Microsoft.Teams.AddinLoader.dll for the version and architecture of the Office install and ensuing the reg entries for its load behaviour are set.
How can we fix this permanently so our Helpdesk is not constantly fielding calls about it?
Here is my environment:
Win11 & Office 2019 Pro Plus
reg file :
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\TeamsAddin.FastConnect]
"Description"="Microsoft Teams Meeting Add-in for Microsoft Office"
"FriendlyName"="Microsoft Teams Meeting Add-in for Microsoft Office"
"LoadBehavior"=dword:00000003
my script :
#Force close Microsoft Outlook/Teams
#Stop-Process -Name "Outlook" -Force -ErrorAction SilentlyContinue
#Stop-Process -Name "Teams" -Force -ErrorAction SilentlyContinue
Get-Process | Where-Object {$_.Path -like "*outlook*"} | Stop-Process -Force
Get-Process | Where-Object {$_.Path -like "*teams*"} | Stop-Process -Force
#Detect Microsoft Teams version/folder
$RootFolder = "$env:LOCALAPPDATA\Microsoft\TeamsMeetingAddin"
$FolderName = (Get-ChildItem -Path $RootFolder |
Where-Object { $_.PSIsContainer } |
Sort-Object |
Select-Object -Last 1).Name
$Path = Join-Path $RootFolder $FolderName
#Registered Teams Dll Files
& $env:SystemRoot\System32\regsvr32.exe /s /n /i:user $Path\x64\Microsoft.Teams.AddinLoader.dll
& $env:SystemRoot\System32\regsvr32.exe /s /n /i:user $Path\x86\Microsoft.Teams.AddinLoader.dll
exit $LASTEXITCODE
thanks,
Michael B. Smith
Run it as part of the installation routing or push a script. Which you already know how to do. 😊
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ntsysadmin/5453e330-c871-451f-aca5-132684d86a47n%40googlegroups.com.
maxcoder1
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/26bf6397850a4bf896695cec86825974%40smithcons.com.
Perisa, Nik
when you say 'breaking', what are the symptoms? We are currently in a pilot phase and have the toggle switch between the old and new Teams. A handful of people have found that when using the new Teams, if they setup a new Outlook meeting invitation, the Teams meeting link doesn't populate in the body of the invite. If they switch to the old Teams, the invitation generates the Teams links fine
Sent: Thursday, 19 October 2023 2:33:41 AM
To: ntsysadmin
Subject: [ntsysadmin] Teams add-in for Outlook breaking from my Classic Teams to New Teams
| EXTERNAL SENDER:
Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. |
Michael B. Smith
Yes, with small deployments so far. We used these:
https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client
https://learn.microsoft.com/en-us/microsoftteams/new-teams-desktop-admin
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CAKXd-rDQSG8wNkp1W5_3QFs%2B5umCVGXLJUHz5o8ouxHYH%2BQHCw%40mail.gmail.com.
maxcoder1
2. Once the policy is defined, I will assign it to a user.
3. Users will switch to new Teams via popup notification.
4. Lastly , after all the tests have been successful , I will remove old teams installer like below.
Start-Process -FilePath "msiexec.exe" -ArgumentList "/X $UninstallGUID /quiet" -Wait
C:\Users\xx\AppData\Local\Microsoft\TeamsMeetingAddin\1.23.24801 ->> new teams installer
#Stop-Process -Name "Outlook" -Force -ErrorAction SilentlyContinue
#Stop-Process -Name "Teams" -Force -ErrorAction SilentlyContinue
Get-Process | Where-Object {$_.Path -like "*outlook*"} | Stop-Process -Force
Get-Process | Where-Object {$_.Path -like "*teams*"} | Stop-Process -Force
#Detect Microsoft Teams version/folder
$RootFolder = "$env:LOCALAPPDATA\Microsoft\TeamsMeetingAddin"
$FolderName = (Get-ChildItem -Path $RootFolder |
Where-Object { $_.PSIsContainer } |
Sort-Object |
Select-Object -Last 1).Name
$Path = Join-Path $RootFolder $FolderName
#Registered Teams Dll Files
& $env:SystemRoot\System32\regsvr32.exe /s /n /i:user $Path\x64\Microsoft.Teams.AddinLoader.dll
& $env:SystemRoot\System32\regsvr32.exe /s /n /i:user $Path\x86\Microsoft.Teams.AddinLoader.dll
exit $LASTEXITCODE
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/b3a58b26e0db49808e724e708f7d2a3e%40smithcons.com.
Perisa, Nik
going back to do this, we have MS APPS 365 2308 and Win 10 and running your commands dont seem to do the trick in our setup. Even still, this is something MS really needs to address given they are close to going live with the new version
The only way we seem to get the add-in to work is to toggle Teams back to the old version, close and re-launch outlook and new meetings have the Teams links in the body of the email
We can then toggle back to the new Teams as long as we dont close outlook. As soon as you exit outlook and open again, the Teams addin is present but doesnt actually generate a teams link in the body of the meeting request...
To: ntsysadmin
Subject: [ntsysadmin] Teams add-in for Outlook breaking from my Classic Teams to New Teams
| EXTERNAL SENDER:
Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre. |