Hello,
when I run the "package installation" on several selected machines, some return this error message:
"Host target UUID is not matching your request."
What does this error mean?
And what should I do to fix it?
Do I need to go back to all the affected machines to perform a procedure?
Thank you in advance.
Best regards,
Clément.
Error message on the WAPT 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
Okay, so I'll answer my own question then. 
Indeed, WAPT uses motherboard UUIDs to list PCs on the network, but quite a few motherboards (Gigabyte in particular) have identical UUIDs and therefore cause a bit of a mess in WAPT (and that's putting it mildly).
To fix this, you need to create a new UUID that will be stored both locally and on the server so that WAPT can find the machine.
You therefore need to access the machine in question or take control of it to run this command:
`c:\wapt\waptpython -c "import common,uuid; wapt = common.Wapt(); print 'Old UUID: %s' % wapt.host_uuid; wapt.host_uuid='%s' % uuid.uuid4(); print 'New UUID: %s' % wapt.host_uuid;print wapt.update_server_status()"`
The new generated UUID will allow the PC to be visible at all times on the WAPT console and no longer only randomly depending on which other machines are running.
Have a good day.
Indeed, WAPT uses motherboard UUIDs to list PCs on the network, but quite a few motherboards (Gigabyte in particular) have identical UUIDs and therefore cause a bit of a mess in WAPT (and that's putting it mildly).
To fix this, you need to create a new UUID that will be stored both locally and on the server so that WAPT can find the machine.
You therefore need to access the machine in question or take control of it to run this command:
`c:\wapt\waptpython -c "import common,uuid; wapt = common.Wapt(); print 'Old UUID: %s' % wapt.host_uuid; wapt.host_uuid='%s' % uuid.uuid4(); print 'New UUID: %s' % wapt.host_uuid;print wapt.update_server_status()"`
The new generated UUID will allow the PC to be visible at all times on the WAPT console and no longer only randomly depending on which other machines are running.
Have a good day.
