For InTrust Connector installation and functioning, your environment must meet the following requirements:
To allow a user to configure InTrust Connector (apply filters to the alerts that should be forwarded, set up alert forwarding process, etc.), you must add the user's account to the InTrust OpsMgr Connector Admins local group. This group is automatically created on the computer where InTrust Connector is installed, and the group is granted the permissions described in the Connection to Alert Database and Operations Manager Server topic.
The following accounts are added to the InTrust OpsMgr Connector Admins group during installation:
|
Note: The InTrust OpsMgr Connector Admins group is not removed when you uninstall InTrust Connector; you need to remove it manually. |
The InTrust OpsMgr Connector Admins group is granted the following permissions:
|
Note: The Synchronize permission is not displayed in the standard Properties window. To show it, use the Subinacl.exe utility available from the Resource Kit. |
|
Note: When granting the necessary permissions manually, clear the Allow inheritable permissions from parents to propagate to this object check box. |
To connect to the InTrust Alert database, InTrust Connector can use either the ITConOpsMgrService account (supplied during the setup) or a specific different account (which you can supply using the Configuration Wizard). Whatever account is used, it should be assigned the following:
If specific Windows account will be used to access the Alert database (see the Configuring InTrust Connector for Operations Manager topic for details), then it also must be granted the Log on as a batch job right.
The account used for connecting to the Operations Manager server must be a member of the domain global group included in the Operations Manager Administrators role (this group is created during Operations Manager setup).
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center