I've included the fix in the upcoming 2.7 release.
In the meantime, you'll need to copy the file modified via GPO...

Curious.
Probably related to Windows updates. We haven't touched that in years.
I'll implement a fallback.

Could you try replacing the function with:


`def get_language(full_locale=False, separator='_'):
"""Get the OS default locale (example: fr, en, pl, etc.)

>>> get ...`

The latest version of waptagent.exe (2.6.1.17765) is incorrectly flagged as a Trojan by the antivirus WithSecure (
Trojan.TR/Crypt.XPACK.Gen3), but this is a separate issue from waptdeploy, not waptsetup.exe (https://www.virustotal.com/gui/file ...

The initial deployment via GPO works by launching waptdeploy using "cmd.exe /C " ...".
The reason for the regression in behavior on some systems is not yet known...

Script: c:\windows\system32\cmd.exe
Arguments: /C ""

I haven't been able to reproduce the problem yet.

There have been quite a few security-related changes since version 2.6.1.17472.
As a workaround, it's possible to use the waptdeploy.exe from version 2.6.1.17472 with the latest version of waptagent.exe
if the problem is located...

Hi Rémy,
Between these two versions, I don't see what could be causing this.

Could you share the current WADs post-installation script?

Ideally, we should take a look at it with screen sharing.

Hi Rémy,
To compare the behavior in the code, which version of Wapt did you upgrade from?

Hubert

Hello Mélyne,

Kerberos mode is not available in Discovery.
If you are in the testing phase, you can request a temporary license for a few workstations from the sales department.

Regards,

Hubert

Hello Mickael,

Since version 2.6.0.17279, custom logos and templates must be placed in
C:\Program Files (x86)\wapt\custom_templates.

This prevents them from being overwritten during a Wapt upgrade.

The package template in our repository for customizing logos...

There's no concept of an "exception" when you add a dependency.
So if the package is added as a dependency on the OU, all machines in that OU are expected to install it.

The safest way to prevent machines from installing the software or configuration is to add the rule to the setup code...