Last post Jun 17, 2009 11:28 AM by DmitriG
Jun 16, 2009 01:04 PM|appxjohnny|LINK
I have a consolidated HMC environment and I am trying to setup a BES server to connect. Have gone through all the Rimm instructions and have also checked every forum post I could find for Integrating this into a HMC setup. I have logged in with the BESadmin
account via OWA and have sent and recieved e-mail but through the BES install I still get a name cannot be resolved issue. I know it is permissions based with the BESadmin account as I can install under admin and I do not recieve the error. Any assistance
would be much appreciated.
Jun 16, 2009 04:04 PM|DGaikovoi|LINK
Check if your BESadmin account is listed in Default Global Address List. Check value(s) of the showInAddressList attribute for this user object using ADSIEdit.msc
Jun 16, 2009 04:31 PM|appxjohnny|LINK
Checked in adsi edit under the account and the show in address is correctly in.
CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=hosted,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=net
However interesting enough when I log in as besadmin i can only see the AL of one of the hosted domains and not the addresses of all the other hosted domains. So for example I log into OWA as besadmin and hit send and to. I change to all addresses and I
can see domain xx.com int the listing but non-of the other hosted domains.
Thank you for your reply.
Jun 16, 2009 04:46 PM|DmitriG|LINK
1. OWA doesn't use AL/GAL, it uses direct LDAP search in AD starting from container specified in msExchQueryBaseDN attribute for logged on account.
2. You have to use Outlook to test your Besadmin account. BES uses MAPI to connect to Exchange servers, if it can't create MAPI profile for BESadmin user it wouldn't work.
Use ADSIEdit to check if BESadmin has read access to "CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=hosted,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=net "
Jun 16, 2009 04:57 PM|appxjohnny|LINK
besadmin has both read and open rights here under adsi configuration.
Jun 17, 2009 11:28 AM|DmitriG|LINK
Try to logon as BESAdmin and user ADSIEdit to browes to
1. CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=hosted,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=net
2. to BesAdmin account itself.