Page 1 of 1

Invalid OR(unit) packets

Published: October 20, 2021 - 06:10
by davidbkk
Wapt Enterprise 2.1
Debian 10

Good morning,

Sorry if this question has already been asked.

My OU (unit) packages are displayed in red and I get this message when I try to update them.
2.PNG
2.PNG (67.77 KB) Viewed 3215 times

In practice, when I upgrade packages, they do not upgrade on the machine packages; the unit/machine link is no longer established.
I re-signed the unit packages but it didn't change anything.

It appears that these are all the OUs that have a space, and I have a large number of them.

What to do:
- Rename the OUs in my Active Directory? What's the simplest method?
- Other solutions?

Thank you for your help.

Sincerely.

David.

Re: Invalid OU(unit) packets

Published: October 20, 2021 - 9:30 AM
by dcardon
Hi David,

there was indeed a name sanitization that was a bit too drastic. Spaces are being removed for software packages, but apparently this was also applied to OrgUnit packages, which shouldn't have been the case. Thanks for reporting this bug.

I'll check with the developers to get a quick patch; there's not much to fix, it will just require reinstalling the console, the logic on the agent side shouldn't change anything.

Sorry for the inconvenience, see you soon, :-)

Denis.

PS: Personally, I advise never using spaces, accents, or special characters in AD object names; it avoids having to deal with tricky cases when scripting AD.

Re: Invalid OU(unit) packets

Published: October 20, 2021 - 12:07 PM
by davidbkk
Thank you, Denis, for your quick reply.

I explained that this was blocking the download of updates to the machine packages, but that's not the case; we just needed to wait a little longer.

So there's no rush.

Best regards,

David.

Re: Invalid OU(unit) packets

Published: November 1, 2021 - 5:35 AM
by davidbkk
Hello,

I apologize for contacting you again, but this is indeed causing real problems with the sub-OUs. Some packages are no longer recognized during updates and are not being downloaded to the sub-OUs, conflicting packages are not being applied, and there are quite a few bugs, mainly with synchronization between the OUs and sub-OUs. This is becoming complicated for us.

The same issue arises with access to Veyon; we use it for maintenance, and the right-click functionality made our lives much easier.

Do you think you'll be able to release a patch soon?

Thank you for your help.

Best regards,

David.