GPO installation problem
Published: May 16, 2023 - 2:42 PM
Client machine OS: Windows 11
Version 2.4.0
Build: 2.4.0.13958
Edition: Discovery
Hello,
After following the documentation on deploying WAPT via GPO, I'm getting this error on the machines where I deployed the GPO.
After investigation, WAPTService is not listed in the services (not even stopped), the log folder is empty (and the event viewer isn't showing anything either), so there's no information there. When I use the installation command manually in the command prompt as recommended in the documentation https://www.wapt.fr/en/doc/wapt-common- ... k-with-gpo, the command works, WAPT installs correctly, and I no longer get the error message (port 8088 is listening).
I don't seem to have the issue of the domain controller replicating incorrectly, and the only unusual thing I've noticed after several tests is that the "waptservice.exe" file in "C:\Program Files (x86)\wapt" is missing after installation via GPO.
I'm starting to think the problem stems from the Discovery version, but I haven't seen any mention of this in the documentation.
Do you have any idea what the problem might be?
Thank you,
Ryan
Version 2.4.0
Build: 2.4.0.13958
Edition: Discovery
Hello,
After following the documentation on deploying WAPT via GPO, I'm getting this error on the machines where I deployed the GPO.
After investigation, WAPTService is not listed in the services (not even stopped), the log folder is empty (and the event viewer isn't showing anything either), so there's no information there. When I use the installation command manually in the command prompt as recommended in the documentation https://www.wapt.fr/en/doc/wapt-common- ... k-with-gpo, the command works, WAPT installs correctly, and I no longer get the error message (port 8088 is listening).
I don't seem to have the issue of the domain controller replicating incorrectly, and the only unusual thing I've noticed after several tests is that the "waptservice.exe" file in "C:\Program Files (x86)\wapt" is missing after installation via GPO.
I'm starting to think the problem stems from the Discovery version, but I haven't seen any mention of this in the documentation.
Do you have any idea what the problem might be?
Thank you,
Ryan