Hello,
I have the WAPT management console on a Windows 10 machine and it works.
I changed the hard drive, installed Windows 10 v2004, and now I can't get the console to work with the .crt and .pem keys.
I put the old hard drive back in and the console works.
I've read the documentation, but nothing works.
Is there a solution?
Yann
Management console installation error
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
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I don't have a key problem with Windows 10 v2004.
The problem lies elsewhere.
The problem lies elsewhere.
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Good evening Yann,
what exactly isn't working? Is it opening the console, configuring the local keys, assigning a package to a workstation, etc.?
Which version of WAPT are you using?
Denis
what exactly isn't working? Is it opening the console, configuring the local keys, assigning a package to a workstation, etc.?
Which version of WAPT are you using?
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
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
Hello,
when I open the administration console on a Windows machine, I get a key or password error. I think I'm not putting the .crt and .pem keys in the right places. In my previous installation, the PEM key was in C:\private and the .crt key was in \issl. The password is OK.
I reinstalled the administration console, but it doesn't uninstall everything because it keeps the settings from the previous installation.
The server (version 1.81) works fine; I manage it with the console from the old disk, which is working.
I installed the administration console on another machine, and I get the same key/password error. Where should I put the private PEM key and the public .crt key?
Yann
when I open the administration console on a Windows machine, I get a key or password error. I think I'm not putting the .crt and .pem keys in the right places. In my previous installation, the PEM key was in C:\private and the .crt key was in \issl. The password is OK.
I reinstalled the administration console, but it doesn't uninstall everything because it keeps the settings from the previous installation.
The server (version 1.81) works fine; I manage it with the console from the old disk, which is working.
I installed the administration console on another machine, and I get the same key/password error. Where should I put the private PEM key and the public .crt key?
Yann
