Hello,
I'm writing to explain my problem:
I installed Wapt Server on a Debian 9.9 machine, and WaptSetup on a Windows Server.
I configured the deployment using a Group Policy Object (GPO).
The issue is that I tested the deployment using this method:
- From the command prompt (cmd): I directly launched the GPO and got an error:
`wapt version: 1.7.5.6177
wapt required version 1.7.5.6177
Nothing to do
Update host status on the server`.
As indicated, the server is running Debian 9.9 and the installed version is 1.7.
When I add `--force` to the end of my command, the GPO launches, but I don't see any improvement.
There are no updates in Wapt Server, on my Debian machine, and no logs of communication with any IP address other than the one already known.
Another problem is that there was a server running Windows 1.13.13 that crashed, and the workstations remained on that version.
The problem is that computers running version 1.13.13 refuse to install version 1.7.4...
How can I fix this? In version 1.13.13, the PC and group were registered under wapt-host; in version 1.7.4, where are the PCs registered?
Sincerely,
William
[SOLVED] Server 1.7 installation on Debian 9.9 and client/agent configuration
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Your WAPT agent is apparently already running the latest version, 1.7.5.6177William wrote: ↑Sep 13, 2019 - 11:42 AM Hello,
I'm writing to explain my problem:
I installed Wapt Server on a Debian 9.9 system, and WaptSetup on a Windows Server.
Deployment was configured via a Group Policy Object (GPO).
The problem is that I tested the deployment using this method:
- from the command prompt (cmd): I directly launched the GPO and I get an error:
Wapt version: 1.7.5.6177
Wapt required version 1.7.5.6177
Nothing to do
Update host status on the server
Code: Select all
wapt version : 1.7.5.6177Yes, because your WaptSetup must be version 1.7.5.6177 and your local agent is also version 1.7.5.6177
Note that the procedure for upgrading from version 1.3 to 1.6 or higher is different!William wrote: ↑September 13, 2019 - 11:42 AM No activity is being reported in waptserver on my Debian system, and there are no logs of communication with any IP address other than the one already known.
Another issue is that there was a server running Windows 1.13.13 that crashed, and the workstations remained on that version.
The problem is that the workstations still running version 1.13.13 refuse to install version 1.7.4...
https://www.wapt.fr/fr/doc/waptserver-u ... 1-3-to-1-6
In the same place! Note that we are only talking about the machine package for groups and software here. Not the inventory!
Can you give us a general overview of the history because I don't understand everything that has been done!
Hello,
thank you for your reply.
On Windows Server 2008 RC, I had a WAPT server (version 1.13.13). The server was crashing, and we could no longer add any ".exe" files.
I uninstalled the 1.13.13 server and installed the 1.7.5* server, but I'm getting error messages.
I tested it on other servers and got
the same error. I also tested it on Debian, and there were no errors.
My problems are:
- Since installing server 1.7.4, when I install the agent myself on the PCs, it works.
- Via Group Policy, when I run the command through Command Prompt as administrator, I get an error:
`wapt version: 1.7.5.6177
wapt required version 1.7.5.6177
Nothing to do
Update host status on the server`
. When I run the same command with `--force` at the end, it runs correctly, but I get no response from the WAPT server.
I just saw that it requires the waptagent.sha256 file to be present. I created a GPO to create this file on each workstation.
My other question is, where is the PC inventory stored, please?
Sincerely,
William
thank you for your reply.
On Windows Server 2008 RC, I had a WAPT server (version 1.13.13). The server was crashing, and we could no longer add any ".exe" files.
I uninstalled the 1.13.13 server and installed the 1.7.5* server, but I'm getting error messages.
I tested it on other servers and got
the same error. I also tested it on Debian, and there were no errors.
My problems are:
- Since installing server 1.7.4, when I install the agent myself on the PCs, it works.
- Via Group Policy, when I run the command through Command Prompt as administrator, I get an error:
`wapt version: 1.7.5.6177
wapt required version 1.7.5.6177
Nothing to do
Update host status on the server`
. When I run the same command with `--force` at the end, it runs correctly, but I get no response from the WAPT server.
I just saw that it requires the waptagent.sha256 file to be present. I created a GPO to create this file on each workstation.
My other question is, where is the PC inventory stored, please?
Sincerely,
William
Hello,
I've solved my problem. My GPO was configured to install at startup, then I switched to Shoutdown, and the WAPT agent installed...
New problem: the agent is installing in a loop!
That is to say, it installs every time I shut down the PC.
Another question: I don't know if I misconfigured my agent or not, but the installation process isn't consistent;
some agents require a password and others don't.
I've solved my problem. My GPO was configured to install at startup, then I switched to Shoutdown, and the WAPT agent installed...
New problem: the agent is installing in a loop!
That is to say, it installs every time I shut down the PC.
Another question: I don't know if I misconfigured my agent or not, but the installation process isn't consistent;
some agents require a password and others don't.
