Invalid OR(unit) packets

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Locked
davidbkk
Messages: 24
Registration: May 15, 2020 - 08:29

October 20, 2021 - 06:10

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 3211 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.
High
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :
Contact dcardon

October 20, 2021 - 9:30 AM

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.
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
High
davidbkk
Messages: 24
Registration: May 15, 2020 - 08:29

October 20, 2021 - 12:07

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.
High
davidbkk
Messages: 24
Registration: May 15, 2020 - 08:29

November 1, 2021 - 5:35 AM

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.
High
Locked

Return to “WAPT Packages”


  • To go further with WAPT