Tranquil IT Forum

Hello,

I'm trying to deploy my WAPT 1.8.2 agent to a few workstations (to start) in order to begin actively deploying WAPT packages.
I'm using the documentation for deploying the agent via GPO.
I created my GPO on my SAMBA 4 Active Directory domain, and it's visible and applied on my test machine (gpresult).
However, it's not running on my machine. Manual execution via:
`waptdeploy.exe --hash=XXX --minversion=1.8.2.7267 --waptsetupurl=https://XXX/wapt/waptagent.exe --wait=15` works perfectly.
I tried running it as a startup and shutdown script, and in both cases, nothing happens. In my log console on my machine (Windows 7), the GPO is correctly indicated as being applied, and the startup scripts as being executed.

I'm not sure what my mistake is or why the GPO isn't running.
The client workstation is logged in as a domain user with admin rights and is running Windows 7 x64.
The antivirus software is working correctly and is not logging any blocks against Wapt.

I also read your article https://www.wapt.fr/fr/doc/wapt-common- ... blems.html regarding the network sometimes being unavailable when the machine starts up.
Since we have mobile users, we cannot condition network availability based on the execution of Group Policy Objects (GPOs).
The idea is to deploy the Wapt agent via GPO when users are present and connected to the network.

Hello,

I've noticed that the script doesn't work between a Windows Server 2012 R2 and a Windows 10 client.

What operating systems are your server and clients running?

Have you tried accessing https://xxx/wapt/waptagent.exe and manually installing the agent?

Malo wrote: ↑August 6, 2020 - 10:17 AM Hello,

I've noticed that the script doesn't work between a Windows Server 2012 R2 and a Windows 10 client.

What are the operating systems of your server and clients?

Have you tried accessing https://xxx/wapt/waptagent.exe and manually installing the agent?

My server runs on Debian 4.19 and the clients on Windows 10 x64 and Windows 7 x64
I have access to the URL from my clients and the manual installation works perfectly.
After several tests, I think I'm encountering the problem of network unavailability when a workstation starts up or shuts down. Since I have mobile workstations, I can't afford to wait indefinitely for the network to become available before logging the user in.
So I tested the scheduled task installation method to install the agent at startup but with the executables previously copied.
It seems to be working well.
Deploying via GPO at boot on the server URL still seems difficult to achieve on a Windows machine without waiting for the network!