Tranquil IT Forum

Hello,

I'm having a small problem with the WAPT console. The following options are grayed out:
Check for updates,
Launch installations,
Refresh inventory
, Restart WAPT service,
Forget a package
, Install a package.

As a result, I can no longer manage my workstations.
Console version 1.6.2.7,
Server 1.6.2.7, Community
Agent 1.6.2.7.

Can you please help me?

Thank you in advance for your help.

Fabrice

This is because you haven't specified the path to your personal certificate (and therefore your private key) in the configuration (Tools/Preferences/Personal Certificate Path).
Generally, the two files (.pem and .crt) are located in c:\private, but you may have placed them elsewhere.

The console needs them to sign actions to be executed on remote machines.

htouvet wrote: ↑Oct 16, 2018 - 4:15 PM It's because you haven't entered the path to your personal certificate (and therefore your private key) in the configuration (Tools/Preferences/Personal Certificate Path).
Generally, the two files (.pem and .crt) are located in c:\private, but perhaps you put them somewhere else.

The console needs them to sign actions to be executed on remote machines.

Good morning,

This element is correctly entered and yet it no longer works, whereas last week I deployed it without any problems.

Do you have any other leads?

Thank you again for your help

Hello Fabrice,

ryoken95 wrote: ↑Oct 16, 2018 - 4:28 p.m.

htouvet wrote: ↑Oct 16, 2018 - 4:15 PM It's because you haven't entered the path to your personal certificate (and therefore your private key) in the configuration (Tools/Preferences/Personal Certificate Path).
Generally, the two files (.pem and .crt) are located in c:\private, but perhaps you put them somewhere else.

The console needs them to sign actions to be executed on remote machines.

This element is correctly entered and yet it no longer works, whereas last week I deployed it without any problems.

Do you have any other leads?

Are you experiencing this issue on just one machine or on all machines? Do the machines you want to perform actions on have a "Reachable" status of "OK"? Are you certain your private key matches the one deployed on the workstations?

Sincerely,

Denis

dcardon wrote: ↑Oct 16, 2018 - 6:50 PM Hello Fabrice,

ryoken95 wrote: ↑Oct 16, 2018 - 4:28 p.m.

htouvet wrote: ↑Oct 16, 2018 - 4:15 PM It's because you haven't entered the path to your personal certificate (and therefore your private key) in the configuration (Tools/Preferences/Personal Certificate Path).
Generally, the two files (.pem and .crt) are located in c:\private, but perhaps you put them somewhere else.

The console needs them to sign actions to be executed on remote machines.

This element is correctly entered and yet it no longer works, whereas last week I deployed it without any problems.

Do you have any other leads?

Are you experiencing this issue on just one machine or on all machines? Do the machines you want to perform actions on have a "Reachable" status of "OK"? Are you certain your private key matches the one deployed on the workstations?

Sincerely,

Denis

Hello Denis,

I have the problem on all machines.
The machines do indeed have the Reachable status.
This private key has been used for months without any problems. I even deployed BIOS updates last week.

Regards

Upon reviewing the source code: Therefore, the action is not grayed out if at least one machine is selected and is "connected," and the file specified in the "personal_certificate_path" parameter of the [global] section of the %LOCALAPPDATA%\waptconsole\waptconsole.ini file exists
(Verify that the user under which the wapt console is running has access to this file)

htouvet wrote: ↑Oct 17, 2018 - 09:34 Upon reviewing the source code:

Code: Select all

  Enabled:= (GridHosts.SelectedCount>0) and OneHostIsConnected(GridHosts) and FileExistsUTF8(WaptPersonalCertificatePath)

Therefore, the action is not grayed out if at least one machine is selected and is "connected," and the file specified in the "personal_certificate_path" parameter of the [global] section of the %LOCALAPPDATA%\waptconsole\waptconsole.ini file exists
(Verify that the user under which the wapt console is running has access to this file)

Good morning,

I confirm that the actions are greyed out and that the user does have access to this file (I am the administrator of the machine on which the wapt console is running)

Hello Fabrice,

ryoken95 wrote: ↑Oct 17, 2018 - 10:03

htouvet wrote: ↑Oct 17, 2018 - 09:34 Upon reviewing the source code:

Code: Select all

  Enabled:= (GridHosts.SelectedCount>0) and OneHostIsConnected(GridHosts) and FileExistsUTF8(WaptPersonalCertificatePath)

Therefore, the action is not grayed out if at least one machine is selected and is "connected," and the file specified in the "personal_certificate_path" parameter of the [global] section of the %LOCALAPPDATA%\waptconsole\waptconsole.ini file exists
(Verify that the user under which the wapt console is running has access to this file)

I confirm that the actions are greyed out and that the user does have access to this file (I am the administrator of the machine on which the wapt console is running)

We'll need to provide a bit more information... The fact that the menus are grayed out doesn't need confirmation; we'll take your word for it. However, I want to emphasize that an administrator user doesn't necessarily have access to all files (the administrator account is more like a sudoer than root on a modern Windows system). Access depends not only on permissions but also on the security tokens of the process trying to access the file.

Is there anything special in the path to the key file? Network drive, encrypted drive, special character, special permissions, etc.? Do you have User Account Control (UAC) enabled on the machine? When you launched the WAPT console, did you launch it with elevated privileges or not? Is the account a local administrator or a domain administrator?

Sincerely,

Denis