S.I.G.M.A. Network s.r.l. | Via Clelia, 60 – 00181 Roma | P.IVA/C.F. IT05255401001
Registro Imprese Roma – R.E.A. RM-870189 | Capitale sociale i.v. €10.200,00
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
How to monitoring Active Directory
How to Monitoring Microsoft Active Directory
Microsoft Active Directory is used to share user list, provide single sign on and other central features in large Microsoft based workstation and server networks. Active Directory is Microsoft’s implementation of existing business standards such as LDAP, Kerberos and DNS. The purpose of this article is describing how op5 Monitor can be used to monitor these core features of an Active Directory and make sure that notifications are sent about common errors.
To be able to complete this how-to you will need the following files:
The scripts are not officially supported by op5 Support, but we will help you as good as we can.
This will be done
The suggested configuration components for monitoring Active Directory are:
check_ad=cscript.exe //T:30 //NoLogo scripts\check_ad.vbs
check_ad_fsmo=cscript.exe //T:30 //NoLogo scripts\pluginscheck_ad_time.vbs” example.com “$ARG1$”
Add the required check-commands, if they don’t already exist in your configuration, add dem via: (‘Configure’ -> ‘Check Commands’ -> ‘New command’)
* Require changes to NSC.ini, see section below.
** This is just one example of performance counters you might want to monitor, for a full list we sugest you take a look at Microsoft own reference list.
Short list of counters we think is good to monitor:
Add the required services
Go to ‘Configure’ -> ‘Host:
‘ -> ‘Go’ -> ‘Services for host ‘ -> ‘Add new service’ -> ‘Go’
Add the following services (Arguments are just examples, you need to adjust them to suite your environment).
Use the “Test this service” botton for the services to see if they work. Once the are correct and working as they should you may add the services to all of your domain controllers with the clone-function.
Configuring the service group
Configuring a service group is not necessary for tde monitoring to work, but it will be easier to display tde current status on tde Active Directory – for instance for help desk staff.
From Configure, select Service Groups and add a new service group.
Enter a service name and a description (alias) tdat is suitable for your organization.
Hold down tde Control key and select tde services you wish to include – preferably tde services you added in tdis How-To, and some otder important services for tde domain controllers:
Move tde selected services to tde selected list.
Click on “Apply Changes” and tden “Save”.
Ciao mondo!20 Settembre 2022
Improving Your Technology13 Novembre 2019
Apply These 5 Secret Techniques13 Novembre 2019