Tranquil IT Forum

Hello,

I just migrated my Wapt server from version 1.3 to 1.5.1.23 without any problems. The server is running Debian 9.4 Stretch.

I have a computer lab with 21 Windows 7 64-bit machines, where the Wapt client is installed. Of these 21 PCs, 9 appear on the console with a clock icon, making it impossible to perform updates or install software via the Wapt console. The buttons appear grayed out. The only way to install software is with WaptExit, after shutting down the machine.
I thought it was due to the machine's UUID, but generating a new UUID with the command "wapt-get generate-uuid" yields no results. Uninstalling and reinstalling the client also had no effect.
I should mention that these are cloned PCs (using FOG).

Do you have any ideas or solutions to offer?

Thank you for your help...

Frédéric

Hello,

Problem with the clock not showing the correct time: viewtopic.php?f=10&t=1057&p=3372&hilit=horloge#p3372

Regards,

Alexandre

Hello Frédéric,

fred34 wrote: ↑May 3, 2018 - 4:45 PM I have a computer lab with 21 Windows 7 64-bit machines, where the WAPT client is installed: Of these 21 PCs, 9 appear on the console with a clock icon, making it impossible to perform updates or install software via the WAPT console. The buttons appear grayed out. The only way to install software is via WaptExit, after shutting down the machine.

This means the WebSockets aren't connecting correctly. Could you please check that the workstations and the server are synchronized? Starting with version 1.5, there's a timestamp check for connections originating from the workstations.

fred34 wrote: ↑May 3, 2018 - 4:45 PM I thought it was due to the machine's UUID, but generating a new UUID with the command "wapt-get generate-uuid" doesn't work. Uninstalling/reinstalling the client also didn't help.
I should mention that these are cloned PCs (with FOG).

The UUID used by WAPT is the BIOS UUID, not the Windows installation UUID. Therefore, it makes no difference whether the machine was cloned with or without sysprep.

Does the inventory in the console correctly show that the agents are on version 1.5? This would at least allow us to know if it's a registration problem or a problem with opening websockets.

Could you also test a `wapt-get -l debug register`?

Sincerely

Denis

Yes, it was indeed the time; the PC was connected to our NTP server, but it wasn't synchronizing!

Thanks again for your help...