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 ... 9
1
You can definitely add in a try catch, the biggest thing is to ensure is that it returns a 0 if it is successful, or the entire installation might return as failed.

2
I would use a post install script. You can easily turn a registry file into a PowerShell script using this awesome tool: https://reg2ps.azurewebsites.net/

3
We'll have this in the catalog later this week (Week of 15/11/2021).

4
You are correct, just make sure to set that Assignment on "All Products" first, as it will wipe all assignments below it, and replace them with the assignments made at the "All Products" level.

5
Hello,

So setting an assignment on "All products" will overwrite assignment settings below. If you want to set a default assignment for everything, then adjust settings for specific applications/updates, you would want to set the default assignment first, then go and make customizations on specific applications afterwards.

6
You should not need the console for that specific task, and the feature is in production.

7
Confirmed. I'll update the website shortly with this information. I have also added the appropriate processes to the application so that you can use our "Manage Conflicting Processes" feature to close the app prior to update. https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications

8
Hi Aleksander,

I believe this application needs to be closed before installation will complete successfully. I am still testing this and will confirm and add it to our known issues page once I confirm the issue. https://patchmypc.com/known-issues-and-considerations-when-using-patch-my-pc#topic2

9
Hi Aleksander,

Sorry for the delay on this! I'm not sure how we missed it, but we are looking into it now.

10
The SCUP schema is the same as is used in ConfigMgr. The creator of WSUS Package Publisher actually works for us :) I'll have him check this out.

11
Interesting. What is the full title of that update?

12
Hello,

I believe our Non-LTSR updates (starting with 21.7.0.44) Are already doing what you are suggesting:

Code: [Select]
<lar:And>
<bar:RegValueExists Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\CitrixOnlinePluginPackWeb" Key="HKEY_LOCAL_MACHINE" Value="DisplayVersion" RegType32="true" />
<bar:RegSz Comparison="Contains" Data="Workspace" Value="DisplayName" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\CitrixOnlinePluginPackWeb" RegType32="true" />
<bar:RegSzToVersion Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\CitrixOnlinePluginPackWeb" Value="DisplayVersion" Comparison="LessThan" Data="21.7.0.44" Key="HKEY_LOCAL_MACHINE" RegType32="true" />
<bar:WindowsVersion Comparison="GreaterThan" MajorVersion="6" MinorVersion="1" ProductType="1" />
<lar:Not>
<lar:Or>
<lar:And>
<bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Citrix\ICA Client\AutoUpdate\Commandline Policy" Value="LTSROnly" RegType32="true" />
<bar:RegSz Comparison="EqualTo" Data="true" Value="LTSROnly" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Citrix\ICA Client\AutoUpdate\Commandline Policy" RegType32="true" />
</lar:And>
<lar:And>
<bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Policies\Citrix\ICA Client\AutoUpdate" Value="LTSROnly" RegType32="true" />
<bar:RegSz Comparison="EqualTo" Data="true" Value="LTSROnly" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Policies\Citrix\ICA Client\AutoUpdate" RegType32="true" />
</lar:And>
</lar:Or>
</lar:Not>
</lar:And>

Currently, for NON-LTSR to be applicable the following conditions must be met:
Registry key "CitrixOnlinePluginPackWeb\DisplayVersion" exists and is less than 21.7.0.44
Registry key "CitrixOnlinePluginPackWeb\DisplayName" exists and contains "Workspace"
Windows Version > 6.1
NOT
(OR
   (Registry key Commandline Policy\LTSROnly exists AND = true)
   (Registry key AutoUpdate\LTSROnly exists and  =true)
)

I went ahead and made truth table for the second part to make sure the logic was sound.
X = ! ( ( a && b ) || ( c && d ) )
Cmdln exists (a)Cmdln eq True (b)AutoUpdate exists (c)AutoUpdate eq true (d)Applicable (X)
00001
00101
00110
10001
10101
10110
11000
11100
11110

Looking at this, the only times the NON-LTSR update would be applicable are:
  • no registry keys are set
  • AutoUpdate\LTSROnly exists and is set to false
  • CommandLine Policy\LTSROnly exists and is set to false
  • CommandLine Policy\LTSROnly and AutoUpdate\LTSROnly both exists and both are set to false

Otherwise, the LTSR version is applicable (either the install flag was set or the GPO is set).

From what I understand from your explanation, I believe this is the behavior you are looking to have for this application. Please let me know if I am misunderstanding.

13
Hi Jared,

I do wonder if this is an issue with the VSCode installer itself. There is a long-standing issue on the github that sounds exactly like this problem: https://github.com/microsoft/vscode/issues/47841

14
A fix just rolled out in today's catalog update, we had to fall back to a file version detection if the registry version detection does not work. This seems to have been a problem since they switched over to the MSI based installer. We modified the existing updateid, so you will want to republish https://patchmypc.com/when-and-how-to-republish-third-party-updates the Nextcloud update to make this change active, otherwise all future releases should be fixed as well.

15
We were able to replicate this and will work to resolve this week.

Pages: [1] 2 3 4 5 6 ... 9