ad_server and ad_response probes will not start on a new Active Directory AD server
search cancel

ad_server and ad_response probes will not start on a new Active Directory AD server

book

Article ID: 263694

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

ad_response/ad_server probes do not start up on a new configured Active Directory server.

We currently show that .NET version 4.7.02053 is installed. We attempted to install a stand-alone version of 4.5 and cannot, due to 4.7 being a higher version and backwards-compatible.

Should these probes work with .NET version 4.7?

Environment

  • Release: DX UIM 20.4
  • ad_server 2.04 or higher
  • ad_response 1.80 or higher

Cause

  • .NET version requirement

Resolution

Here are the prereqs:

ad_server
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/servers-and-application-infrastructure/ad-server-active-directory-server-monitoring/ad-server-active-directory-server-monitoring-release-notes.html 

***For ad_server 2.04 or later, installing .NET Framework version 4.8 is a prerequisite***

ad_response
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/systems-and-service-response/ad-response-active-directory-response-monitoring/ad-response-active-directory-response-monitoring-release-notes.html 

**For ad_response 1.80 or later, installing .NET Framework version 4.8 is a prerequisite.***

One way of understanding what a probe requires is to run the probe manually from the Windows command line, for example:

You can click Yes to install .NET Framework 4.8

Or download and install .NET Framework version 4.8 manually from:
https://go.microsoft.com/fwlink/?LinkId=2085155

ad_response and ad_server probes were working as expected after updating .NET to v4.8.

Additional Information