Add a Windows Monitor
Monitor your Windows server and measure 50+ critical metrics like CPU, memory, disk utilization, processes and network traffic - all from a unified dashboard. Site24x7 uses the server monitoring agent to collect the performance data from your servers.
Supported Versions: 2008, 2008 R2, 2012, 2012 R2, 2016, Windows 7 and above, Windows 2019.
- Add a Windows monitor
- Edit/modify existing Windows monitors
- Bulk installation methods
- Microsoft Windows applications
- Associate configuration profiles during agent installation
- Security
Other supported features:
- Windows plugins
- Resource check profiles - Monitor files, directories, event logs
- IT automation
- Configuration rules
- Access tray icon
- Troubleshooting tips
Add a Windows Monitor
- Log in to Site24x7 and go to Server > Server Monitor > Servers (+) > Windows.
- Click on Download Site24x7 Windows Server Agent. Double-click on the .msi file. Click Next
- Enter the Device Key in the field provided. This is found in the Add Windows Monitor page in the web client.
- If proxy configuration is needed to access our domain, check the Enable Proxy option. Enter the server name, port number, user name, and password.
- Select an installation folder where you want to place the agent. Ensure the folder has Read and Write permission. In case you have more than one server, choose to bulk install while installing the agent.
- Know the services installed by the Windows server monitoring agent
- Make sure you exclude the complete Site24x7 installation directory (C:\Program Files (x86)\Site24x7) and agent processes (MEAgentHelper.exe, MonitoringAgent.exe, Site24x7WindowsAgentTrayIcon.exe, Site24x7PluginAgent.exe (if present)) from your AntiVirus scanning. Read more.
Once the agent is successfully installed, you can view the monitor under Server > Server Monitor > Servers. Once the agent is installed, a Tray Icon will appear in the Quick Launch Bar or listed under Start > All Programs > Site24x7 Windows Monitor > Tray Icon. If you have Microsoft applications like SQL, IIS, and Exchange running in your environment, the agent will auto-discover and add them for monitoring.
Edit/Modify Existing Windows Monitors
- Log in to Site24x7 and go to Server > Server Monitor > Servers > click on the Windows server monitor you wish to edit.
- Beside the display name, hover on the hamburger icon and click Edit.
- Edit and change the display name, monitor group, dependency on monitor, threshold and availaibility profile, notification profile, user groups, tags, resource check profiles and more.
The Host Name, IP address and Associated Configuration Template are also listed. These fields cannot be edited.
- Set the Poll Interval i.e. select the frequency for data collection. You can choose from a range of 1 min, 5 min, 10 mins, 15 mins, 30 mins, 1 hour, 3 hours, 6 hours, 12 hours, and one day. Read on to find out how to edit the frequency interval.
- Use the toggle button to enable or disable Event Log Monitoring.
- Integrate new or remove existing Third Party Integrations from Site24x7 alarms.
- Save your changes.
Bulk Installation Methods
- Remote Commands
- Active Directory
- Custom scripts
- During agent installation
- PowerShell DSC
- Via Google Cloud Platform (GCP)
- SaltStack
- Add as a VM extension in Azure
- Via System Center Configuration Manager (SCCM)
- Via ManageEngine Desktop Central
Resource Check Profile
Resource check profiles can be used to monitor internal resources like files, directories and event logs. The resources to be monitored should be added as checks to a resource check profile and this profile can be associated to any number of server monitors. You can also edit or delete a resource check profile.
IT Automation
Bring in an automated workflow and save time and reduce manual intervention. Learn more about the automation tools we have and how the automation process works.
Configuration Rules
Use Configuration Rules to create better pre-defined actions and automate the automate the configuration settings of your monitoring resources. Learn more.
Windows Plugins
Use our ready-to-install plugin integrations or write your own plugin using DLL, Batch, Powershell, and VB scripts. Set thresholds to individual attributes and choose to get alerted if the set values exceed.
Microsoft Windows Applications
Once the Windows agent is installed, the following applications will be auto-discovered and monitored:
Application | Supported Versions |
Exchange | 2007, 2010, 2013, & 2016 |
IIS | 7.0 and above |
SQL | 2008 and above |
BizTalk | 2006 and above |
SharePoint | 2007, 2010, 2013, & 2016 |
Active Directory | 31 and above |
Failover Cluster | 2008 and above |
Hyper-V | 2008 and above |
Windows Backup | Windows 2008 R2, Windows 2012, Windows 2012 R2, Windows 2016 |
Windows Updates | Windows server 2012 and above; Windows 8 and above |
Tip: You can also monitor your stand-alone Windows desktop applications developed in the .NET platform. Learn more.
Access Tray Icon
You can access the tray icon from the quick launch bar.
Important options available in the tray icon are:
- View Agent Logs to check on error codes, data collection metrics etc.
- Check Site24x7 Connectivity- To check if all the three domains are reachable. If connectivity is not available, provide access to the below domains and ports for the communication between the monitoring agent and the Site24x7 server.
- https://dms.zoho.com - Port 443
- https://plus.site24x7.com - Port 443
- https://plus2.site24x7.com - Port 443
- Proxy Configuration
- View Agent Details
- Start, Stop, and Restart Agent
Associate Configuration Profiles during Agent Installation
You can associate configuration profiles (like threshold, resource, notification profiles and group/display name) during the installation of the Windows agent itself. Learn more to know how to set this up with a use case.
Security
The Windows server monitoring agent runs as a SYSTEM role, and consists of four major services:
- Site24x7 Windows Agent
- Site24x7 Agent Helper
- Site24x7 APP Monitoring Agent
- Site24x7 Plugin Agent
In addition to the above four, there is the Tray Icon (running as a process) and the Agent Logs ({installation directory}> Site24x7 > WinAgent > Monitoring > Logs). The agent is a native C/C++ executable file, run as either a Site24x7 Windows Agent service or a MonitoringAgent.exe process.
Collection of performance data:
The agent collects data using WMI queries, performance counters and few built-in APIs. The performance data and the agent's device key (for authorization purposes) are stored in the <installation dir>\monitoring\conf directory and then sent to the Site24x7 Data Centers, based on your poll setting. Configuration data including the WMI queries, performance counters, proxy details etc. are stored in a SQLite DB and in the System Registry (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ManageEngine).
Agent upgrade process:
All agent upgrades are saved to the %temp% directory. After getting an upgrade request by the agent, the agent downloads the Site24x7 Windows Agent Upgrader. After download, the agent will check for checksum and verify the digital signature. After verification, the Site24x7 Windows Agent Upgrader will start and download the Site24x7 Windows Agent MSI file. There will again be a checksum and digital signature verification by the agent for the MSI file. Once that is successfully done, the upgrade process will be initiated.
Apart from the above mentioned file locations, Site24x7 does not store any information.
Microsoft Applications Monitoring:
Once the Windows agent is installed, Microsoft applications including SQL, IIS, Exchange, BizTalk, Active Directory, Failover Clusters, SharePoint, Windows Backup servers, Windows Updates, and Hyper-V will be auto-discovered and added for monitoring. In case you wish to disable this setting, you can do it in the Settings (Admin > Server Monitor > Settings) page. Learn more.
Troubleshooting Tips
- Error while installing the Windows Server Monitoring agent
- Troubleshooting steps if the Windows server monitoring agent is using high amount of CPU/memory
- Troubleshooting tips for Quota violation and WMI error while running WMI queries and scripts
- What TLS versions are supported by the Windows agent?
- What is the level of access the installed Windows server monitoring agent has towards the customer's environment?
- What will happen if I delete a Windows server monitor from the client and try to add it again?
- Required system settings for successful upgrade of Windows Server Monitoring agent
- Error message "Invalid WMI class" on computers running on Windows 7 or Windows server 2008 R2
- Timeout error or unable to start a service on a Windows server
- Why are the Start, Stop, and Restart options in my Tray Icon disabled?
- Monitor a specific Windows service using Server Monitoring
For more troubleshooting help, refer here.
Related Articles
- Other OS platforms supported: Linux | FreeBSD | OS X
- Server performance metrics
- Server monitoring architecture