1.
Domain Controller Monitoring Setup
The following steps are for setting up monitoring on one Windows Server at a time.
Click here for Bulk Windows Server Setup
> Click here to log into Monro Cloud Monitoring.
> Log in with either your mobile number or email address.
2.
Windows Server Monitoring Setup
> Open your email and search for the original email your received when you signed up.
> Download the first file - Windows Agent.
> Download the second file - Custom Agent
3.
Domain Controller Monitoring Setup
> Copy the 2 files onto your Windows Domain Controller, place them anywhere on the C drive.
> Make sure both files are in the same directory.
4.
Domain Controller Monitoring Setup
> Double click the file called ID_Number-Monitoring_Install_Tool.cmd
> If prompted for administrator permissions, allow the installation to continue.
5.
Domain Controller Monitoring Setup
> Go back to your Monro Cloud Monitoring.
> Select Data Collection.
> Select Hosts.
> You should now see your new Windows Domain Controller being monitored.
6.
Domain Controller Monitoring Setup
We now need to configure the items to detect abnormal behavior with Active Directory, for situations such as domain controllers unable
to replicate or a DNS service failing to start.
> Select Data Collection.
> Select Hosts.
> Click the Domain Controller you want to manage - in this example DC4.
7.
Domain Controller Monitoring Setup
> Under Templates click the Select button.
> From the Template Group select Windows Servers.
> Check AD DS Health and Performance.
> Check AD Replication.
> Click Select and then Update to complete the setup.
8.
Domain Controller Monitoring Setup - Testing
These tests were performed in a Lab environment and should NOT be used in production.
The following tests the AD Replication template.
> By using the repadmin /options command the tests broke replication between DC1 to DC4.
> Once the next AD sync it attempted, Monro Cloud will detect the replication errors.
> These will display in the central dashboard as seen below.
> The time to detect the replication issues is approximately every 5 - 10 minutes.
9.
Domain Controller Monitoring Setup - Testing
These tests were performed in a Lab environment and should NOT be used in production.
The following tests the AD DS Health and Performance template, specifically the time service.
> By using the w32tm stop command, the time service (w32tm) was stopped on DC4.
> Time is critical for Active Directory to work, therefore if the service stops - you need to know!
> The screenshots below show the time service stopped and the monitoring detecting it soon after.
> The time to detect tine issues (and other AD services) is approximately every 5 - 10 minutes.
9.
Domain Controller Monitoring Setup - Testing
These tests were performed in a Lab environment and should NOT be used in production.
The following tests the AD DS Health and Performance template, specifically the DNS service.
> By using the Services tool, the DNS Server service was stopped on DC4.
> DNS is critical for Active Directory especially when using AD Integrated zones.
> The screenshots below show the DNS Server service stopped and the monitoring detecting it soon after.
> The time to detect tine issues (and other AD services) is approximately every 5 - 10 minutes.
6.
Domain Controller Monitoring Setup - COMPLETE
These steps have been guides on how to use Monro Cloud Monitoring for your IT infrastructure.
Always take care when making changes production infrastructure and consult a professional if you require assistance.
> From the Monro Cloud dashboard, you will now be able to monitor domain controllers and Active Directory.
