ad_server alarms generate with unresolved variables: $fsmoName$ / $errors$ / $domain

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

ad_server probe 2.06 has some issues related to probe variables not resolved in alarms generated:

 

• MasterConsistency profiles and Gpupdate alarms generate with unresolved variable: eg.: $fsmoName$ / Gpupdate errors: $errors$

 

<message-2e4c5340-c08e-49f4-ae24-31a14abcb31b>
     name = OM_MasterConsistency
     text = The PDC and local DC do not agree on the owner of the FSMO: $fsmoName$
     subsystem = 2.1.2
     i18n_token = as#application.ad_server.provider_OM_MasterConsistency
  </message-2e4c5340-c08e-49f4-ae24-31a14abcb31b>

 

 

• The $domain variable is resolved only for the profile AD Trust. For other profiles it doesnn't resolve shiowing "$domain" in the alarm. 

Environment

• DX UIM 23.4.*
• ad_server 2.06

 

Cause

Probe Defect / Enhancements

Resolution

The ad_server 2.10 GA Version contains enhancements for the $domain variable for Master Consistency FSMONames variabled. 

The FSMOnames variables that were implemented are: 

$domain_naming$
$schema$
$rid$
$infra$

 

these are specifically enabled in the code to support each of the 4 Master Consistency Counters: 

 

 

Note: it is expected that $fsmoName$ is not resolved. Instead of $fsmoName$ use $domain_naming$, $schema$, $rid$, $infra$ respectively. 

Additional Information

Related KB: ad_server GroupPolicyCheck alarms does not resolve variable error (Gpupdate errors: )