Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Hi mitchelw,

thanks for your reply. Indeed I did not realize that there is a new version out despite checking the rss feed.

What doesn't make sense for me yet though is, as the catalog sync wasn't done yet, the 'old' update has not been marked as superseded / expired. So I would assume the update would install fine over the currently installed one (9.1.x).

Can someone please enlighten me about how the detection / applicable rule is working as I may see some issues with rolling out updates like that.
If I deploy an update of any kind of software it usually takes some time until every client has been online and installed the update.
So if the update gets superseded (or not applicable) without synchronizing my SUP I will have a deployment that runs into errors for every client that is not updated yet.

In my understanding an update was applicable until SUP is synchronized again and it will receive the updated metadata.

Thank you

Best regards
2
Hello FGN, you are seeing that error because there is a higher version patch for the product.  The updated version is 9.2 M3 release on Nov 5 2019. https://www.displaylink.com/downloads/windows
3
Report Update Install Issues Here / DisplayLink 9.2.2335.0 Update issue - not applicable
« Last post by fgn on November 13, 2019, 02:31:52 AM »
Hi,

i am not quite sure if this is really an issue of Patch My PC update package but I am unable to successfully install above update (DL-9.2M2).
After successfully publishing the update I try to install it on a test client via Software Center (as it is reported as I needed update). Unfortunately it is running into error 0x80240017(-2145124329) which translates to Update not applicable according to google.
I cannot see any messages in event log or in any CCM log that is relevant (to my knowledge).
Also I tested with some other clients (different models) with no success.

If I run the exe installer that is downloaded into my ccmcache folder manually I can successfully run the update with no further issue.

So my question is regarding the rules of the update package and where to find any further details about why it isn't running anything.

Thanks for your help.

Best regards
4
Hey Jim,

We don't actually set the download URL that reflects in ConfigMgr. That's based on what you entered when you created the software update point site system role.

It may be easiest to edit the host file on the proxy so hosting can resolve as a workaround.

UPDATE: Actually just chatted with the ConfigMgr PG. The download URL comes from the WSUS API and that is set to use the hostname. If you wanted support to do FQDN, it would actually be something that needs to go over to the ConfigMgr UserVoice portal.

Justin

Is there a way to configure PachMyPC to use the FQDN of the server instead of the short name when publishing patches? Also, what about requiring the use of SSL? I'd like to be able to try the FQDN of the server using https.

https://servername.domainname.com:8531

I'll add a vote to the uservoice.

Jim
5
Is there a way to configure PachMyPC to use the FQDN of the server instead of the short name when publishing patches? Also, what about requiring the use of SSL? I'd like to be able to try the FQDN of the server using https.

https://servername.domainname.com:8531

I'll add a vote to the uservoice.

Jim
6
Report Detection Issues Here / Re: Waterfox Classic 2019.10 / 56.3
« Last post by Admin - Omar on November 09, 2019, 05:35:48 AM »
Fixed, Thanks for reporting.
7
Report Detection Issues Here / Waterfox Classic 2019.10 / 56.3
« Last post by kofira2337 on November 09, 2019, 03:47:32 AM »
...is irregularly detected as outdated.

https://www.waterfox.net/releases/
8
Report Bugs Here / Crystaldiskmark updates but does not remove the older version
« Last post by Peace2000 on November 09, 2019, 03:46:47 AM »
Hi. Pmp updated Crystaldiskmark to the version of 7.0.0 but didn't remove the older version of 6.0.2. So I have now both versions installed.
9
General Questions / Re: Scheduled Task via Group Policy - Not sure if it's working
« Last post by Mahirasharma on November 08, 2019, 11:18:35 PM »
Great Information was very useful for me..
10
Your issue is that ADRs tries to use the proxy and your proxy cannot resolve your wsus content website. Please up-vote this user voice we created for SCCM
https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/38885431-add-option-to-bypass-proxy-for-local-address-for-a

The current work around for adr's to work is to allow your proxy to resolve and download content from the wsus server.
Nope. No updates fail when manually selecting and downloading in the console. They only fail when the ADR runs. The cab files are present on the WSUS server, and are available to download when the URL is pasted in a browser.

Jim
Pages: [1] 2 3 4 5 6 ... 10