If you need to perform a packet capture under Windows without having to install Wireshark, here are some netsh commands:

netsh trace start capture=yes tracefile=c:\net.etl persistent=yes maxsize=4096 filemode=circular overwrite=yes report=no

When you are done with your capture do:

netsh trace stop

This will take some time.

You will see the files under C:\net.etl and net.cab

As a follow up to my last article regarding Microsoft Teams NEW Addin missing in Outlook https://www.ajni.it/2024/03/microsoft-teams-lightweight-teams-meeting-addin-in-outlook-missing/, this script might help you if there are still some issues especially on Terminal Services/RDS 2019/2022.

This script registers Microsoft.Teams.Addin.Loader.dll as the current user, so it has to run at logon.

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"

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

$TMAParam= '/s /n /i:user "C:\Program Files (x86)\Microsoft\TeamsMeetingAddin{0}\x86\Microsoft.Teams.AddinLoader.dll"' -f $TMAVersion
Start-Process "C:\windows\System32\regsvr32.exe" -ArgumentList $TMAParam

A follow-up on the last post here is another way to run msiexec through PowerShell.

For example, here is how you can install OCS inventory agent with some parameters. OCS is an open source inventarization system.

Start-Process -FilePath .\OCS-Windows-Agent-Setup-x64.exe -ArgumentList ‘/S /NOSPLASH /NOW /SERVER=https://inventory.ajni.it//ocsinventory /TAG=”a” /SSL=0’

References:

https://www.ajni.it/2024/04/run-msiexec-transforms-with-powershell/

Microsoft Intune or Endpoint Manager is awesome but also a pain if something does not work as expected. For example, if you create a package that simply imports a reg file, it will import the keys under SOFTWARE\WOW6432Node (WOW or SysWoW means Windows32OnWindows64). This is normal behaviour because Microsoft Intune Extension runs as a 32 Bit process on Windows. Therefore it does not know about the 64 Bit architecture.

So the solution is to run the reg command with this option. This will import the keys directly under SOFTWARE\…

reg import file.reg /reg:64

There are other approaches to this but my solution works and is the fastest in my opinion.

If you are having issues with Microsoft Teams Meeting Addin missing in Outlook, here are a few tips:

1. Make sure Microsoft Teams Meeting Addin is installed and present in the Control Panel
2. Navigate as admin to C:\Program Files\WindowsApps\MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe (Version number might have changed)
3. Copy MicrosoftTeamsMeetingAddinInstaller.msi
4. Run the following command:
   • msiexec.exe /i “MicrosoftTeamsMeetingAddinInstaller.msi” ALLUSERS=1 /qn /norestart TARGETDIR=”C:\Program Files (x86)\Microsoft\TeamsMeetingAddin\1.23.33413\” (Version number might have changed)
5. Also, make sure this key is set on the user side. You could make a GPO or Intune script for that
   • 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