[WAPT 1.5] Maximum 12 hosts?

[Intra1910]

Hello,

I installed a WAPT server (version 1.5.1.23, running on Debian Stretch 9.4), configured my GPO, and the agents are being deployed.

However, in the console (Windows 10), I'm having the problem of only seeing a maximum of 11 hosts (it was 10 last week). Each new host or each update to an existing host is moved to the newest list, but this removes a host from the list, and I seem to have a host limit.

PS: I'm using the free version.

Do you have any ideas?


Thanks in advance for your help!

[AlbanUCA]

Hi,

since I'm browsing the forum, maybe this will help:
https://www.wapt.fr/fr/doc-1.5/Frequent ... bios-bogue

I've already had this problem with machines having the same UUID.

Alban

[Intra1910]

Thank you for your reply

I tried it with my computer via a command prompt opened as administrator:

C:\Windows\system32>wapt-get generate-uuid
2018-06-05 16:40:49,834 WARNING Host on the server is not known or not known under this FQDN name (known as None). Trying to register the computer...
2018-06-05 16:40:54,555 WARNING New registration successful
New UUID: f70fcb84-2e44-4248-83b1-bf9e67dfcd0c

My position was added twice.
I now have 12 hosts.
My old computer has disconnected.
The new one was paired with the clock symbol.
I might need to restart my PC, I don't know.
Edit: I reinstalled the agent on my machine so I wouldn't have to restart, and it turned green again.

That's strange... I don't think that's it, each machine is installed manually, not from an OS image.

[Intra1910]

Next, some workstations don't yet have the WAPT agent installed, and I don't know why.

I chose to deploy via GPO as indicated in the WAPT documentation.
The DeployWAPT command was executed via the WAPT server's web interface, and the script parameters were: "waptdeploy.exe --hash=MyKey... --minversion=1.5.1.23 --wait=15" (which I found in my WAPT server's web interface).

Then, in my GPO, I targeted authenticated users (this is the default setting) and a group that has access to all PCs.
In the "Delegation" section, I granted edit permissions to this group.


Do you have any ideas?

[dcardon]

Hello Intra1910,

I installed a WAPT server running version 1.5.1.23 (on Debian Stretch 9.4), configured my GPO, and the agents are being deployed.

However, in the console (Windows 10), I have the problem of only having a maximum of 11 hosts (last week it was 10). Each new host or each update to a host is moved to the newest list, but this removes a host from the list, and I seem to have a host limit.

There is no limit to the features of the free version.

PS: I'm using the free version.

It's better to say "the free version". Indeed, free doesn't mean open source, and open source doesn't mean free of charge.

Do you have any idea?

It is very likely that you have workstations with the same BIOS UUID. You have three possibilities:

• Add the parameter use_fqdn_as_uuid=1 so that the computer name, and not the BIOS UUID, is used as the reference

• Run the command line wapt-get generate-uuid on each machine (can be run via GPO or WAPT package)

• buy computer hardware that has a BIOS configured well enough to have a unique GUID

Sincerely,

Denis

[Intra1910]

Hello Intra1910,

I installed a WAPT server running version 1.5.1.23 (on Debian Stretch 9.4), configured my GPO, and the agents are being deployed.

However, in the console (Windows 10), I have the problem of only having a maximum of 11 hosts (last week it was 10). Each new host or each update to a host is moved to the newest list, but this removes a host from the list, and I seem to have a host limit.

There is no limit to the features of the free version.

PS: I'm using the free version.

It's better to say "the free version". Indeed, free doesn't mean open source, and open source doesn't mean free of charge.

Do you have any idea?

It is very likely that you have workstations with the same BIOS UUID. You have three possibilities:

• Add the parameter use_fqdn_as_uuid=1 so that the computer name, and not the BIOS UUID, is used as the reference

• Run the command line wapt-get generate-uuid on each machine (can be run via GPO or WAPT package)

• buy computer hardware that has a BIOS configured well enough to have a unique GUID

Sincerely,

Denis

Thank you for your reply.

Ah cool, so my setting becomes "waptdeploy.exe --hash=MyKey... --minversion=1.5.1.23 --wait=15 use_fqdn_as_uuid=1"or has a different syntax?"
Or, I could try running the wapt-get generate-uuid command on each remote machine only once, but I don't know how to do that yet.

And regarding the positions where the agent has not settled, do you have any idea in relation to what I mentioned above?


Thank you in advance!