• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 
Menu

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.

Show posts Menu

Messages - quackpatch

#3
Hi Justin,

I was hoping to copy out local config prior to our Java8 upgrade however I've noticed the Pre-Update script is also Post-Uninstall - this removes the files before I have the chance to dump them out:


Running script: PatchMyPC-Remove-JRE8-32bit-Only.ps1 ScriptRunner 27/06/2019 11:49:43 AM 1 (0x0001)
Running Powershell Script. ScriptRunner 27/06/2019 11:49:43 AM 1 (0x0001)
Exiting With code: 0 ScriptRunner 27/06/2019 11:49:58 AM 1 (0x0001)
Running script: Pre-Update.ps1 ScriptRunner 27/06/2019 11:49:58 AM 1 (0x0001)


This was my workaround in lieu of not having the ability to incorporate additional source files into the update as per this post: https://patchmypc.com/forum/index.php?topic=3034.msg8073#msg8073. I'm wondering if you have any suggestions on how to best approach this, or would I need to raise a feature request to add Pre-Uninstall / Post-Uninstall actions?

Thanks!
#4
Perfect that did the trick. It's a minor use case but I guess the expected behavior as per the "Supersede Previously Published Update" dialog was to supersede the previous update irrespective. Thanks for your help!
#5
Happy to side-line this. We'll instead be using a gpo and pre/post scripts. The drawback of gpo being immediately post install it leaves the application unmanaged, at least until next gpo refresh which could be 90mins by default; not ideal when it concerns security. To combat that we'll trigger the Pre-Update script to copy the required local files to a temporary location and copy them back in Post-Update.
#6
I fat-fingered an update script and had to republish content for the second time in one day. The first time worked flawlessly, appending the date onto the update name eg "Oracle Java 8 Update 211 8.0.2010.9 (x64) - (June 25, 2019)" and automatically superseding the previous update. However the second republish used the exact same name and did not supersede the previous one. What would you recommend at this stage?
#7
Both. A way to make external files available to the application and then use the script to process them.
#8
Hi there,

We've started to deploy Java 8 updates in our environment and run into a pickle with custom files....

Our initial deployment includes copying config files into "C:\Windows\sun\Java\Deployment" eg deployment.config, exception.sites etc. however these are ripped out during the upgrade. Unless I'm missing something, I was thinking a "Copy custom source files..." option could exist within pre/post scripts which can be referenced by the scripts. I see there is an option to "Add MST transformation file" available to some applications, not for Java 8 unfortunately given its not an MSI installer.

We've obviously other tools at our disposal to do this, CI's, gpos etc but was hoping for a one-stop-shop solution.

Thanks!
#9
Hi there,

During our security audits we've found vulnerabilities in stunnel: https://www.stunnel.org/vulns.html

The application appears to be a free download: https://www.stunnel.org/downloads.html

We've discovered this installed on around 10 devices. Be great if this could be incorporated into the catalog.

Rgs,
S.
#11
We have a bunch of old Citrix servers running Server 2008R2x64 that have WinZip 17.0 installed along with the Winzip Command but these are not being detected to upgrade to the latest release. Other updates, Chrome, Flash Player are coming through fine...

C:\Program Files\WinZip\WINZIP64.EXE (File ver: 28.0.10381.0, Product ver: 17.0 (10381)

* screeners attached
#12
No problem, will do.

In the meantime, another troubleshooting step I tried was to use the SCCM Content menu to publish the content, but that failed as per SMS_ISVUPDATES_SYNCAGENT.log below:

[34, PID:8812][02/06/2019 16:26:21] :PollingWorkMonitor: There are 1 jobs that are pending in the jobs table. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[34, PID:8812][02/06/2019 16:26:21] :PollingWorkMonitor: Starting job 72057594037927937 for subject c8d329d4-141d-47c4-9fb7-0d2855317ed4. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[34, PID:8812][02/06/2019 16:26:21] :Creating a new SyncUpdate work item for update c8d329d4-141d-47c4-9fb7-0d2855317ed4, jobid is 72057594037927937 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[34, PID:8812][02/06/2019 16:26:21] :Launcher : About to start work item: SyncUpdate. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:21] :SyncUpdate: c8d329d4-141d-47c4-9fb7-0d2855317ed4 - No synchronization record for update with id c8d329d4-141d-47c4-9fb7-0d2855317ed4 was found, only updates synchronized by Configuration Manager can have update content published to WSUS by Configuration Manager. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:21] :STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_UPDATECONTENT_NO_METADATA). 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:22] :STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_UPDATECONTENT_FAIL). 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:22] :Launcher : Work item SyncUpdate has completed queued time was 00:00:00.1670159 run time was 00:00:00.1869994 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
[27, PID:8812][02/06/2019 16:26:22] :SyncUpdate: c8d329d4-141d-47c4-9fb7-0d2855317ed4 - Completed. 1/01/1601 12:00:00 AM 2000310283 (0x773A500B)
#13
Yes, that was the first step which I noticed after changing then running a sync did not reflect in SCCM; hence all the deleting\re-syncs.
#14
I'm trying to switch a few updates from "metadata only" to "full content" after they've already been published.  Apologies in advance, I'm sure I've seen this posted somewhere but for the life of me cannot find any information on it  :o

I appreciate I could wait for the next release of the update(s) but who knows when that could be. I've tried the following method and had mixed results:

- deleted the update using the Modify Published Updates Wizard (Advanced tab)
- run a full SCCM Software Updates sync, once complete, confirm update(s) expired
- start a sync from PatchMyPC Publisher # this will trigger sccm software updates sync
- once complete, confirm update(s) published with full content

I'm obviously missing something as the updates return as metadata only  :(
#15
Thanks Justin. I can confirm we've auto-upgraded - very helpful changes.