Good morning,
We are using Discovery version 2.2.3 on a DEBIAN server and the admin console on Windows 10.
Our PCs managed on WAPT are mostly mobile.
We observe that these PCs, depending on where they connect from, are detected as different machines by WAPT (examples below).
We sometimes end up with 5-6 lines for the same position.
The MAC address is the same, but the machine name has changed.
This is very problematic for managing positions.
Is there a possibility for WAPT to consider these different lines as a single machine (which is the case) based on the MAC address for example?
Positions that appear multiple times on the console
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 :
Can you tell us more about your identification method?
https://www.wapt.fr/fr/doc-2.2/wapt-con ... apt-agents
https://www.wapt.fr/fr/doc-2.2/wapt-con ... apt-agents
Good morning,
Thank you for your prompt reply.
Indeed, we had not explored this point before our deployment.
We haven't set any particular parameters; we are in default mode.
What do you advise us to do in our situation?
Here are the agent build parameters we currently have: Is the identification configured only on the agent?
Thank you for your prompt reply.
Indeed, we had not explored this point before our deployment.
We haven't set any particular parameters; we are in default mode.
What do you advise us to do in our situation?
Here are the agent build parameters we currently have: Is the identification configured only on the agent?
