Unable to Complete Install AppManager Agent Component Locally due to Lack of Communication to the AppManager Management Server (NETIQKB4485)

Unable to Add AppManager Management Server Name during Local Install of Agent Component
NetIQ AppManager Management Server Service Fails to Start
Error: Process Terminated Unexpectedly
Unable to Complete Install AppManager Agent Component Locally due to Lack of Communication to the AppManager Management Server
Discovery Jobs will Not Run Automatically
Error 1067

To use the Distributed COM Configuration Properties utility to configure DCOM permissions:

1. Go to Start | Run.
2. Type dcomcnfg and clickOK.
3. In the Distributed COM Configuration Properties window, select the Default Security tab.
4. Under Default Access Permissions, click Edit Default.
5. In the Registry Value Permissions window, click Add.
6. In the Add Users And Groups window, click Show Users.
7. Select the appropriate User and select Allow Access in the Type Of Access drop-down list.
8. Click OK. The User should now appear in the Registry Value Permissions window.
9. Click OK again.
10. Under Default Launch Permissions, click Edit Default.
11. In the Registry Value Permissions window, click Add.
12. In the Add Users And Groups window, click Show Users.
13. Select the appropriate User and select Allow Launch in the Type Of Access drop-down list.
14. Click OK. The User should now appear in the Registry Value Permissions window.
15. Click OK again.
16. Repeat Steps 4 through 15 for System and Interactive.

The account being used to LogOn As for the NetIQ AppManager Client Resource Monitor Service and/or the NetIQ AppManager Management Server Service does not have permission to access or launch DCOM objects on the target Server. This prevents the Service from starting and connectivity is not established between the Management Server and the Managed Client to complete the local install by automatically discovering the selected modules.

Formerly known as NETIQKB4485

This should be applied to the (explicit) User Account and both the System and Interactive (System and Interactive are part of the Local Server) for Access and Launch permissions.