Hello,
I'm working with WAPT Enterprise version 1.8.2. The WAPT server is running Windows.
I'm a complete beginner with WAPT.
I installed a WAPT agent on a Windows 7 Pro PC. I then manually updated the Windows version (without going through WAPT).
The WAPT console still displays Windows 7 Pro as the operating system.
I should mention that the time of the last contact between the WAPT server and the agent is correctly recorded, but the
PC is considered "Disconnected" (I don't know why).
Thank you in advance for your help.
Incorrect version of Windows reinstalled
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
The complete inventory isn't sent with every connection.
What's sent regularly are software, updates, packages, and other dynamic information (network, etc.).
To get an accurate, up-to-date view, you need to request an inventory update from the console (context menu on the machine / Refresh workstation inventory)
or schedule the periodic retrieval of information using an audit function.
You're not the first to mention this; we surely need to send this information back to the server when it changes...
What's sent regularly are software, updates, packages, and other dynamic information (network, etc.).
To get an accurate, up-to-date view, you need to request an inventory update from the console (context menu on the machine / Refresh workstation inventory)
or schedule the periodic retrieval of information using an audit function.
You're not the first to mention this; we surely need to send this information back to the server when it changes...
Tranquil IT
Hello,
thank you very much for your reply.
It works when the remote computer is identified as reachable, but I'm having trouble with a computer on the network, which is powered on, and from which I load the homepage of my WAPT server, yet it's identified as "disconnected." As a result, the context menu you mentioned is grayed out.
Do you have any idea what the problem might be?
Thank you for your help.
thank you very much for your reply.
It works when the remote computer is identified as reachable, but I'm having trouble with a computer on the network, which is powered on, and from which I load the homepage of my WAPT server, yet it's identified as "disconnected." As a result, the context menu you mentioned is grayed out.
Do you have any idea what the problem might be?
Thank you for your help.
If the device appears disconnected, it could be:
- because he's not on time?
- because it is no longer registered correctly (its public certificate is no longer valid in the database) -> test a "wapt-get register" on the client
- because a proxy is defined at the registry level for the system account (it happens...)
- because an antivirus intercepts the HTTPS stream and prevents the WebSocket from establishing itself
To better diagnose the problem, you can run the wapt service in debug mode:
in a command prompt with elevated administrator privileges:
and analyze the console output
- because he's not on time?
- because it is no longer registered correctly (its public certificate is no longer valid in the database) -> test a "wapt-get register" on the client
- because a proxy is defined at the registry level for the system account (it happens...)
- because an antivirus intercepts the HTTPS stream and prevents the WebSocket from establishing itself
To better diagnose the problem, you can run the wapt service in debug mode:
in a command prompt with elevated administrator privileges:
Code: Select all
runwaptservice.bat -l debugTranquil IT
