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.
[RESOLVED] WAPT 1.8.2 - Deployment via GPO
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
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
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?
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?
-
Geovariances
- Messages: 15
- Registration: July 28, 2020 - 10:56 AM
My server runs on Debian 4.19 and the clients on Windows 10 x64 and Windows 7 x64Malo 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?
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!
