Wua - Various questions

Share your tips or issues concerning the WAPT Console or WAPT Agent here
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Answer
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

November 20, 2024 - 7:54 AM

Wapt version: 2.5.5.15697 - Enterprise Edition
Server OS: Debian 12
Target operating systems: Windows 10
Os Machine administration: Win server 2022

Good morning,

We recently implemented WAPT with the WUA function, however there are a few points we cannot explain:
1- Update notifications appear. The oldest PC in our fleet dates from 2019, but we are seeing updates dating back to 2017 that are long outdated
wua_date_maj.PNG
wua_date_maj.PNG (233.82 KB) Viewed 3541 times
Is this normal?

2- Regarding these updates, we created a package, type wsus, but my colleague and I do not have the same view of the updates when we edit it.
  • Her: She only sees the allowed updates.
    Me: I see both the allowed updates and those that aren't yet allowed.
3- We initially planned to implement a wsus-type package for workstations and another for servers, but given the not very user-friendly interface, we're wondering if this is really the right approach. How do you handle this?

THANKS
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

November 20, 2024 - 12:26

clafon wrote: ↑Nov 20, 2024 - 07:54 1- Update notifications are appearing. The oldest PC in our fleet dates from 2019, but we are seeing updates dating from 2017 that are long outdated.


Is this normal?
If they were detected by Windows Update, they're still relevant. You can click on "View clients" by clicking on the CAB file to see the relevant post. These appear to be CAB files related to Office 2007, so I'm not surprised
clafon wrote: ↑Nov 20, 2024 - 07:54 2- Regarding these updates, we created a package, type wsus, but my colleague and I do not have the same view of the updates when we edit it.
  • Her: She only sees the allowed updates.
    Me: I see both the allowed updates and those that aren't yet allowed.
In version 2.5, there was a minor refresh bug; you absolutely had to go through the Windows Update tab and click "Refresh" to get a proper view. This bug has been fixed since version 2.6
clafon wrote: ↑Nov 20, 2024 - 07:54 3- We initially planned to implement a wsus-type package for the workstations and another for the servers, but given the not very user-friendly interface, we're wondering if this is really the right approach. How do you proceed?
It all depends on how you operate. But I didn't understand your problem with the visualization
High
clafon
Messages: 109
Registration: Nov 06, 2024 - 10:56

November 21, 2024 - 5:04 PM

Thank you for your feedback and explanations.
Regarding the update visualization, we don't find it intuitive (or perhaps we're doing it wrong, which is quite possible) to know which updates are intended for which machines (except for OS updates). Basically, how do we know if a .NET 8.0 update should be applied to a server or a machine? When editing the "Wua" package to "Allow" updates, there seems to be a missing field for "affected machines"—that's just our opinion.
Or perhaps we need to change our workflow: allow everything and let the machines choose what to apply. It's a real question. :?
High
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

November 22, 2024 - 1:51 PM

clafon wrote: ↑Nov 21, 2024 - 5:04 PM Basically, how do you know if a .NET 8.0 update should be applied to a server or a machine? When editing the "Wua" package to "Allow" updates, there seems to be a missing field for "affected" machines; this is just our opinion.
Your comment is relevant; currently, if you want to see the list of machines involved in a cab, you cannot do so from this window.

You have to go through "Windows Update", find the cab and click on "show clients".

It should be possible to search from this window. I'll open an internal ticket for this
High
Answer

Return to "WAPT usage (Console, Agent) / WAPT usage (Console, Agent)"


  • To go further with WAPT