Dependency field removal and prevent auto update

Dependency field removal and prevent auto update

The dependency field of the devices can be entered manually or it can update itself when a layer 2 map is created.
If you remove the dependency manually, it will be populated again since by default the layer 2 map will have a auto-discovery interval.

To stop the auto update/population of dependency field -
Connect to the DB -

Execute -
update layer2configuration set autodependency='false';

This will prevent the auto-updation of the dependency field.

        New to ADManager Plus?

          New to ADSelfService Plus?

            • Related Articles

            • Daylight Saving Time(DST) not being updated in the OpManager

              Issue: Daylight Saving Time(DST) difference is not reflected in OpManager. The Time that is being shown in "About" tab in OpManager UI will have 1 hour time difference with respect to the actual time. Reason: Daylight Saving Time(DST) changes that ...
            • Resolving Pgsql Startup due to DNS issue

              1. Stop the OpManager service and wait till all java/postgres processes are closed. (If postgres process doesn't exit for a long time, do not kill the process, instead, run StopPgsql.bat from cmd and wait for the process to terminate.)  2. Navigate ...
            • Configuring a non-admin user for WMI monitoring (domain level)

              For non-admin users to perform WMI monitoring in OpManager, the user profiles need to be configured accordingly in your network. This can be done: On a device level (configuring individual devices) - Link to KB On a domain level (configuring the ...
            • Admin Password reset in OpM 12

              For users that are authenticated with Active Directory Domain authentication, you can reset the password of an AD user by changing the AD password. The same is applicable for Radius Authenticated users. Local Authenticated users can follow one of the ...
            • Find the missing VMs and Hosts - HyperV and Xen

              After the HyperV discovery if the VMs are missing, query the below table and check select * from hyperventitymomap where entity_type = 'HyperV-VM'; select * from hyperventitymomap where entity_type = 'HyperV-Host'; When the MOID is -4, check whether ...