Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Andrew Jimenez

Pages: 1 2 3 4 5 [6] 7 8 9
76
So we currently populate this flag for HKLM, but we cannot populate HKCU at this time. In order to set that flag for HKCU, you'll likely need to use a GPO or some other method to set: HKCU:\SOFTWARE\Zoom\OutlookPlugin\autoUpdate:dword:0

I assume if it is set at the HKLM level, that setting will actually be set for new users, but not for existing users.

77
ohh it has to be done per user... That is... not good. I'll see if we can support that scenario.

78
Can you link me to that reddit thread? We'll look at adding this as well.

79
Create either of the following Reg key values:
HKLM\SOFTWARE\Citrix\ICA Client\AutoUpdate\Commandline Policy\LTSROnly = true
HKLM\SOFTWARE\Policies\Citrix\ICA Client\AutoUpdate\LTSROnly = true

80
The issue there is that if you have both Workspace and Workspace LTSR published, since there is nothing else differentiating them, both would be applicable.

We did however add in the install string to set the LTSROnly flag, so if you deploy Workspace LTSR via our App method, future patches from Patch My PC will be LTSR.

81
So during our testing for Workspace LTSR, we found that if you install the application and do not define LTSROnly to equal true, then during an auto-update, the app will actually revert itself to non-ltsr. Additionally, there is no other indication for the LTSR app that the application is actually an LTSR release. Because of this, we chose to use the LTSROnly reg value to determine if the Citrix Workspace install is actually an LTSR installation. If you know of any other methods of determining if the app is in fact LTSR, we'd be happy to test that.

We are not superseding Citrix Receiver LTSR at this time because Receiver LTSR is still supported, once Receiver LTSR falls out of support, we will likely supersede it with the latest Workspace LTSR.

82
Thanks! This actually helped us identify a bug! Should be fixed in the next release!

83
Interesting, let's move this to a support case, I think I'm going to need logs here.

Please open a case at: https://patchmypc.com/technical-support

If you could zip and attach the logs specified here, that would help a ton: https://patchmypc.com/collecting-log-files-for-patch-my-pc-support#publishing-service-app-logs
Thanks!

84
Do you happen to have the delay option set in the Publisher under ConfigMgr Apps -> Options?

85
Hello,

What version of Patch My PC are you using? You can find this in the "About" tab of the Patch My PC Publisher. This was a known issue in a previous release but has been fixed for some time, so I want to rule that bug out. Thanks!

86
We've added the ability to disable the self updater to the Zoom Outlook Plugin. You may need to go into Patch My PC and confirm the option is now available and enabled.

87
For sure, if we continue to see issues like this, we'll add the recommendation to our considerations page here: https://patchmypc.com/considerations-third-party-products

88
I actually checked this out for someone else a week or 2 ago. This seems to be an ongoing issue with the Visual Studio Code installer, and an issue outside of Patch My PC. I would definitely turn on the auto-close or skip install if code is running for the time being. Please see the following bug reports for VSCode:
https://github.com/microsoft/vscode/issues/71937
https://github.com/microsoft/vscode/issues/47841
https://github.com/microsoft/vscode/issues/47968

89
I see the issue here. We look specifically for "Teamviewer Host" and it looks like Teamviewer 13 pops in "Teamviewer 13 Host" instead, I'll look at fixing up the applicability rules to ensure we don't push out Full over Host in this situation. (we do specifically check the wow6432node).

90
What is the exact version of Teamviewer 13 that was being pushed out? We have a check in place for teamviewer host, but I'm wondering if something is different here. This is the applicability rule for Teamviewer 13.2.36220 in our catalog:

Code: [Select]
      <sdp:IsInstallable>
        <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="13.2.36220.0" Value="DisplayVersion" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" RegType32="true" />
          <bar:RegSzToVersion Comparison="GreaterThanOrEqualTo" Data="13.0.0.0" Value="DisplayVersion" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" RegType32="true" />
        </lar:And>
      </sdp:IsInstallable>

So we search for the Teamviewer uninstall reg key, and ensure that the display name i s not "Teamviewer Host". Can you let me know what you see under that reg key? Thanks!

Pages: 1 2 3 4 5 [6] 7 8 9