Tranquil IT Forum

Good morning,

Environmental information:
WAPT Server OS version: Debian 12
WAPT version: 2.5.4.15342 (Enterprise Edition)
Operating system of the machine from which the packages are created: Windows 10 22H2
Secondary repository: Ubuntu 22.04

EDIT: The problem below is solved; it was related to the secondary repository certificate.

Here are the problems I'm encountering:
I have four machines that were brought up via AD, they are part of two sub-OUs (B and C).
I applied package changes at the parent OU level (A). The modification, and therefore the added package, was only done on one machine (you can see in the screenshot that I am keeping the unit package at 1 even though it is version 5) the others did not recover anything, neither the added package, nor the unit package from the OU.
If I want to add the package directly to a machine, it tells me there is a dependency problem (which I can understand).
If I update the unit package (of OU A), it does not update, even on the machine for which it initially worked.

These 4 machines are linked to the secondary repository: the repository is properly synchronized (I forced it)
The machines and the warehouse do indeed have the certificate that signed the packages.
For the secondary repository, the rule applies to the IP address and the boxes checked for the folder type are: WAPT and WUA.
The repository is properly connected, no errors.

Hoping I've been clear, thank you for your help.

Sincerely,

Guillaume.

Hi Guillaume,

thanks for the feedback, glad you found the problem quickly

. Best regards,

Denis