[SOLVED] Unable to install software via the console

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Locked
fred34
Messages: 2
Registration: May 3, 2018 - 4:26 p.m.

May 3, 2018 - 4:45 PM

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
User avatar
agauvrit
WAPT Expert
Messages: 238
Registration: Nov 17, 2016 - 10:25
Location: Nantes
Contact :

May 3, 2018 - 5:42 PM

Hello,

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

Regards,

Alexandre
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

May 3, 2018 - 5:52 PM

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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
fred34
Messages: 2
Registration: May 3, 2018 - 4:26 p.m.

May 4, 2018 - 09:46

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

Thanks again for your help...
Locked