WAPT on a non-persistent Citrix server

[jcdemarque]

Hello,

We deployed the WAPT agent on our Citrix "master" server running Windows Server 2019, which is then cloned and distributed across 12 Citrix VDA servers.

The WAPT packages update correctly using a computer startup script that runs `wapt-get update` and `upgrade`, but the WAPT agents all appear offline and don't show up correctly in the console, preventing any interaction from the console.

I tried using `wapt reset-uuid` and then `generate-uuid` in my computer startup script, but there still seem to be some issues with the VDA display.

What would be the best way to ensure the agent shows up online in the console with the correct server name at each server startup?

I've seen packages like `WAPT-Generate-Random-UUID-if-Needed` and `WAPT-RESET-UUID` that seem to do the same thing; have I missed one?

Thank you for your feedback, and have a good day.

[dcardon]

Hello Jean-Charles,

Which version of WAPT?

Could you try doing it via the command line (without a script)?

The following command should create a random uuid stored in the waptdb.sqlite database.

Code: Select all

wapt-get generate-uuid

You can verify that the value has been changed correctly with the command (which will return the new random uuid)

Code: Select all

wapt-get getparam uuid 

You can also check the VM's UUID with the following command (to see if the clones are too "perfect"):

Code: Select all

wapt-get biosinfo

Or, more simply, to retrieve all the UUIDs that WAPT thinks it has (which may be incorrect if there is a bug)

Code: Select all

c:\Program Files (x86)\wapt>wapt-get get-params "*uuid*"
{
        "hardware_uuid": "b91ca9cc-1ec8-11b2-a85c-fb1f40f73e05",
        "random_uuid": "RND-59254400-E310-4218-8EBA-5E7C38AFD25A",
        "server_uuid": "7c54647e-1b54-11ea-bcbe-cae466b691e5",
        "uuid": "b91ca9cc-1ec8-11b2-a85c-fb1f40f73e05"
}

Exit code: 0

When you write your script, I imagine it's non-interactive. Could you try using the following command to prevent the registration that follows `generate-uuid` (the machine tries to re-register immediately afterward with its new uuid) from causing problems? The `wapt-server-user` argument is required but won't be used.

Code: Select all

wapt-get generate-uuid --not-interactive --wapt-server-user=admin

Sincerely,

Denis

[jcdemarque]

Thank you for your reply.
The version is the latest, 2.5.5.15697, for both the server and agent. I also added the WAPT-UPGRADE package to the Citrix servers to be sure.

The command `wapt-get getparam uuid` returns a list of available options, but it's not recognized by wapt-get. I tried using the command `wapt-get get-params "uuid"` instead.

I do have different BIOSINFO values ​​between the VMs. The Citrix deployment uses a VMware clone and then individualizes the VMs.

The hardware_uuid and uuid values ​​are identical between the Citrix servers.

There doesn't appear to be a RandomUUID in my configurations.

Here is my amended startup script:
`wapt-get generate-uuid --not-interactive --wapt-server-user=admin > c:\temp\wapt.log`
`wapt-get register >> c:\temp\wapt.log`
`wapt-get update >> c:\temp\wapt.log`
`wapt-get upgrade >> c:\temp\wapt.log`

Would it be more useful to switch to the computer name rather than the BIOS UUID?

The UUID returned by the `biosinfo` command is different from the one stored in `wapt-get get-params "*uuid*"`.

Should I "clean up" the WAPT configuration before cloning the VMs? Have

a good day,

[dcardon]

Hello Jean-Charles,

Would it be more useful to switch to the computer name rather than the BIOS UUID?

there is use_fqdn_as_uuid , cf [1]

Sincerely,

Denis

[1] https://www.wapt.fr/en/doc/wapt-advance ... l-settings