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 - David P

Pages: [1]
SnapGene viewer downloads viewer_download.php file instead of the .exe installer.
Attached is screenshot of the package details where it lists the wrong file name.
Maybe the download link or method needed to get the installer changed.

Tableau Reader 20.1.527 detecting as installed when version 19 is installed.

from PatchMyPC-SoftwareDetectionScript.log:
*** Starting detection for Tableau Reader*  with version 20.1.527
Detection script version 1.5
Running as xxx [Administrator] on ITS-xxx-VM2
Found Tableau Reader 2019.4 (20194.19.1010.1202) version 19.4.190 installed on
Found Tableau Reader 2019.4 (20194.19.1010.1202) version 19.4.190 installed on 20191117
*** Starting detection for Tableau Reader*  with version 20.1.527
Detection script version 1.5
Running as xxx [Administrator] on ITS-xxx-VM2
Found Tableau Reader 2019.4 (20194.19.1010.1202) version 19.4.190 installed on
Found Tableau Reader 2019.4 (20194.19.1010.1202) version 19.4.190 installed on 20191117

Detection method has: $AppVersionToSearch = '20.1.527' so that is correct.

Ok. I just wanted to make sure it was on your radar and also make sure I wasn't doing something wrong  ;)

I noticed Jaws was missing from the drop down selection in the report "05 - Installed 3rd Party Application Reports". I figured that I probably needed to update the report, so i looked in C:\Program Files\Patch My PC\Patch My PC Publishing Service\SSRSReports\Reports but the report is date modified 8/18/2018 which was pre Jaws support in PatchMyPC.
Should the files in the folder auto update when PatchMyPC does? Am I missing something? Or does your team need to update them with the newly supported applications?
Edge is also missing from the report.


Detection Script has:
$AppToSearch = 'TeamViewer 15*'
$AppVersionToSearch = '15.1.3937'

But the name of the application is just 'TeamViewer' now instead of "TeamViewer 15" so it fails on the match.

Thanks! I didn't want to delete it because its attached to multiple task sequences. I manually changed the detection method to look for x64, if that doesnt work ill delete it and reattach it.

Hi yes, that is our problem.
I saw their was another thread about duplicate entries but I didn't read it until now.
"We did this in one of our labs and things worked fine with the exception of the duplicate Patch My PC vendor. We've just been using both vendors and that's the easier workaround. We've just made sure that ADRs and searches include both vendor names."

Is the resolution still to just enable both vendors for now then?

We have 2 ConfigMgr servers, a site server(A), and a MP/DP/SUP(B) with PatchMyPC installed.
Yesterday we updated both server OS's from 2012R2 to 2019. Before doing so on the B server, we removed the WSUS role, then after upgrading reinstalled WSUS and reattached the database (which is on A). All as outlined here:

The issue we are having is that PatchMyPC updates are not syncing, application builds are working.

I can see in the wsyncmgr.log that Microsoft updates are syncing, I see 4 that synced this morning, and they are listed in the Console. There are no errors or any notifications about the updates from PatchMyPC.

The PatchMyPC.log says everything is fine and its publishing updates. "A total of 10 updates were published, 0 update was revised, 0 update was expired, 0 application was published into SCCM, 0 SCCM package was updated, 0 package was revised in SCCM, 0 application was auto-enabled and 0 update was auto-enabled"
They just dont show in the Software Updates in the ConfigMgr console.

What I'm looking for is advice, should I just run the PatchMyPC installer again, maybe some components went missing during the upgrade? Or is there something else I should check.

The application build of Tableau Reader 19.3.510 is detecting that 19.3.510 is installed when 19.2.149 is installed.

PatchMyPC-SoftwareDetectionScript.log shows:
*** Starting detection for Tableau Reader*  with version 19.3.510
Found Tableau Reader 2019.2 (20192.19.0515.1630) version 19.2.149 installed on 20190605

AppDiscovery.log shows:
+++ Detected app deployment type Tableau Reader 19.3.510 (x64)(ScopeId_0575162B-4A47-4F76-9601-CC33EA4057C5/DeploymentType_4dfe3e48-ca24-4a29-9db6-ab8ac18ebbdd, revision 1) for system.

I see in the logs back on 7/19 the app failed to publish which was probably the detection method change. Just says SCCM: Generic Failure.
Works now though. Thanks!

$AppVersionToSearch = '' in detection script, but the DisplayVersion in registry is

Active Setup is an undocumented unsupported feature of Windows. You add keys to HKLM\Software\Microsoft\Active Setup\Installed Components, one of the keys is a command to run the first time a user logs in, which is usually to merge a .reg file to put keys into the current user registry hive.
Compliance settings may not run in time, as the settings need to be in place before the application is opened by a new user, which could be before the compliance setting evaluates.
Regardless, I solved my problem, I used a post powershell script that creates a .reg file and adds the keys to HKLM to have it merge the .reg file on first time profile setup.
I had a minor setback because I was using the preview build and building applications, and the publishing service updated which reverted the tab back to packages and I didn't notice  :)

We just started using PatchMyPC here, and I have been recreating our SCCM applications in the product. Our old install script for WinSCP we use Active Setup to set keys in HKCU registry on logon to disable the self update message. Within PatchMyPC I am unable to select "Disable self-updater" for WinSCP. The option does show on "Martin Prikryl" but nothing happens when you select it. So I assume that the self updater cannot be disabled this way.
Has anyone handled Active Setup within PatchMyPC?
Besides adding a script that runs post installation, is it possible to also add a .reg file to the install location or some other location? It doesnt seem like the ability to just copy a file is in the interface, I suppose you could manually put the file in the application folder and redistribute, but I dont know if that would also work for Updates as well as Base installs. And doing something manually every build defeats the purpose.

I can think of other ways to do this:
1) run a post install script that adds the reg keys to HKLM\Software\Microsoft\Active Setup\Installed Components and then creates a .reg file with HKCU settings to import (might be the best option?)
2) add the reg keys in HKCU with GPO (simple but hard to target only computers with WinSCP installed)
3) add the reg keys in HKLM\Software\Microsoft\Active Setup\Installed Components with the post install script and point it to a reg file to be imported that is locally copied via GPO or Configuration Item (overly complicated)
I would love to have the entire install all in one place so option 1 might be the best bet and may be what people with this problem are doing?

Pages: [1]