Domain Admin is not an issue, it is tied to specific mailboxes.  
RpcClientAccessServer was blank for two mailbox databases, the DA database was 
correctly set.  They are now all correctly set but that has not cleared the 
issue.



________________________________
From: [email protected] [[email protected]] on behalf 
of Kennedy, Jim [[email protected]]
Sent: Friday, March 06, 2015 7:18 PM
To: [email protected]
Subject: [NTSysADM] RE: OT Exchange issues.


Delete the Outlook profile and create a new one and all is well. Need to figure 
a better way, but it's a start.



________________________________
From: [email protected] [[email protected]] on behalf 
of Kennedy, Jim [[email protected]]
Sent: Friday, March 06, 2015 7:13 PM
To: [email protected]
Subject: [NTSysADM] OT Exchange issues.


Exchange list is really quiet, struggling with an issue here. Sorry.



I rolled up a new Exchange 2010 CAS/Hub and decommissioned the old one. 
Transferred all the URL's, and swapped IP's.  Internal and external flow is 
great, OWA is fine, external OWA and Active Sync is fine. Internal existing 
Outlook users are broke.  A regular user cannot find the new server when they 
start up, and domain admin with an email box can.



Feels like permissions on Autodiscover.xml or auth on Autodiscover but I have 
check that a million times.

Reply via email to