Add windows client to zenoss monitoring Rumi, September 27, 2015 Allow ICMP Through Firewall Firstly you need to allow incoming ICMP ping request since this is the way Zenoss checks if the system is online. Go to: Server Manager -> Configuration -> Windows Firewall with Advanced Security -> Inbound Rules Do the following: Enable rule “File and Printer Sharing (Echo Request – ICMPv4-In)”. Manually Configure WinRM Service Go to: Start -> Search programs and files -> gpedit.msc -> Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM) -> WinRM Service Configure as follows: Allow automatic configuration of listeners -> Enabled -> Under IPv4 filters input “*” without the quotation marks Allow Basic authentication -> Enabled Allow unencrypted traffic -> Enabled Manually Configure Windows Remote Shell Go to: Start -> Search programs and files -> gpedit.msc -> Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Shell Configure as follows: Allow Remote Shell Access -> Enabled Specify maximum number of processes per Shell -> Enabled -> MaxProcessesPerShell = 2147483647 Specify maximum number of shells per user -> Enabled -> MaxShellsPerUser = 2147483647 Specify shell Timeout -> Enabled -> ShellTimeOut = 2147483647 Run WinRM Quick Config Run WinRM quick configuration which adds a firewall exception, allows remote access to the machine for management and starts a WinRM HTTP listener. Go to: Start -> Search programs and files -> cmd Run “winrm quickconfig” and press “y” as follows. Check WinRM HTTP Listener is Running Go to: Start -> Search programs and files -> cmd Run “winrm enumerate winrm/config/listener” to make sure it is running and accepting connections as follows. Add Windows Client to Zenoss Go to Zenoss web GUI to the following page: Infrastructure -> Devices -> Details Under “Configuration Properties” enter “zWinRMUser” and “zWinRMPassword” details. This user should have administrative rights on Windows Zenoss client machine. Next on the Zenoss Infrastructure page click “Add a Single Device”. Enter the Windows machine name or IP address. Make sure to choose the device class “/Server/Microsoft/Windows”! Voila, the Windows machine was successfully added to your Zenoss. The Windows machine should be modeled automatically – the filesystems and services should appear along with interfaces and processors. Src: https://geekpeek.net/add-windows-client-to-zenoss-monitoring/ Related Configurations (Linux) Configurations (Windows) WindowsZenoss
Proxmox Firewall Service Disable using Command March 20, 2024 Chrooting and then doing: systemctl disable pve-firewall systemctl mask pve-firewall should do the trick. then after rebooting and fixing your config, systemctl unmask pve-firewall systemctl enable pve-firewall systemctl start pve-firewall Should return to the defaults again. Ports used by Proxmox VE Web interface: 8006 (TCP, HTTP/1.1 over TLS) VNC Web… Read More
Running pfSense in a XenServer with xenguest November 19, 2022 If you deploy pfSense on a XenServer, you may be shocked at the performance loss-specially on interface speed! But wait, there are some tweaks to make this usable. Installing pfSense Go ahead and setup pfSense like normal, and when you are done, perform the following tweaks. (the day till it’s… Read More
Virtualmin create a catch-all email account June 21, 2023 This tutorial will cover how to setup a catch-all email account. Once finished, it will be the default destination for any email arriving at your domain, unless overridden by another email account or alias. It assumes you have logged into Virtualmin as the root user. You can make any email… Read More