Microsoft Patch Tuesday - August 2024

[Esben_D]

The August 2024 edition of Patch Tuesday brings us 86 new fixes, with 7 rated as critical and 6 exploited. Additionally, I've also used the the new format of report as was discussed on the forum here: https://community.lansweeper.com/t5/reports-analytics/patch-tuesday-improvement/m-p/75608

You can find all the info and report in the August blog post.

[Esben_D]

@GWVS Could you double check you used the latest version of the report that is now live on the website?

[Mister_Nobody]

@vinnes 

You have to check Compatibility level of LS DB!

[GWVS]

@Esben_D doublechecked, it's the current version.
I can run the report as sql query on the sql server directly. So error message only displayed on the lansweeper sql editor.
Lansweeper on prem version v. 11.4.0.4

Maybe it's because of this row, it's the only row with a NULL value 

[RickZler]

I have an issue with the Patch Tuesday report for the August 13th 2024 Microsoft update cycle. The report is returning a null value and I know that the P.C. I'm running it on needs to have this update installed. No assets are being returned even those that have had the updates installed and have been restarted several times now. The assets were all also rescanned to make sure the Asset pool was up to date. Please let me know what my next step should be as I know that many of my assets still need to have this installed. Lansweeper v. 10.2.4.0

[Drivenpowder1]

@Esben_D 

Hey thanks for the report, this is the first time I'm seeing this error:

Error: Report not allowed. You need permission to view uptime information.

My account has full administrator access and should be able to see this report, all other reports don't have this issue and previous Patch Tuesday reports also worked. Can you advised me on what to do next?

[Esben_D]

@GWVS I updated the report to add another condition which might fix it. However, if the report works in SSMS but not in Lansweeper, it might be related to your Lansweeper version.

So if the issue persists, I'd recommend checking for an update or contacting support.

[Esben_D]

@RickZler 

I think its best you contact support and provide them with screenshots of your issues since your description seems to indicate a scanning issue rather than a report issue. Do note that the report mostly relies of the Windows build number of assets rather than patch numbers, specific patch information is purely informational now.

[Esben_D]

@Drivenpowder1 this post might help. Alternatively, you'll have to contact support.

https://community.lansweeper.com/t5/reports-analytics/error-report-not-allowed/td-p/35533

[RickZler]

@Esben_D 

All other reports run correctly and post to output report with the specific colors to indicate that the other queries are indeed running correctly and showing the details of the query correctly on the output report.  Just having an issue with this particular report. Can I update the software on my Lansweeper server without having to re-install the LSAgent on all my client machines ?  Here is a snapshot of my work computer waiting to have the updates installed.

[GWVS]

@Esben_D Thank you very much, the most recent version works.

[Drivenpowder1]

@Esben_D 

That post worked wonderfully, just had to add the Domain Admins group to Administrator role and this fixed it. Thanks for the great direction!

[Esben_D]

@RickZler LsAgent and Lansweeper always have different versions, they are not related so its fine to update them separately.

Regarding the report, I'm not sure I really understand what the issue is. But you mentioned that assets might be missing from the report. Without details of the assets that are missing I am unable to troubleshoot them. That's why I suggest contacting support so you can provide them the details so you don't have to post any sensitive information publicly.

[grimsheeper]

Hi, i too had issues with this report at first but seems to run OK now.

TBH i preferred the old version. I had modified the columns and each month i only copied and pasted a small section of the latest report so that it just updated the KBs and version checks etc.

Now this new version defunks all my work and i have to amend it again..... urgh.

OK so..... i get that its progress. But why remove the "install this patch" column? is that purely because it would/could change throughout then month as they get superseded?

For me - that was the column that i used to manually download each given KB to my WSUS server. Now i have all these machines showing "out of date" and i dont know exactly what KB they MEANT to have, all i can see is what they currently have.

[Esben_D]

@grimsheeper 

The main reason to remove the KB patch suggestions was partially to make it more efficient for me to actually create this every month. Partially because, as you mentioned, it wouldn't be super accurate or the best advice for someone looking at the report a month later (or a week if Microsoft has to fix something they break).

I think you're the second person to mention it. If there is enough demand I don't have issues adding it back next month.

[grimsheeper]

I dont know if you use WSUS - but they email you a list of what your WSUS Server has just downloaded ready for you to approve. They list each update with about 5 variations for each, and trying to work out which one the PC is expecting is not fun.

Also, as i customise the columns, ie i remove plenty i dont need to see to simplify it, i also rename columns, and add things in like "uptime" and filtering columns by "Workstation" so that i can have one version for servers and one for workstations is a massive plus for us here. I dish out work to people depending on their skill level so we try to seperate them.

So - that being said, i understand that i am going against the grain with these changes and you cant be expected to facilitate everyone, but each month i only ever used to copy and paste small sections of the code (that pointed to which KB was required etc). Im hoping that next month i will be able to do the same with this...