Microsoft Configuration Manager and Intune (Enterprises/Paid) > Report Update Detection Issues (Enterprises Using ConfigMgr and Intune)

Teams machine installer detection issues

(1/1)

Robd:
Good afternoon,

We have recently enabled CMApp packaging for Teams x64 machine wide installer and found that Microsoft are reusing MSI product code GUID's whilst incrementing the product version.
The PMPC detection script is identifying that the GUID & product version is mismatched / application not detected, then it is matching the GUID only and reporting installation detection.

I have worked around the issue by removing the MSI GUID from the detection script, is it possible to handle this in a future published catalogue?
Happy to raise a product enhancement as well  on configuring the detection script with MSI GUID & target version :)

Verbose output of the detection script.

VERBOSE: Current User =
VERBOSE: Running as system = False
VERBOSE: LogPath =
VERBOSE: Current User =
VERBOSE: Current User Is Admin = True
VERBOSE: Will search the following registry paths based on [Architecture = x86] [HivesToSearch = HKLM]
VERBOSE: registry::HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*
VERBOSE: Extracted version  from Logi Firmware Update Tool for MeetUp
VERBOSE: Extracted version  from Logitech Camera Settings
VERBOSE: Extracted version  from Microsoft OneDrive
VERBOSE: Extracted version  from Microsoft Azure Information Protection
VERBOSE: Extracted version  from Teams Machine-Wide Installer
VERBOSE: Result of comparing Current Version 1.2.0.17057 to Target Version 1.4.0.7174 for the purpose of Detection rule = False
VERBOSE: Extracted version 11.0.60610 from Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.60610
VERBOSE: Extracted version 12.0.40660 from Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.40660
VERBOSE: Extracted version 14.16.27012 from Microsoft Visual C++ 2017 Redistributable (x86) - 14.16.27012
VERBOSE: Extracted version  from WUFB - PROD
VERBOSE: Extracted version  from Teams Machine-Wide Installer
VERBOSE: Found Teams Machine-Wide Installer matching based on MSIProductCode {731F6BAA-A986-45A4-8936-7C3AAAAA760B}
VERBOSE: Extracted version 14.16.27012 from Microsoft Visual C++ 2017 X86 Minimum Runtime - 14.16.27012
VERBOSE: Extracted version 12.0.40660 from Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.40660
VERBOSE: Extracted version 14.14.26429 from Microsoft Visual C++ 2017 Redistributable (x64) - 14.14.26429
VERBOSE: Extracted version  from Office 16 Click-to-Run Extensibility Component
VERBOSE: Extracted version  from Office 16 Click-to-Run Localization Component
VERBOSE: Extracted version 11.0.60610 from Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.60610
VERBOSE: Extracted version 11.0.60610 from Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.60610
VERBOSE: Extracted version  from Microsoft Intune Management Extension
VERBOSE: Extracted version  from Adobe Acrobat Reader DC
VERBOSE: Extracted version  from Microsoft Search in Bing
VERBOSE: Extracted version  from DefaultPackMSI
VERBOSE: Extracted version  from Microsoft Azure Information Protection
VERBOSE: Extracted version 14.16.27012 from Microsoft Visual C++ 2017 X86 Additional Runtime - 14.16.27012
VERBOSE: Extracted version 12.0.40660 from Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.40660
VERBOSE: Extracted version 11.0.60610 from Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.60610
VERBOSE: Extracted version 12.0.40660 from Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.40660
VERBOSE: Extracted version  from Intel(R) Processor Graphics
VERBOSE: Extracted version 12.0.30501 from Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501
Installed

Cody Mathis:
At this time this is how the script will function when generated by the Publisher.

We have plans to improve the Teams Machine Wide Installer, but at this time they are not in place.

What you have done is the current workaround.

GeoSimos:
Between us, the Teams "machine wide" installer is not such a thing, what it does is a staging of the installation and then a per-user install when the user logs on. Pretty weird for Microsoft's standards if you ask me..... :o

daniel.stewart:
I know this is a bit old, but can you share how you edited the script to remove the GUID? I'm running into this issue where it won't repair (exit code 1603) or uninstall (exit code 65535) from Software Center due to the GUID/Version mismatch. I tried removing these two lines and get a different error (exit code 1638).

[string]$AppMSICodeToSearch = '{731F6BAA-A986-45A4-8936-7C3AAAAA760B}',
[Parameter(Mandatory = $false)]

Uninstall error log without any edits to script:
Starting ScriptRunner (V2.1.3.0) with 1 argument(s)   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
Current culture info name is: en-US   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
Running as NT AUTHORITY\SYSTEM (Admin)   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
Working directory: C:\WINDOWS\ccmcache\8g   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
System path is C:\WINDOWS\System32   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
Argument #1 is: /UninstallPackage   Arguments   4/26/2022 9:23:05 AM   1 (0x0001)
Inspects argument: uninstallpackage   Arguments   4/26/2022 9:23:05 AM   1 (0x0001)
Uninstallation mode requested   Arguments   4/26/2022 9:23:05 AM   1 (0x0001)
App uninstallation mode requested.   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
Argument #1 is: /MainFile=Teams_windows_x64.msi   Arguments   4/26/2022 9:23:05 AM   1 (0x0001)
Inspects argument: mainfile=teams_windows_x64.msi   Arguments   4/26/2022 9:23:05 AM   1 (0x0001)
MainFile is: Teams_windows_x64.msi   Arguments   4/26/2022 9:23:05 AM   1 (0x0001)
Argument #2 is: "/MainArg=Reboot=ReallySuppress ALLUSERS=1"   Arguments   4/26/2022 9:23:05 AM   1 (0x0001)
Inspects argument: mainarg=reboot=reallysuppress allusers=1   Arguments   4/26/2022 9:23:05 AM   1 (0x0001)
MainArg is: Reboot=ReallySuppress ALLUSERS=1   Arguments   4/26/2022 9:23:05 AM   1 (0x0001)
Ready to uninstall: [Microsoft Corporation] - [Microsoft Teams (x64)]   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
Checking if MsiExec is available to perform an installation/uninstallation task   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
MsiExec is available.   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
Looking if application uninstallation process need to be aborted due to running process   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
No need to abort due to the running processes   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
Running application uninstall   PerfTimerLogger   4/26/2022 9:23:05 AM   1 (0x0001)
Warning: Unable to find the uninstall string for: Teams Machine%Wide Installer with version 1.5.0.9163   ScriptRunner   4/26/2022 9:23:05 AM   1 (0x0001)
Running application uninstall finished with Elapsed Time: 00 minutes 00 seconds 014 milliseconds   PerfTimerLogger   4/26/2022 9:23:05 AM   1 (0x0001)
End of Script Runner. Exit code is: 65535   ScriptRunner   4/26/2022 9:23:07 AM   1 (0x0001)

Navigation

[0] Message Index

Go to full version