Unsolved
This post is more than 5 years old
3 Posts
0
2482
May 1st, 2013 22:00
NMM 2.4.1.92 Wants Send-as and Recieve-as to open RDB
After creating a RDB and restoring a database to it, trying to open it from NMM comes up with the following error.
Permission Check
Send-as and Receive-as permissions are not set on the host wol-mbx-1. Please refer to the help file for prerequisites for Exchange 2010 recovery. RDB browsing and recovery is disabled.
I can confirm the two servers in this DAG have the required permissions by running the included powershell script:
get-ExchangeServer wol-mbx-1 | add-adpermission -user EMCBackup -accessrights ExtendedRight -extendedrights Send-As, Receive-As, ms-Exch-Store-Admin
with the result:
WARNING: The appropriate access control entry is already present on the object "CN=WOL-MBX-1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=GBST,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=gbst,DC=net" for account "GBST\emcbackup".
WARNING: The appropriate access control entry is already present on the object "CN=WOL-MBX-1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=GBST,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=gbst,DC=net" for account "GBST\emcbackup".
WARNING: The appropriate access control entry is already present on the object "CN=WOL-MBX-1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=GBST,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=gbst,DC=net" for account "GBST\emcbackup".
Identity User Deny Inherited
-------- ---- ---- ---------
WOL-MBX-1 GBST\emcbackup False False
WOL-MBX-1 GBST\emcbackup False False
WOL-MBX-1 GBST\emcbackup False False
Where should I start looking as to why NMM doesn't have the required permissions?
I've been through the Install and Application documents, have run the program as administrator under different accounts too.


CarlosRojas
1.7K Posts
0
May 1st, 2013 23:00
Hello Rohan_g,
First I would run NMM Config Checker and find out if there is any alert/error in the pre-requisites.
If NMM Config Checker comes up clean then ensure you have a Mailbox created and active (after creating it please send any email from it) and then try again.
Also check the Exchange event logs in case there is any other permission no set for that user.
You can use Microsoft's tool MFCMapi to verify the permissions for that user.
For more information on how to use MFCMapi please refer to the link below:
How to installing it without having Outlook installed on the Exchange server itself:
How to Use MFCMapi in Exchange 2010 Server itself - TechNet Articles - United States (English) - TechNet Wiki
How to use it:
Microsoft Exchange Server MAPI Editor
How to use the Mfcmapi.exe utility to view and work with messages in the SMTP TempTables in Exchange 2000 Server and in …
There is plenty of information about this tool in the web.
Thank you,
Carlos
Rohan_G
3 Posts
0
May 2nd, 2013 18:00
Do you need to make NMM aware of the server with the CAS role somehow or will just providing the mailbox server details be enough.
Looking through MFCMapi, I connect as "EMCBackup" account which has its own mailbox, I guess i'm trying to work out if it has permissions across exchange (including the RDB).
If I navigate to "Mailbox - EMC Backup" then right click the root folder, view table, ACL Table I see only Default & Anonymous so I'm guessing this isn't the location I'm meant to be looking for permissions.
Can you confirm where one would find out exchange permissions when looking at a single mailbox in MFCMapi?
Thanks again for you help,
Rohan
Rohan_G
3 Posts
0
May 2nd, 2013 22:00
Looks like a re-install has fixed everything somehow.
CarlosRojas
1.7K Posts
0
May 3rd, 2013 02:00
Hi Rohan_g,
I guess that the user used for the first installation didn't have the right permissions?
Next time just check the config checker, and find out the details for the user, not only the send as-receive as, but also the groups that user is member of.
You can run on the Exchange server the following command also and see if there is enough details in the output:
whomi /all
Thank you,
Carlos