Wazuh not installing on WS2022
232 views
Skip to first unread message
Brice Nevitt
Jul 13, 2023, 3:32:35 PM7/13/23
to Wazuh mailing list
Is there a compatibility issues with WS 2022? the commands run, even ran the MSI. but its not following through with the service or connection to the Wazuh Manager
Federico Gustavo Caffieri
Jul 13, 2023, 5:02:05 PM7/13/23
to Wazuh mailing list
Hi Brice Nevitt,
To understand the situation a little better, I would need you to provide me with the following information.
- What version of Wazuh are you using? I have carried out tests with the last published version of Wazuh and I was able to connect the WS 2022 agent to the manager without problems.
- Can you see any errors in the logs? You can check with this command:
Into Wazuh manager:
cat /var/ossec/logs/ossec.log | grep -i -E "(error|warning)
Into Wazuh WS agent:
Open the file placed in: C:\Program Files (x86)\ossec-agent\ossec.log
- Did you check if the manager is active?
systemctl status wazuh-manager
- Another thing you can check is that the necessary ports on the manager are open and reachable. The default ports for agent communication and enrollment via agent configuration are 1514/TCP and 1515/TCP.
To understand the situation a little better, I would need you to provide me with the following information.
- What version of Wazuh are you using? I have carried out tests with the last published version of Wazuh and I was able to connect the WS 2022 agent to the manager without problems.
- Can you see any errors in the logs? You can check with this command:
Into Wazuh manager:
cat /var/ossec/logs/ossec.log | grep -i -E "(error|warning)
Into Wazuh WS agent:
Open the file placed in: C:\Program Files (x86)\ossec-agent\ossec.log
- Did you check if the manager is active?
systemctl status wazuh-manager
- Another thing you can check is that the necessary ports on the manager are open and reachable. The default ports for agent communication and enrollment via agent configuration are 1514/TCP and 1515/TCP.
Brice Nevitt
Jul 13, 2023, 5:43:58 PM7/13/23
to Wazuh mailing list
im using Wazuh 4.4. it has installed on every machine so far until i tried ws2022. im not seeing anything on logs. it runs but it wont install on this server for somereason
Brice Nevitt
Jul 14, 2023, 1:54:12 PM7/14/23
to Wazuh mailing list
Update on this, the msi file puts out error 2738. do you know where that relates to
On Thursday, July 13, 2023 at 3:02:05 PM UTC-6 Federico Gustavo Caffieri wrote:
Federico Gustavo Caffieri
Jul 17, 2023, 4:16:31 PM7/17/23
to Wazuh mailing list
Hello Brice Nevitt,
I have tried to reproduce the error you mention without success.
From what I could investigate, it may be a configuration problem in your WS 2022 where the VBScript engine is not registered or points to the wrong path.
Try running the following command in a cmd as administrator:
regsvr32 vbscript.dll
Try the installation again and verify that the 2738 error does not appear again.
Another alternative is to check the default path to the VBScript engine. For this, you will need administrator access in WS 2022 and open the regedit console.
Then go to the following path:
HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
Validate that the default contains the following in data:
C:\Windows\System32\vbscript.dll
Let me know if this was helpful.
I have tried to reproduce the error you mention without success.
From what I could investigate, it may be a configuration problem in your WS 2022 where the VBScript engine is not registered or points to the wrong path.
Try running the following command in a cmd as administrator:
regsvr32 vbscript.dll
Try the installation again and verify that the 2738 error does not appear again.
Another alternative is to check the default path to the VBScript engine. For this, you will need administrator access in WS 2022 and open the regedit console.
Then go to the following path:
HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
Validate that the default contains the following in data:
C:\Windows\System32\vbscript.dll
Let me know if this was helpful.
Reply all
Reply to author
Forward
0 new messages