Hello,
I'm currently having a problem with some new workstations we recently acquired.
During the WADS deployment, after installing Windows 11, we use PostScript to deploy a WAPT package. The only issue on these new workstations is that nothing is being deployed and the deployment completes.
After checking (via the command prompt with the command "wapt-get update"), we're getting an error: "Missing local service certificate C:\Program Files (x86)\wapt\public\localservice.crt", which is indeed missing.
Do you have any idea what could be causing this? I've been looking into the network side of things, but I haven't found a solution yet
. Thank you in advance!
[RESOLVED] Missing local certificate during deployment
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: 2363
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello
, normally the file C:\Program Files (x86)\wapt\public\localservice.crt
is created directly when the service starts.
Did you add a short delay in the startup script to allow the service time to start?
Is the service running correctly?
The last time I saw this, an antivirus program panicked when it saw the file.
, normally the file C:\Program Files (x86)\wapt\public\localservice.crt
is created directly when the service starts.
Did you add a short delay in the startup script to allow the service time to start?
Is the service running correctly?
The last time I saw this, an antivirus program panicked when it saw the file.
Hi Simon,
I had indeed set the time to 120 seconds in the script. That said, I increased the time to 300 seconds and now the process runs smoothly!
I was a little surprised since this same deployment script worked perfectly on other brands, but as long as the solution works, I'm happy!
Have a good day
I had indeed set the time to 120 seconds in the script. That said, I increased the time to 300 seconds and now the process runs smoothly!
I was a little surprised since this same deployment script worked perfectly on other brands, but as long as the solution works, I'm happy!
Have a good day
