dannymyung
asked on
OOOA Assistant Issues with SBS 2011
There is a 2011 SBS server that is running Exchange and SQL. This issue is a new issue and everything used to work fine 2 months ago. When a local domain workstation user opens their Outlook 2007 and clicks Tools > Out of Office Assistant they get the following error: "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later."
When the user logs in with OWA and goes to Automatic Replies, they check the box to "Send automatic replies" then click Save at the bottom, then this message pops up: "Sorry! We're having trouble processing your request right now. Please try again in a few minutes."
How can I fix this issue? I've checked all services on the exchange management console and everything appears to be enabled/running. The user I'm trying to do this with is also in the Domain Admins group in AD. It is to my knowledge (not first hand experience) that all users, even with Outlook 2010, have the same issue.
When the user logs in with OWA and goes to Automatic Replies, they check the box to "Send automatic replies" then click Save at the bottom, then this message pops up: "Sorry! We're having trouble processing your request right now. Please try again in a few minutes."
How can I fix this issue? I've checked all services on the exchange management console and everything appears to be enabled/running. The user I'm trying to do this with is also in the Domain Admins group in AD. It is to my knowledge (not first hand experience) that all users, even with Outlook 2010, have the same issue.
ASKER
Is there a way I do the Test Email AutoConfiguration from OWA or the server or should I only do it from a local workstation?
Use the cmdlet
test-OutlookWebServices -identity: user@domain.com | FL
Regards,
Exchange_Geek
test-OutlookWebServices -identity: user@domain.com | FL
Regards,
Exchange_Geek
ASKER
Please see attached screenshots
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for your help. This is a new customer and someone else set up the server. Can you point me in the right direction as to updating the certificate?
I'll have to look into the records for you but I don't think there is anything currently set up for "autodiscover.domain.com" -- it's funny though, the customer says that a few months ago everything was working fine.
The internal and external domains are the same.
I'll have to look into the records for you but I don't think there is anything currently set up for "autodiscover.domain.com" -- it's funny though, the customer says that a few months ago everything was working fine.
The internal and external domains are the same.
LOL, every customer says so.
Here are some quick tips.
Exchange has certain URL that needs to be in-place, we can check them quickly
Get-ClientAccessServer | FT Identity,AutodiscoverServi ceInternal Uri
Get-WebServicesVirtualDire ctory | FT Identity,InternalURL
Set-OWAVirtualDirectory FT Identity,InternalURL,Exter nalURL
Get-OABVirtualDirectory | FT Identity,InternalURL
Get-ActiveSyncVirtualDirec tory | FT Identity,InternalURL
Set-OutlookAnywhere -identity "CAS Server Name\RPC (Default Web Site)" |FT Identity,External*
Next, check the certificate of you're Exchange Server - check the Subject Alternate Name
Next, ensure that you've got a SRV Record pointing to your CAS Server internally
_autodiscover._tcp.domain. com --> CAS.domain.com
AND A SRV Record externally pointing to your webmail address.
That's it my friend.
Regards,
Exchange_Geek
Here are some quick tips.
Exchange has certain URL that needs to be in-place, we can check them quickly
Get-ClientAccessServer | FT Identity,AutodiscoverServi
Get-WebServicesVirtualDire
Set-OWAVirtualDirectory FT Identity,InternalURL,Exter
Get-OABVirtualDirectory | FT Identity,InternalURL
Get-ActiveSyncVirtualDirec
Set-OutlookAnywhere -identity "CAS Server Name\RPC (Default Web Site)" |FT Identity,External*
Next, check the certificate of you're Exchange Server - check the Subject Alternate Name
Next, ensure that you've got a SRV Record pointing to your CAS Server internally
_autodiscover._tcp.domain.
AND A SRV Record externally pointing to your webmail address.
That's it my friend.
Regards,
Exchange_Geek
ASKER
I added a SRV record in the server's DNS manager under the "remote.domainname.com" Forward Lookup Zone as "_autodiscover._tcp.remote .domainnam e.com" with host of "remote.domainname.com" which is the OWA login website -- I put it under port 443, weight 100, and priority as 0 but then go to testexchangeconnectivity and it still fails...
I'm contacting GoDaddy tomorrow to add a line in the Subject Alternative Name for the Certificate they have in addition to the existing entries of:
{existing} DNS Name=remote.domainname.com
{existing} DNS Name=www.remote.domainname.com
{adding this line next} DNS Name:SBS2011.domainname.co m
Am I going in the right direction?
I'm contacting GoDaddy tomorrow to add a line in the Subject Alternative Name for the Certificate they have in addition to the existing entries of:
{existing} DNS Name=remote.domainname.com
{existing} DNS Name=www.remote.domainname.com
{adding this line next} DNS Name:SBS2011.domainname.co
Am I going in the right direction?
Select Test Email AutoConfiguration
Uncheck both checkboxes for guessmart and hit enter.
Once done, provide us the screenshot of the entire results (with the entire scroll bar)
Regards,
Exchange_Geek