TeamViewer 15.8.3 - Applicability Rule missing WOW6432Node

[fgn]

Hi,

I just tried to debug why the Update wouldn't showed up and checked the Applicability Rule:

Code: [Select]

<lar:And>
  <bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" Type="REG_SZ" RegType32="true" />
  <lar:Not>
    <bar:RegSz Comparison="EqualTo" Data="Teamviewer Host" Value="DisplayName" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" RegType32="true" />
  </lar:Not>
  <bar:RegSzToVersion Comparison="LessThan" Data="15.8.3.0" Value="DisplayVersion" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" RegType32="true" />
  <bar:RegSzToVersion Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" Value="DisplayVersion" Comparison="GreaterThanOrEqualTo" Data="15.0.0.0" Key="HKEY_LOCAL_MACHINE" RegType32="true" />
</lar:And>
It seems that it was missing from the two prior versions as well.
Has there been any major change that I've missed or is that just an issue on your side?

Thanks!

[Cody Mathis]

Hello,

Please not the last part of the applicability rule RegType32="true"

This component ensure we search the Wow6432Node.

Usually, Wo6432Node will not be explicitly written out, instead thise is used to ensure proper redirection of registry searches for a 32 bit application ona 64 bit operating system, and also ensure it is handled appropriately on a 32 bit operating system as well.

[fgn]

Hi Cody,

thanks for the explanation, I didn't know that. I just compared the most recent ones to the older ones we automatically installed and in those rules, Wow6432Node was always written out.
Gotta have to find another reason why it is reported as not required.

Thanks you anyways!

Best regards
Fabian

[Cody Mathis]

Let us know if you can't get it figured out!

[fgn]

Hi Cody,

actually I am not able to figure it out and have now spent way too much time on it.

I am testing the update on two devices. Both have TeamViewer 15 installed but are having different minor versions. On one of the devices I have tried multiple minor versions to see if it makes any change. It doesn't.
So right now I am stuck with an installed version (15.6.7) but the reports (e.q. Compliance are reporting the update as "not required" and therefore wouldn't show up. I quadruple checked the applicability rules / registry.
There's a Key (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{36A33BB9-E44B-45EA-A4FD-E861A103FF97}) with DisplayName set to "TeamViewer" and DisplayVersion to "15.6.7.0".

Both clients just work / report fine to any SCCM component, no obvious issue present in log files related to software updates.
As I have tested my application deployment of the new version on both of those clients before the testing of the update it may have corrupted something.
Therefore I went and tried another client which had an even older version installed (15.1.3937.0). The update was available to install yet the registry key never changed to anything newer than 15.1.3937.0. However the local TeamViewer.exe showed 15.8.3 in the files' details tab. Checking the client with the "Client Center for Configuration Manager" (3rd Party Tool by Rob Zander) there is no TeamViewer 15.8.3 Update marked as applicable or installed. But there's an update for TeamViewer 12(!) marked as installed.

At the moment I think there is something really weird happening on our side and it has nothing to do with your published updates.

My last idea until I'll just deploy the latest version as an application:
We are using the msi installer with options for management assignments (API token etc.) - are there any known problems with patching the MSI versions with the updates provided by you? I would have thought it was working, but obviously things are bit different.

Best regards
Fabian

[Cody Mathis]

It might be easiest to do a support session

Can you use this link https://calendly.com/cody-123/30min to schedule a support session and we will see what we can get figured out?

[fgn]

Just wanted to post a follow up as I have found the issue.

The issue is related to the different installations (.exe and .msi).
As we are using .msi installer to customize our installation the provided update is not applicable as they are using different registry keys.

MSI installer for example "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{36A33BB9-E44B-45EA-A4FD-E861A103FF97}"
and for .exe
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer"

Unfortunately there's no chance we can use the .exe installer as customization on install is needed.

Thank you Cody for your offer to schedule a support session, but I guess there's nothing to support right now so we can cancel it. Not quite sure how to cancel as I haven't received any inviation or anything else after I scheduled a call via the link.

For now we probably need to wait until you support the update for msi installers as well.

Regarding the different installation states on other clients. Seems that those guys have just manually installed an exe-version and the update applied correctly.

[Cody Mathis]

Hello,

Glad you were able to determine the root cause. I didn't see a Calendly event come through that I know of, so I don't think there is anything to cancel.