NetIQ AppManager 7.0.x
How do I manually update the Exchange Profile and Exchange Mailbox alias for the Exchange Server?
How can I determine what name was set for the MAPImail account for the Exchange Server?
Any Exchange jobs that use a mailbox profile will fail with the following error: 'error message = no profile/mailbox = , mailbox = job 2076 error'.
To manually update the Exchange Profile and Exchange Mailbox alias for the Exchange Server, launch the AppManager Security Manager, then:
- In the left-most pane, select the Exchange Server that is getting errors when running Knowledge Scripts that require access to a mailbox profile.
- In the right-most pane, click the Exchange tab.
- Verify that the Profile field contains the name of the account for the MAPImail function on that Exchange Server.
- Verify that the 'Mailbox alias' field contains the alias name of the account for the MAPImail function on that Exchange server, which will typically be the same name as in Step 3.
One possible cause is that the Exchange Profile and Exchange Mailbox alias for the Exchange Server are not correct in AppManager Security Manager. These two entries are populated during discovery. If these fields contain incorrect information, you need to manually update them in AppManager Security Manager.
If you are unsure what name was set for the MAPImail account for the Exchange Server in question, open the following hive in the registry of that Exchange Server:
HKEY_LOCAL_MACHINE > Software > NetIQ > AppManager > 4.0 > NetIQMC
Then check the values of the following two keys:
- Exchange Profile
- Exchange Mailbox
These are the values at the time the Exchange Discovery knowledge script ran on that server. The values for the Exchange Profile and Exchange Mailbox registry keys are the values needed for Steps 3 and 4 above. If the values in these two registry keys do not match those of the Exchange Server in the NetIQ AppManager Security Manager , manually update the entries in the Security Manager to match the registry values of the Exchange Server in question.
If the registry values of the Exchange Server in question are incorrect or blank, re-run the Exchange Discovery on that server. DO NOTmanually change the values for these Exchange Server registry keys.