Waptagent deployment - non-reachable client

Questions about WAPT Server / Requests and help related to the WAPT server
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
Locked
lazy
Messages: 3
Registration: March 8, 2019 - 11:47

March 8, 2019 - 12:12

- Installed WAPT version 1.7.3.5
- Server OS: Debian 9.7
- Operating system of the administration/package creation machine: Windows Server 2012 R2

Good morning,

I set up the Wapt server in my establishments 2-3 weeks ago. Everything works well except for the deployment of the agent on client workstations.
When I download and install the agent via the executable on a client machine, I have no problem. But when I try to do it via GPO, scheduled task, or simple command line, the client machine appears correctly in the WAPT console, but it is not accessible (no green indicator light icon in the "Reachable" column).

I tried adding some extra details like the server address, but it didn't change anything...

Code: Select all

waptdeploy.exe --hash=monHash --minversion=1.7.3.5 --waptsetupurl=http://monagent.exe --setupargs="/wapt_server https://mon.server" --wait=15
When using the command line directly, there are no error messages in the terminal. I have no idea.

Thank you in advance for your help
User avatar
agauvrit
WAPT Expert
Messages: 238
Registration: Nov 17, 2016 - 10:25
Location: Nantes
Contact :

March 11, 2019 - 09:46

If the green icon does not appear, it could be a problem with the 'http_proxy' environment variable, an issue encountered by a WAPT Enterprise client.
Another possibility is that the computer's clock is not synchronized with the server's.
CHISFE
Messages: 3
Registration: August 27, 2019 - 2:41 PM

August 27, 2019 - 2:56 PM

- WAPT version installed: 1.7.3.5
- Server OS: Windows 7 Pro
- Client machine OS: Windows 7 Pro 32-bit

Hello everyone,

on my WAPT server with the latest version, I have all the computers on the console, but on some workstations, there's no green "reachable" icon. I can't figure out where the problem is coming from. The client workstations are set to the same time as the WAPT server. Can you help me, please?

A screenshot is attached.

Thank you in advance, and a big thank you again to the entire WAPT team.


Sincerely,

CHISFE
Attachments
B7BEDF21-1AD8-4BFC-B951-E1F0DE60AE82.jpeg
B7BEDF21-1AD8-4BFC-B951-E1F0DE60AE82.jpeg (38.08 KB) Viewed 3575 times
Locked