• 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 - Atreus21

#1
Tenable is reporting high vulnerability for Zoom Client for Meetings from about 100 devices that all show the client installed at c:\users\username\appdata\roaming\zoom\bin\zoom.exe.  They are reporting versions from 4.6 up to 5.15.

We are currently publishing updates for Zoom Meetings (x64), Zoom Meetings (x86), and Zoom Outlook Plugin.

Is there anyway to attack this?



#3
Just starting using tightvnc for a VM in an hmi role.  PMPC picked it up but is getting the attached error.  Letting it sit usually fixes errors but after a week or so, no dice.
#4
Quote from: Adam Cook on April 27, 2021, 01:59:49 AM
Hello

Could you share WCM.log, wsyncmgr.log and WSUSCtrl.log please? You might prefer emailing these to [email protected] as they will contain hostnames or IP addresses.

Thanks
Adam

I've just emailed them to [email protected] sir.  Thank you very much.
#5
Hi folks,

I've got several product categories enabled for update publishing in the Publishing Service.  The Patch My PC product in the SCCM console is selected.  Yet nothing shows up in All Software Updates when I add Vendor = Patch My PC. 

Applications selected in the Publishing Service publish just fine and can be distributed and deployed.

PatchMyPc.log doesn't show anything in red, but wsyncmgr.log shows this:



I've been getting this error for awhile, and it hasn't stopped Microsoft products from publishing.  When I investigated it appears to be spurred by some errant Microsoft product selected for synchronization - I'm not sure it's causing or even related to the 3rd Party Update issue.

Would appreciate any opinions.
#7
I looked at the KB for this issue as well as followed the video but I'm confused.  I've never stood up a separate software update point as the video suggests as a possible cause.

The registry entry cites J:\WSUS, which is the SQLTempDB volume.  I've absolutely no idea how it got there.  It's also got nothing in it beyond two folders WsusContent and UpdateServicesPackages.   
The SQL query cites G:\WSUS, which I think is where it's supposed to be.  That's the Content Source volume, and it's definitely got lots of contents, clocking in at three quarters of a terabyte.
The IIS Basic Settings cite C:\Program Files\Update Services\WebServices\Root as the physical path.

When I run the wsusutil.exe to specify G:\WSUS, it tells me:

Content location is being moved. Please do not stop this program.
Content move failed. Please refer to the log file for more details.
Fatal Error: The new content file location is the same as the old location: G:\WSUS
Parameter name: newContentPath

Should I move it somewhere else?
#9
Hi folks,

This is a little confusing so please bear with me.

Microsoft Edge 87.0.664.57 and 87.0.664.66 (henceforth referred to as 57 and 66 respectively) are both members of a software update group we use for measuring compliance with the native "Compliance 1 - Overall Compliance" report.

Only 66 is actually deployed.

When we run Compliance 1 against the reporting SUG we get nearly 75% of the fleet evaluating as non-compliant.  Running the PMPC Report "04 - All Software Update Missing by Collection" we see that Edge version 57 is missing on many of them.



Furthermore, looking at the updates in the console, 57 shows 2,282 devices requiring it, whereas 66 only has 2 showing required.




Most of the fleet, servers especially, don't even have Edge installed.  The server referenced in the report in the first screenshot didn't have it installed.  Why are so many devices (1) reporting that 57 will satisfy them but 66 won't, and (2) why should machines without it installed need either one in the first place?

I could just remove 57 from the compliance SUG, but I'm concerned about why so many devices show it as required.

Would appreciate any opinions.
#11
I tried 03 - SUG Compliance - Dashboard and that one runs with about the same success as 01.

However, I don't think there's much in the way of indexing going on.  I've implemented Olga Hallengrin's solution here:  https://ola.hallengren.com/downloads.html, since you suggested looking into it.  I'm running the indexing job now and it's taking awhile, so I hope it's getting things straightened out.

I'll let you know how it goes sir.

Incidentally, we'll be activating our subscription soon.  I must confess the Application Publishing service, when used in conjunction with MDT's Application Mapping capability is....well it's going to spoil us rotten if we buy it.  Truly an astonishing product sir, thank you.
#12
Hi fellas,

Just got my 30 day trial of Enterprise and also wanted to use the Patch My PC Software Updates Dashboard.  But when I run it as it's configured out of the box, it runs until the SQL Reporting times out.  If I extend the timeout to never expire, it eventually throws an error after many hours of running.

If I cancel the report an target a smaller collection of about 100 devices or fewer, it will eventually resolve after about 10 minutes.  But I wanted to give my security guy the whole thing if possible.

I also suspect there may be something more fundamental afoot, as the native SCCM Software Updates Dashboard in Monitoring freezes the console for a good 5 minutes when you run it, but eventually resolves.  I thought the two issues may be related.

Is there any kind of indexing I may be missing?  The reporting server is on the primary site server - would it beneficial to separate them?  The server's provisioned with 32GB of RAM and is on our highest performing disks - task manager doesn't generally show the server's resources being exhausted.

Would appreciate any advice.  Thanks.