Tranquil IT Forum

By the way, version wapt-2.2.1.11957-da81836d has been out for a while now. Don't hesitate to upgrade from time to time; there are plenty of bug fixes with each new version.

WAPT version 2.2.2 should be released next week, also with quite a few minor fixes (see https://www.wapt.fr/fr/doc/wapt-changel ... 2022-07-12 ).

Best regards,

Denis

I think I've found the source of the problem.
Our Scribe server is quite well-organized; I'm working hard to ensure everything runs smoothly and without any buggy rules or scripts.
We don't use Active Directory, but Samba3.

I haven't tested it on a machine outside the domain and without the Scribe client. I also thought that might be the issue, but it
turns out WPKG was causing a conflict. WPKG is our application deployer integrated into Scribe
, and I was running waptdeploy before uninstalling WPKG.
Simply reversing the process and uninstalling WPKG first is all it takes. Although WPKG is configured to launch when the PC starts up (and not when it shuts down like Wapt), it seems to be causing a problem with this GPO. In any case, it significantly lengthens the Waptagent installation.

The difference is striking: if WPKG is still present on the client machine, the Wapt agent takes 12 minutes to complete, compared to 2 minutes if WPKG is uninstalled beforehand!

Thanks for the feedback, glad it's finally resolved