none
Exchange 2007 - Out of Office not working RRS feed

  • Question

  • Hi Support,

    My organization Out of Officce is not working.

    I have already tried removing and recreating the WebServicesVirtualDirectory.

    I have also enter the below command, but issue still persists.

    "Set-WebServicesVirtualDirectory -identity "CAS01\EWS (Default Web Site)" -externalurl https://mail.contoso.com/EWS/Exchange.asmx -BasicAuthentication:$True"

    I will send you my remote connectivity analyzer log after receiving your email.

    Hope to hear from you soon.

    Best Regards

    Bryan Teo

    Monday, April 23, 2012 1:15 AM

Answers

  • Hi Rich,

    It does not work internally also.

    How to I check (Get-RemoteDomain default).AllowedOOFType ??

    Maybe it will be good if you can list an example.

    Best Regards

    Bryan Teo

    I'd suggest you try in OWA to see is this works. It would help us verify if the availability service is working or not.

    If the issue continues in OWA, verify the mailbox assistant service on the CAS server and make sure it is starting up. Besides, create a new user mailbox and test again.

    Let me know if you have any other question.


    Fiona Liao

    TechNet Community Support

    Tuesday, April 24, 2012 6:23 AM
    Moderator

All replies

  • Please explain by "not working"?  What happens when you try to change it?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Monday, April 23, 2012 1:45 AM
    Moderator
  • Hi Ed,

    Users were able to set Out Of Office but when external users sent email to the user, they did not receive the Out Of Office message.

    Best Regards

    Bryan Teo 

    Monday, April 23, 2012 1:59 AM
  • On Mon, 23 Apr 2012 01:59:28 +0000, Bryan Teo wrote:
     
    >Users were able to set Out Of Office but when external users sent email to the user, they did not receive the Out Of Office message.
     
    Does it work properly for internal users that send e-mail to the user?
     
    Assuming it works (or doesn't work) the same way regardless of the
    external sender's domain, check this:
     
    (Get-RemoteDomain default).AllowedOOFType
     
    Is it set to "External"?
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Monday, April 23, 2012 3:18 AM
  • Hi Rich,

    It does not work internally also.

    How to I check (Get-RemoteDomain default).AllowedOOFType ??

    Maybe it will be good if you can list an example.

    Best Regards

    Bryan Teo

    Monday, April 23, 2012 4:18 AM
  • Type that in the Exchange Management Shell.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

    Monday, April 23, 2012 4:39 AM
    Moderator
  • Hi,

    It is set to External.

    So what's next ?

    Best Regards

    Bryan Teo

    Monday, April 23, 2012 4:42 AM
  • On Mon, 23 Apr 2012 04:42:57 +0000, Bryan Teo wrote:
     
    >It is set to External.
    >
    >So what's next ?
     
    Well, if it's not working even for people on your LAN sending to other
    people on your LAN then it's not anything to do with the settings for
    remote domains.
     
    The first thing I'd suggest is running the Exchange Best Practices
    Analyzer (found in the "Toolbox" of the EMC) and addressing any
    problems it points out. The next thing to do is see if
    https://testexchangeconnectivity.com works (particularly the
    "Microsoft Exchange Web Services Connectivity Tests" for OOF). This
    may also provide some more information:
    "Test-WebServicesConnectivity". Having more information about the
    nature of the problem is always a good thing.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Monday, April 23, 2012 9:43 PM
  • Hi Rich,

    It does not work internally also.

    How to I check (Get-RemoteDomain default).AllowedOOFType ??

    Maybe it will be good if you can list an example.

    Best Regards

    Bryan Teo

    I'd suggest you try in OWA to see is this works. It would help us verify if the availability service is working or not.

    If the issue continues in OWA, verify the mailbox assistant service on the CAS server and make sure it is starting up. Besides, create a new user mailbox and test again.

    Let me know if you have any other question.


    Fiona Liao

    TechNet Community Support

    Tuesday, April 24, 2012 6:23 AM
    Moderator