Executables and scripts to allow for Windows server monitoring
One of the reasons you could not enable Site24x7 server monitoring could be your organization's group policy denying access to the executables, scripts, and batch files associated with Site24x7 server monitoring. Mark the following executables, scripts, and batch files as a safe process and allow access for seamless Windows server monitoring:
Executable files (.exe) to be allowed
For server monitoring:
- MEAgentHelper.exe
- MonitoringAgent.exe
- Site24x7WindowsAgentTrayIcon.exe
- Site24x7WindowsAgentUpgrade.exe
- Site24x7ITAutomation.exe
- Site24x7WinCommunicator.exe (if TLS1.2 is not enabled)
For monitoring using plugins: Site24x7PluginAgent.exe
For Microsoft Applications monitoring: Site24x7AppAgent.exe
For log management using Applogs: Site24x7ApplogAgent.exe
VB Scripts (.vbs), PowerShell scripts (.ps1), and batch scripts (.bat) to be allowed:
- FindProcess.vbs
- TrayIcon.bat
- Restart.bat
- ShortCut.bat
- ShortCut.vbs
- StartServer.bat
- StartService.vbs
- StopServer.bat
- StopService.vbs
- event.vbs
- Exchange2007InventoryDetails.ps1
- Exchange2010InventoryDetails.ps1
- Exchange2013InventoryDetails.ps1
- Exchange2016InventoryDetails.ps1
- Exchange2019InventoryDetails.ps1
- ExecuteRemoteInstall.ps1
- file.vbs
- folder.vbs
- GetProcessAndServiceDetails.ps1
- GetProcessAndServiceDetails.vbs
- GetProcessDetails.vbs
- GetServiceDetails.vbs
- MessageBox.bat
- MessageBox.vbs
- ADDMForWindows.ps1
- GetADInventoryDetails.vbs
- Deleted
- GetCloudMetaData.vbs
- GetContainerVersion.ps1
- GetDirectorySize.vbs
- GetFirewallProfile.vbs
- GetProcessDetails.ps1
- GetProcessDetails.vbs
- GetWMIQuery.ps1
- GetHyperv.ps1
- GetHyperv.vbs
- GetHypervDiscovery.ps1
- HypervVMActions.ps1
- GetHypervVMDiscovery.ps1
- HypervVMUpdateActions.ps1
- GetiisExportConfig.ps1
- GetLogicalProcessors.vbs
- GetLogonDetails.vbs
- makelink.vbs
- GetNetworkAdapter.vbs
- NLBScript.ps1
- NTPOffsetCheck.ps1
- CheckPendingUpdate.ps1
- PerfmonWMI.ps1
- PermissionCheck.ps1
- Agentquitprocess.vbs
- GetServerInventory.ps1
- GetServerParams.ps1
- ServiceAndProcessDiscovery.ps1
- ServiceAndProcessDiscovery.vbs
- SQLCluster.ps1
- GetSQLDBDiscovery.ps1
- StopCommunicationExtention.vbs
- GetSwapMemory.vbs
- GetTraceRoute.vbs
- wincluster_config.vbs
- GetWindowsBackup.ps1
- WindowsBackupCopies.ps1
- WindowsBackupDiscovery.ps1
- WindowsPendingUpdate.ps1
- GetWindowsUpdateHistory.ps1
- searchstring.vbs
- ServerMetrics.vbs
- Sharepoint.ps1
- sharePointServerDetails.ps1
- SkypeforBusinessDiscovery.ps1
- SkypeforBusinessServices.ps1
- topprocess.vbs
- SharepointDiscovery.ps1
- AppMonitoringConfig.ps1
Related Articles
How to uninstall the Site24x7 Windows Server Monitoring Agent
Method 1: To uninstall the Site24x7 Windows Server Monitoring Agent, click the link below: https://staticdownloads.site24x7.com/server/Site24x7WindowsAgentUninstall.zip Unzip and execute the Uninstall.bat file in the Command Prompt as an ...
How to view perfmon counters in Windows?
To monitor specific Windows performance (perfmon) counters with Site24x7's plugin integration, you need to get the names of the performance counters from the Windows Performance Monitor on your server. Follow the steps below to get the names of the ...
Troubleshooting false positive alerts in monitoring
Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...
How does Site24x7 always ensure the availability of its location agents during monitoring?
Site24x7 uses a preferred location recheck logic in the back-end to ensure the availability of all monitoring locations. This logic is only applied when you've disabled the option "Restrict monitoring within selected locations" in the Add or Edit ...
No data for service and process in Windows server monitor
If you see "No Data" for process and service metrics (such as CPU or memory usage of monitored services) in the Site24x7 Windows server monitor user interface, follow the troubleshooting steps below. Run PowerShell Commands Open PowerShell as ...