WAPT agent deployment via GPO

[MohamedMK2]

Hello,

I am setting up WAPT 2.6.1.17834.

Environment:

WAPT Server installed on Ubuntu
, WAPT Console installed on a Windows Server 2022 server.
Target machine: Windows 11 Pro.

GPO configuration:

My GPO is configured as described in the WAPT documentation. In the startup script, I added waptdeploy.exe, which I downloaded from my WAPT Server interface: https://srv-wapt.mydomain.com.

The file is located in the folder \\mydomain\SYSVOL\mydomain\Policies\{GUID}\Machine\Scripts.
The parameters correspond to those provided by the WAPT Server interface.

--hash=https://srv-wapt.mydomain.com/api/v3/ge ... tagent.exe

Problem:

Automatic deployment via GPO is not working. After the workstation starts, the GPO is correctly applied. However, the agent installation does not start.

A temporary folder is created at each startup in:
C:\Program Files (x86)\wapt\private\tmp\waptdeploy_xxxxx.tmp

. waptagent.exe is the only file in this folder.

However:

waptservice is never installed
; wapt-get.exe is not present;
the workstation does not appear in the WAPT console.

Checks performed

The scripts.ini file contains:


[Startup]
0CmdLine=waptdeploy.exe
0Parameters=--hash=https://srv-wapt.mydomain.com/api/v3/ge ... tagent.exe


I also verified that:

the hash of waptagent.exe matches the one provided by WAPT;
waptdeploy.exe used in the GPO is the one recently downloaded from the WAPT server;
the get_waptagent_exe URL works;
the file download completes correctly.


If I manually run the downloaded file:

waptagent.exe /SILENT or waptagent.exe /VERYSILENT,

the installation proceeds correctly:

waptservice is created, the computer appears in the WAPT console, and everything works normally.
The folder C:\Program Files (x86)\wapt\private\tmp\waptdeploy_xxxxx.tmp no longer exists.

I also tried

enabling "Always wait for network at startup and logon," unfortunately without success.

It seems that waptdeploy.exe correctly downloads waptagent.exe, but never actually starts its installation when run as a GPO startup script.

Have you encountered this behavior in version 2.6.1.17834, or do you have any suggestions?

Thank you in advance for your help.

[sfonteneau]

We've identified this problem with some clients. It's visible if you allow the startup scripts to be displayed in the Waptdeploy GPO.

Waptdeploy downloads the file to a tpm folder.

The EDR detects that the installation directory is a temporary directory simply because the word /tmp/ is in the path.

In newer versions of Wapt, we've modified the directory to remove /tmp/, and that seems to be working better.

What EDR do you see in your case?