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 - mkmaster78

Pages: 1 [2] 3
16
When you guys consolidated all the updates to be under one Publisher and one Product, it left a whole bunch of products and publishers in WSUS.  Is there anyway to remove these products and publishers from WSUS's catalog completely, just for cleanliness sake?



17
Thanks for updating the catalog.

18
Thanks for updating the catalog.

19
Ok, thanks for looking into it.

20
It would be nice if this could be included in the catalog.  I don't know if license restrictions would impede this, however.

21
GoToMeeting 8.33.0 is being detected as required on all machines, regardless of whether a lower version is installed or not.

22
The FileZilla Client 3.36.0 (x64) and FileZilla Client 3.36.0 (x86) fail to publish in SCUP due to file download hash issues. SCUP Logs below:

Code: [Select]
Retrieving content for update 'FileZilla Client 3.36.0 (x64) (UpdateId:'874bca15-6b01-4e20-bd29-9f63fc211386' Vendor:'Patch My PC' Product:'SCUP Updates')'. NormalPublishItem 8/29/2018 9:57:54 AM 7916 (0x1EEC)
--- Content will be saved to C:\Users\SCUP\AppData\Local\Temp\rwzz51ve.zm2\FileZilla_3.36.0_win64-setup.exe. NormalPublishItem 8/29/2018 9:57:54 AM 7916 (0x1EEC)
WebClient reporting progress for download of file https://dl3.cdn.filezilla-project.org/client/FileZilla_3.36.0_win64-setup.exe 8017 / -1 0% WebClientWrapper 8/29/2018 9:57:55 AM 7312 (0x1C90)
Download Content: file was downloaded successfully. NormalPublishItem 8/29/2018 9:57:55 AM 7916 (0x1EEC)
Successfully retrieved content for software update 'FileZilla Client 3.36.0 (x64) (UpdateId:'874bca15-6b01-4e20-bd29-9f63fc211386' Vendor:'Patch My PC' Product:'SCUP Updates')' to local file: C:\Users\SCUP\AppData\Local\Temp\rwzz51ve.zm2\FileZilla_3.36.0_win64-setup.exe NormalPublishItem 8/29/2018 9:57:55 AM 7916 (0x1EEC)
--- Digest verification failed on content for software update 'FileZilla Client 3.36.0 (x64) (UpdateId:'874bca15-6b01-4e20-bd29-9f63fc211386' Vendor:'Patch My PC' Product:'SCUP Updates')'. NormalPublishItem 8/29/2018 9:57:55 AM 7916 (0x1EEC)
--- Publish of software update 'FileZilla Client 3.36.0 (x64) (UpdateId:'874bca15-6b01-4e20-bd29-9f63fc211386' Vendor:'Patch My PC' Product:'SCUP Updates')' has FAILED. NormalPublishItem 8/29/2018 9:57:55 AM 7916 (0x1EEC)
Refreshing updates view... UpdatesViewModel 8/29/2018 9:57:55 AM 7376 (0x1CD0)
Refreshing updates view completed. UpdatesViewModel 8/29/2018 9:57:56 AM 7376 (0x1CD0)


23
Thank you, can't wait to test it out.

24
If possible, could you please add the .NET Core and Hosting Runtime Bundle along with your other .NET Core offerings?
Download can be found on this page: https://www.microsoft.com/net/download/dotnet-core/2.1

Thanks for your time.

25
Archived Feature and Product Request / Re: .NET Core and Powershell Core
« on: August 27, 2018, 09:06:13 AM »
Thanks for the work on that, much appreciated :).  Should I put a separate request in to get the runtime & hosting bundle added into the catalog?

26
Archived Feature and Product Request / Re: .NET Core and Powershell Core
« on: August 01, 2018, 10:16:53 AM »
Any word?  Or should I put in a separate software request for this?

27
It looks like the detections and installs are working better this time around.  Thank you for your efforts.  One last thing, it does not appear that you've included the hosting bundle in the runtime updates.  Would that be something you would consider adding (making sure to distinguish between standard runtime and runtime/hosting bundle)?  It would clear up some CVEs on my end.
https://www.microsoft.com/net/download/dotnet-core/2.1


Thanks again for all the effort you've put into this, it has certainly helped.

28
Well, after the recent updated version added to the catalog, it looks like the x86 versions are detecting now.  I'll have to wait until patching cycle rolls around before finding out how the deployment goes.

29
Many versions - 1.0.1, 1.0.4, 1.1.0, 1.1.1, 1.1.2, 2.0.5
Also, I have machines with x86 installed, and the appear to have the desired reg key (as listed in the Installable portion of the update in the catalog) but they don't detect it (and these machines detect and install other updates in your catalog just fine, so I know it isn't a general failure to accept 3rd party updates).  I can't find a root cause for it though.

30
Thanks for the info and quick response!

Pages: 1 [2] 3