Execute Program action - Enterprise Admin server behavior & Known limitation

Execute Program action - Enterprise Admin server behavior & Known limitation

Behavior in Enterprise Admin server

In case of Enterprise Admin users, following is the behavior of Execute Program action:
  1. All Host in the selected Monitor Group option is not supported
  2. Auto Select Host option is partially supported. Since the host details will not sync to the Admin Server we will not support the monitors which are added through Managed Servers. To make the Auto Select Host work in Admin Server, host details should be added manually in Admin Server through Execute Program Action, File / Directory Monitor and Script Monitor

Known Limitation

Following is the known limitation of Execute Program action: 
  • Updating the Credentials from Credentials Manager will not reflect in the existing host which was added using that particular Credentials Manager credentials. 

          • Related Articles

          • Execute Program Action - BlackListCommands

            There are certain commands which are vulnerable to security threats in both Windows and Linux operating systems such as del and deltree. Such commands can be restricted for execution from Execute Program action. By default, we are restricting the ...
          • Service Now Event Integration using Webhook / Rest API Action

            Steps to perform in Service Now 1) Login to your ServiceNow Instance(dev*****133.service-now.com) 2) Search for the Rest API Explorer and open it 3) In the Rest API Explorer page choose the Namespace and API Name with the proper API version. For ...
          • Tachometers not being displayed on Admin server console in Enterprise Edition

            Problem: Tachometers are not displayed on the Admin server console in Enterprise Edition. Solution: 1. Login to Admin Server UI. 2. Navigate to Admin -> Global Settings -> Enterprise Edition Settings. 3. Kindly enable the Proxy Managed Server request ...
          • Critical\Warning alarm was raised, but action wasn't triggered

            1.) Ensure that actions have been associated for the attribute that generated the alarm. For example, if the CPU utilisation of the server exceeded the permissible levels and generated the alarm, navigate to Monitor page->Configure Alarm and ensure ...
          • Convert Professional edition to Enterprise edition

            Install an "Admin Server" with the same build number as that of your professional edition. (You can find the build number in Settings -> Tools -> Support -> Build number)  Archive link: http://archives.manageengine.com/applications_manager/ After ...