Exch 2010 Out of Office issue - Outlook Client Only

OOF works in OWA, and it also works in Outlook 2011 on our Apple clients. It does not however, work in Outlook 2007 and 2010.
I've done quite a bit of troubleshooting on this issue already. All IIS permissions are correct, there are no IE proxies interfering, autodiscover is setup correctly and working as intended. (Initially, it was not and I assumed this was the issue. Now it
is and the issue continues. Confirmed both by https://www.testexchangeconnectivity.com & Test E-mail AutoConfiguration on our outlook clients)
I'm not sure what else I can do and I'm having trouble finding anymore information on this subject past those issues listed above. Any and all help would be greatly appreciated.
Thanks in advance!

This issue was resolved, forgot all about this thread but figured I'd update it for others if they have the same issue.
The mailbox databases were not pointed to OfflineAddressBook. 
We had to set all the mailbox databases to an Offline address book using following steps. After you run the below changes please run IISRESET command on the CAS server.
To associate the Offline Address Book with a particular mailbox store in Exchange 2007 or in Exchange Server 2010
      Start the Exchange Management Console.
      Expand Server Configuration(For me it was under Organization Configuration),
and then click Mailbox.
      In the details pane, click the Database Management tab.
      Under the appropriate storage group (for example,First Storage Group),
right-click Mailbox Database, and then click Properties.
      Click the Client Settings tab, and then clickBrowse next
to Offline address book.
      Click the appropriate offline address book, and then click OK two
times.
Offline address book is not associated with a particular mailbox store
Hope this helps!

Similar Messages

  • Setting Out Of Office from Outlook not working with exchange 2010

    Hi 
    We have an exchange 2010  server with 2 load balanced CAS server and Mailbox servers in a DAG.  We have a few domain
    names accepted (will call it firstdomain.com and seconddomain.com)  but only one is in certificate (firstdomain.com).
    The issue is - when user with default email @seconddomain.com try to set “Out Of Office” from outlook (2010 with all service
    packs and updates) he is getting “ Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later”  where
    setting it from webmail works fine and setting it from outlook for users with @firstdomain.com reply address works fine.
    we have both internal and external urls for all virtual directories set to external
    host address (https://mail.firstdomain.com
      etc). All the users are on intranet with local ip subnets (sites connected via vpns ), all the routing is in place and DNS points to correct ip addresses.
    Autodiscover works fine (tested in outlook ) and giving correct address for OOF link
    ( https://mail.firstdomain.com/ews/exchange.asmx)
    wich opens fine if entered into address bar in IE so its NOT AN AUTODISCOVER issue .
    I enabled  logging in outlook and thats what I am getting in there:
    We have an exchange 2010  server with 2 load balanced CAS server and Mailbox servers in a DAG.  We have a few domain
    name accepted (will call it firstdomain.com and seconddomain.com)  but only one is in certificate (firstdomain.com).
    The issue is - when user with default email @seconddomain.com try to set “Out Of Office” from outlook (2010 with all service
    packs and updates) he is getting “ Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later”  where
    setting it from webmail works fine and setting it from outlook for users with @firstdomain.com reply address works fine.
    we have both internal and external urls for all virtual directories set to external
    host address (https://mail.firstdomain.com
      etc). All the users are on intranet with local ip subnets (sites connected via vpns ), all the routing is in place and DNS points to correct ip addresses.
    Autodiscover works fine (tested in outlook ) and giving correct address for OOF link
    ( https://mail.firstdomain.com/ews/exchange.asmx)
    wich opens fine if entered into address bar in IE so its NOT AN AUTODISCOVER issue .
    I enabled  logging in outlook and thats what I am getting in there:
    1600       0x49763D20        02/02/15 16:50:44           
    +++++++++++++++++++++++++++++++
    1600       0x49763D20        02/02/15 16:50:44           
    OWINHTTP SEND HTTP REQUEST BEGIN
    1600       0x49763D20        02/02/15 16:50:44           
      Profile=Outlook
    1600       0x49763D20        02/02/15 16:50:44           
      [email protected]
    1600       0x49763D20        02/02/15 16:50:44           
      URL=https://mail.firstdomain.com/ews/exchange.asmx
    1600       0x49763D5F        02/02/15 16:50:45           
    GetLastError=0; httpStatus=401.
    1600       0x49763D5F        02/02/15 16:50:45           
    OWinHtpp disabled auth schemes:
    1600       0x49763D5F        02/02/15 16:50:45           
    <NONE>
    1600       0x49763D5F        02/02/15 16:50:45           
    OWinHtpp supported auth schemes:
    1600       0x49763D5F        02/02/15 16:50:45           
    Negotiate
    1600       0x49763D5F        02/02/15 16:50:45           
    NTLM
    1600       0x49763D5F        02/02/15 16:50:45           
    Basic
    1600       0x49763D5F        02/02/15 16:50:45           
    OWinHttp attempting Auto-Negotiate with Desktop Credentials.
    1600       0x49763D5F        02/02/15 16:50:45           
    OWinHttp USING pcreds->dwAuthScheme:
    1600       0x49763D5F        02/02/15 16:50:45           
    Negotiate
    1600       0x49763D9D       02/02/15 16:50:45           
    GetLastError=0; httpStatus=500.
    1600       0x49763DAD       02/02/15 16:50:45           
    OWINHTTP SEND HTTP REQUEST END
    1600       0x49763DAD       02/02/15 16:50:45           
    Last thing - we are using proxy server and with proxy off it works fine although all
    possible exchange server hosts/domains/ip addresses excluded from proxy.  
    Aside from obvious question - what can be wrong and what to test next, another question
    is - how can I check/monitor setting OOF on server side (log files etc)?
    Last thing - we are using proxy server and with proxy off it works fine although all
    possible exchange server hosts/domains/ip addresses excluded from proxy.  
    Aside from obvious question - what can be wrong and what to test next, another question
    is - how can I check/monitor setting OOF on server side (log files etc)?
    Thanks

    Hi,
    According to your description, I understand that Outlook client with second domain name cannot use OOF setting and get an error “Your Out of Office settings cannot be displayed, because the server is currently unavailable.”  However OWA works fine.
    If I misunderstand your concern, please do not hesitate to let me know.
    I want to double confirm whether all account or some special user experience this question.
    Would you please try to reconfigure Outlook profile in other Computer, Outlook version and return the results?
    If this issue only appeared on Outlook 2010, please refer to below link to troubleshooting:
    https://support.microsoft.com/kb/2596516?wa=wsignin1.0
    Please try to run ExBPA to test OOF to get more details about this question. Additional, I find a similar thread about your question, for your reference:
    https://social.technet.microsoft.com/Forums/exchange/en-US/81ebc1de-c899-4097-b224-a0e4b33e4162/users-cant-open-out-of-office-assistant
    Best Regards,
    Allen Wang

  • Exchange 2010 Out of Office Assistant not working?

    New server with a new Exchange 2010 install into an existing domain...
    When users on both the internal network and external network try to access the Out of Office Assistant they get an error message of: " Your Out of Office settings cannot be displayed, because the server is currently unavailable".
    I have done tons of research on WebServicesVirtualDirectory and AutodiscoverVirtualDirectory and set both internal and external URL's that work if you go to them in IE )internally and externally offsite).
    Here are the settings of Autodiscover and Webservices:
    [PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | Format-List
    RunspaceId : 86aaf7fc-ca19-45b2-87d1-45ec432a670d
    CertificateAuthentication :
    InternalNLBBypassUrl : https://MAILSERVER.domain_name.local/ews/exchange.asmx
    GzipLevel : High
    Name : EWS (Default Web Site)
    InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
    ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
    LiveIdSpNegoAuthentication : False
    WSSecurityAuthentication : True
    LiveIdBasicAuthentication : False
    BasicAuthentication : True
    DigestAuthentication : False
    WindowsAuthentication : True
    MetabasePath : IIS://MAILSERVER.domain_name.local/W3SVC/1/ROOT/EWS
    Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
    Server : MAILSERVER
    InternalUrl : https://MAILSERVER.domain_name.local/EWS/Exchange.asmx
    ExternalUrl : https://mail.domain_name.com/owa
    AdminDisplayName :
    ExchangeVersion : 0.10 (14.0.100.0)
    DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=MAILSERVER,CN=Servers,CN=Exchange Adm
    inistrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=M
    icrosoft Exchange,CN=Services,CN=Configuration,DC=domain_name,DC=local
    Identity : MAILSERVER\EWS (Default Web Site)
    Guid : 4639e4b9-9cf3-4f92-8940-f7c31e07cd47
    ObjectCategory : domain_name.local/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
    ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
    WhenChanged : 4/1/2010 2:47:37 PM
    WhenCreated : 3/11/2010 11:02:22 AM
    WhenChangedUTC : 4/1/2010 8:47:37 PM
    WhenCreatedUTC : 3/11/2010 6:02:22 PM
    OrganizationId :
    OriginatingServer : DOMAINCONTROLLER.domain_name.local
    IsValid : True
    [PS] C:\Windows\system32>AutodiscoverVirtualDirectory | Format-List
    RunspaceId : 86aaf7fc-ca19-45b2-87d1-45ec432a670d
    Name : Autodiscover (Default Web Site)
    InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
    ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
    LiveIdSpNegoAuthentication : False
    WSSecurityAuthentication : True
    LiveIdBasicAuthentication : False
    BasicAuthentication : True
    DigestAuthentication : False
    WindowsAuthentication : True
    MetabasePath : IIS://MAILSERVER.domain_name.local/W3SVC/1/ROOT/Autodiscover
    Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
    Server : MAILSERVER
    InternalUrl : https://MAILSERVER.domain_name.local/autodiscover/autodiscover.xml
    ExternalUrl : https://mail.domain_name.com/autodiscover/autodiscover.xml
    AdminDisplayName :
    ExchangeVersion : 0.10 (14.0.100.0)
    DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=MAILSERVER,CN=Servers,CN=Exc
    hange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organiza
    tion,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain_name,DC=loca
    l
    Identity : MAILSERVER\Autodiscover (Default Web Site)
    Guid : 7a234ea2-20fc-412b-bbf0-3ea5f965d8da
    ObjectCategory : domain_name.local/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
    ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
    WhenChanged : 4/1/2010 3:00:49 PM
    WhenCreated : 3/11/2010 11:02:07 AM
    WhenChangedUTC : 4/1/2010 9:00:49 PM
    WhenCreatedUTC : 3/11/2010 6:02:07 PM
    OrganizationId :
    OriginatingServer : DOMAINCONTROLLER.domain_name.local
    IsValid : True
    Test-OutlookWebServices comes up with errors. The Test E-mail AutoConfiguration within Outlook still appears to be looking for Autodiscover at different URLs...
    OOF within Outlook Web App functions.
    Any suggestions would be helpful!

    From your previous post, I understand that OOF doesn't work for both internal and external clients. Error message "Your Out of Office settings cannot be displayed, because the server is currently unavailable" was received from Outlook client side. Please correct me if I have any misunderstanding.
    Before we go any further, I would appreciate your help in clarifying the following questions:
    1. When did this issue begin to occur, since the installation of Exchange 2010?
    2. Can we access and configure OOF from OWA?
    As internal & external clients are using different methods/URL to access Autodiscover and EWS, which provided OOF service, I recommend we focus on the internal users first.
    To troubleshoot this issue, please install the hotfix mentioned in the following KB on the Exchange Client Access Server first:
    Outlook 2007 crashes or you cannot access OOF settings after you install a package that contains the .NET Framework 3.5 with SP1 and the .NET Framework 2.0 with SP2 on an Exchange 2007 Client Access server or on an Exchange 2010 Client Access server
    http://support.microsoft.com/kb/958934 
    After that, check if the issue remains. If there is still problem, please help me collect:
    1. Test E-mail AutoConfiguration from Outlook client
    1. Launch Outlook 2007 using a correct configured profile.
    2. Hold down the CTRL key on your keyboard and click the Outlook icon in the notification area of the Windows taskbar, also known as the notification area.
    3. In the menu that appears, click Test E-mail AutoConfiguration.
    4. Enter your E-mail Address and Password (if not logged into the domain) in the respective edit boxes.
    5. Choose the desired auto configuration methods with Use Autodiscover, clear other selection.
    6. Click Test.
    7. Please send me the screenshot of the result tab and log tab.
    2. Result files after running the following command on the Exchange 2007 server
    Get-ExchangeCertificate | FL >C:\cert.txt
    Get-WebServicesVirtualDirectory –Server ServerName | FL >C:\EWS.txt
    Get-AutodiscoverVirtualDirectory –Server ServerName | FL >C:\Audis.txt
    Get-ClientAccessServer  | FL >C:\cas.txt
    Email them to me at [email protected]
    With the title as
    "Exchange 2010 Out of Office Assistant not working?"
    Regards
    Fazal M khan

  • Exchange 2013 - OWA "Something Went Wrong", Out of office in Outlook "Server unavailable"

    Hi,
    We have a new deployment of Exchange 2013 CU2 V2 running on a Windows 2012 server.  Everything has been running without issues and then without any real clue to why, we are now getting an issue where OWA says "Something Went Wrong" after processing
    your login, (it appears to process the login as if I type in incorrect details it tells me the password/username is wrong).
    At the same time we have also lost the ability to run the Out Of Office in Outlook which comes back saying the server is not available and we can't seem to share calendars correctly either.  (Can set Out Of Office via the Management Shell without issues).
    When running a Get-Serverhealth on the OWA.Protocol it tells me the OWASelfTestMonitor is unhealthy.
    I've tried re-creating the OWA, EWS Virtual Directorys and also the autodiscover but with no effect.  I've also restarted the server. 
    Outlook 2013 and mobile phones are working fine on the server and the Exchange Admin Centre is also working without issues.
    I am getting tempted to apply CU2 again to see if this sorts it but don't really like doing this on a server with 50 live users on it...
    In the eventlog I can see lots of the 2 errors listed below which seems to line up.  (System Log and Application Log seem to be clear of other errors or warnings.)
    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 04/11/2013 11:25:00
    Event time (UTC): 04/11/2013 11:25:00
    Event ID: 2fcdb9112c794b63a9ea9577a23e4603
    Event sequence: 2
    Event occurrence: 1
    Event detail code: 0
    Application information:
        Application domain: /LM/W3SVC/2/ROOT/owa-411-130280378905273269
        Trust level: Full
        Application Virtual Path: /owa
        Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
        Machine name: SERVERNAME (I altered this for post) 
    Process information:
        Process ID: 9648
        Process name: w3wp.exe
        Account name: NT AUTHORITY\SYSTEM
    Exception information:
        Exception type: HttpException
        Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
    Lots more code.......
    AND
    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 04/11/2013 11:24:24
    Event time (UTC): 04/11/2013 11:24:24
    Event ID: 2586a044b2d74b97a1095aec478bf4ae
    Event sequence: 2
    Event occurrence: 1
    Event detail code: 0
    Application information:
        Application domain: /LM/W3SVC/2/ROOT/EWS-668-130280378564324526
        Trust level: Full
        Application Virtual Path: /EWS
        Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\EWS\
        Machine name: SERVERNAME (I have changed this for post) 
    Process information:
        Process ID: 9840
        Process name: w3wp.exe
        Account name: NT AUTHORITY\SYSTEM
    Exception information:
        Exception type: HttpException
    Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
    lots more data...

    Hi Angela,
    I can't see any re-directions on the website and have certainly not set any intentionally.  I did try installing the Remote Web Gateway on the server and then found that it doesn't work on an exchange box and removed it but the server was working after
    this.
    The HTTP Redirect in Default Web Site is not showing anything set and the same for the Back End.
    The bindings on the default site all look normal with;
    http     80   127.0.0.1
    https   443  127.0.0.1
    http     80    *
    http    443   *
    The same is mirrored in the Exchange Back End site but with ports 81 and 444.
    Running the Outlook auto configure just using Autodiscover all looks good with the URLs listed all pointing to (http)://mail.mydomain.co.uk/whatever...  and the log says Autodiscover to (https)://mail.mydomain.co.uk/Autodiscover/Autodiscover.xml Suceeded
    (0x00000000)
    But, if I type in the OOF address of (https)://mail.mydomain.co.uk/EWS/exchange.asmx I get a login prompt but once user details are entered I then get;
    '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
      Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
     Exception Details: System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
    Source Error:
     An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 
    Stack Trace:
    [XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
       System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) +163
       System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() +7572550
       System.Xml.XmlTextReaderImpl.ParseDocumentContent() +62
       System.Xml.XmlReader.ReadToFollowing(String name) +112
       Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.ReadKillBitXmlContent(XmlReader reader, Int32& refreshRate) +185
       Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.TryReadKillBitFile(Int32& refreshRate, DateTime& lastModifiedTime) +710
       Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitTimer.Start() +202
       Microsoft.Exchange.Services.Global.Application_Start(Object sender, EventArgs e) +975
    [HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
       System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12864205
       System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
       System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
       System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
       System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475
    [HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
       System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12880948
       System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
       System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12722137
    Really wishing I had installed Exchange 2010 at this point!!  Just can't see why its not working :(

  • How to find out what server the outlook client is connected to/change it automatically

    Hi,
    I am performing a server migration from Exchange 2010 to Exchange 2010 (the previous installation was installed by an outsourced provider and is rubbish so I'm configuring it properly). On the of things the existing server lacks is a CAS array configured,
    so I have built the new Exchange 2010 server, configured a new DB and CASArray. I have created a brand new mailbox for a new user and the user's outlook shows it is connected to casarray.domain.local, I have migrated my own mailbox but internally my outlook
    shows it is connected to oldserver.domain.local (under the account settings when you go to change the settings for the account), this is on a domain joined internal desktop. But at home on my personal laptop non-domain joined, it has appeared to reflect the
    new casarray.domain.local. The outlook client is 2007 in both situations.
    When I run the following command, it shows my mailbox is indeed connected to the new exchange server, but this is not true in outlook
    Get-LogonStatistics -Server "new-exch2010" | where {$_.clientname -eq "new-exch2010"}| ft username,servername,clientname
    If I run the above command against the old server my name shows on that list as well. When I look at the connection status of my outlook it shows that it is connected to casarray for directory, but the old server for mail.
    A couple of other things:
    Mailflow is now going to the new exchange server from the gateway over port 25, the autodiscover record in the internal DNS is now also pointing to the new exchange server, outlook clients and users computers have been completely restarted but still don’t
    seem to pick up the new settings, both the old server and new server functions as a multi-role exchange having the Hub, CAS and MBX roles.
     Now that you have all that background info my question is two parts:
    What is the correct powershell command I can run on the exchange server to ensure that all my outlook clients are connected to the new exchange server for all connection types (or identify those which are connected against the old server)?
    How do I get the outlook clients to automatically pick up the casarray servername once their mailboxes have been migrated?
    I am considering removing the CAS from the old server which may force outlook to find it’s new server but am unsure whether this will work or not, and I think I should migrate all the mailboxes into the new DB before I do this.
    Other than that, I am out of ideas.
    Appreciate, any help. Thanks
    Steve

    I had already run the command Get-MailboxDatabase | FL Identity,RpcClientAccessServer
    and it only identified the old database as being tied to the server name, the new database has the correct casarray and all mailboxes are in this new database. should I also set the old database to point to my casarray as the second command indicates? can't
    do any harm right?
    also, I have outlook 2007 and 2013 at home and both of them had automatically reconfigured
    themselves to point to casarray, my problem is with the internal clients.
    today I have also noticed in DNS there is a Zone which points to autodiscover.domain.co.uk
    and in there it points to my old server.
    a few things to note about the above:
    1. the zone is pointing to the .co.uk domain not the .local - is this correct?
    2. should that zone even be in our internal DNS, i hadn't noticed on previous implementation
    of Exchange I have done
    3. if i change the record within that zone to point to my new server, will this likely show
    up the popup message shown in this link http://www.rackspace.com/apps/support/portal/1218 I havent yet got a certificate for the new exchange server (few more days) and i dont want users seeing any kind of untrusted unsecure connection box or it
    will only lead to panic and flooding the helpdesk
    many thanks
    Steve

  • Unable to set out of office on Outlook 2013

    when i click on Automatic Replies (out of office) i get this error "your automatic reply settings cannot be displayed becausethe server is currently unavailable. Try again later.
    When i do Test E-mail Autoconfiguration i get this reponse
    Autoconfiguration was unable to determine your settings!
    I belive OOF isn't working because of autodiscover issue. 
    https://OWA_URL/Autodiscover/Autodiscover.xml
    xml version="1.0" encoding="utf-8" ?>
    <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
    <Response>
    <Error Time="11:09:28.7811659" Id="2346168337">
    <ErrorCode>600</ErrorCode>
    <Message>Invalid Request</Message>
    <DebugData
    />
    </Error>
    </Response>
    </Autodiscover>
    Please help

    Hi,
    Please have a look at the following link and check if it helps:
    Your Out of Office settings cannot be displayed
    Since this issue is more related to the Exchange server side, it's better to post your question to the Exchange forum for further assistance:
    http://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
    The reason why we recommend posting appropriately is you will get the most
    qualified pool of respondents, and other partners
    who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    Steve Fan
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Outlook 2010 Out of Office Assistant only works when prompted for credentials

    Hello,
    I've come across what seems to be an odd issue with Outlook 2010 and Exchange 2010 in an SBS 2011 environment and am hoping someone has seen this issue before.
    Basically, we have a few users who can only get their OOF Assistant in Outlook to work if they supply their credentials at Outlook startup. If credentials are saved, on subsequent startups, the OOF assistant
    will not work, and receive the "Server is currently unavailable" commonly encountered.
    OOF does work within OWA. 
    Everything tests out fine as far as I can tell, but am open to providing more information as required.
    Mahalo!

    Hi,
    Generally, this issue occurs because the CAS server uses the credentials that you used to log on to Windows instead of the credentials that you used to log on to the mailbox in Outlook 2010. Please check whether the Windows credentials do not match the mailbox
    credentials in your environment.
    To resolve this issue, please refer to the following KB:
    http://support.microsoft.com/kb/2596516
    If the issue continues, please check whether there are any event logs in local machine and CAS server. You can post it here for further analysis.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Exchange Server 2010 SP3 RU3 - OWA - Out of Office issue

    Hi,
    We have just upgraded out test lab to Exchange 2010 SP3 RU3. 
    We have 2 CAS-servers and 2 Mailbox-servers. All servers er fully patched.
    Question - reason for upgrading is that our Production environment is running Exchange 2010 SP2 RU7, and we have issues with IE 11(light mode only) which is resolved in SP3 RU3. But we have discovered a another issue after upgrading. 
    After upgrading Exchange,  IE 11 is fixed at the login screen, and we can now choose which login methode we want to use, so this is good. 
    But if you login with IE 11 chosse Options > See all Options > Organize E-mails > Automatic Replies - then the page is blank.
    If you choose to use Firefox or Chrome everything is working correctly.. 
    Does any else have the same problem?

    Hi,
    Yes, running in IE’s compatibility mode is a temporarily workaround. Let’s wait for the update.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Microsoft office issues with clients bound to my Open Directory Master

    So i converted all of my clients from having a local account on there machine to being bound to my Open Directory Master with a home folder on the server. I deleted there local account on there client machine and then bound it and logged in with there server account. launch microsoft entourage,excel and word and i get weird errors when the applications launch. So i reinstalled on the local admin account of the client machine and all applications now work except for microsoft entourage.
    I can set up an account... see my exchange email server but no email. nothing.. if i log the client machine out of the OD master account and log into a local account on the machine everything works fine. Am i missing something? i even set up for the user account in the allowed applications to run the microsoft office suite with no change.
    thanks,
    Jess

    Note Microsoft Office does not support server-based home directories. You can use portable home directories which syncs stuff down to the client (like a roaming profile but "better" )
    As far as errors with application launch, etc., check the permissions on the applications themselves. Office has an annoying habit of installing itself as the user who installs it (well, except Office 2008 which installs itself as user 502, always, lol). Ensure the permissions on the applications make sense -- this will take some command line use of chmod and chown.
    Also ensure that your home directory permissions are mapped to the user you're logged in as. If you move from local accounts to server-based accounts the UID on the home directory will not automatically change properly, and Microsoft stores its stuff in ~/Documents/Microsoft Office Documents which will have the owner/permissions of who initially created that directory.

  • Office 2013 outlook installation only

    Dears,
    Office 2013 installed successfully but some feature for outlook is missing for that need to run setup to select Run All from my Computer.  is there any registry key i can run directly or any script of it do it? only for outlook
    [email protected]

    All i need a key to run setup without going to control panal and select change to add feature.
    Or At least run setup like run from program feature if you select office  and  click option
    There is no registry key to perform this task - because it's not a registry function.
    When you use: Control Panel -> Programs and Features -> Uninstall or change a program -> Office -> Change
    this is actually launching setup.exe, and then you make the changes to features, which then executes msiexec.exe with special logic.
    To perform the equivalent task, you must:
    a1) create the customization MSPfile, with OCT, which generates the special logic (to enable the desired feature state)
    a2) run the necessary msiexec /p YourMSPfile.msp
    or
    b1) create the config.xml, which contains the special logic (to enable the desired feature state)
    b2) run the necessary setup.exe /modify ProPlus /config YourCustomConfig.xml
    e.g.:
    http://technet.microsoft.com/en-us/library/cc178956(v=office.15).aspx
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Outlook client requirements and Exchange 2010/2013 coexistence

    Good morning!
    A question regarding Exchange 2010/2013 coexistence and the Outlook client requirement. I am upgrading and about to install Exhange 2013 into an existing Exchange 2010 Org. The current 2010 Org is patched to SP-3 and Outlook Anywhere is currently disabled.
    I have Outlook clients that do not yet meet the minimun requirements for 2013 (Outlook 2007/2010). When I install my first 2013 server will it effect the current downlevel clients? The mailboxes are still in 2010 so my thoughts were since the Office upgrade
    including Outlook has not yet taken place I didn't want to wait for them to at least get 2013 into the Org. The 2013 server should effect the clients until I configure the CAS on 2013 and only when they are at the proper version, is this correct? Does Outlook
    Anywhere need to be first enabled and configured on the 2010 CAS before I attempt the confgiuration on the 2013 CAS? I just dont want to install 2013 and have Outlook connectivity issues right out of the gate...
    Thanks in advance!

    Outlook 2007 and 2010 are supported for Exchange 2013, you just need to push out the latest patches.
    http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    If you configure the URLs properly in Exchange 2013 to URLs that point to the Exchange 2010 servers, your clients shouldn't try to talk to the Exchange 2013 server.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Out of Office error: 'Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.'

    Hi,
    This is my first post in the forums. Please forgive me if it's in the wrong category or if it's not posted correctly in any way.
    I'll try and give you below as much information about the problem we have here as I can.
    What we have:
    - an on-premises Windows 2012 Standard server that is the PDC, DNS and DHCP server;
    - a second Windows 2012 Standard server with the sole purpose of hosting our Exchange 2013 CU7 server;
    - Windows 7 PCs with Office Home and Business 2010 v.14.0.7143.5000 (32-bit);
    - Outlook 2010 connects through Outlook Anywhere (mail.ourdomain.com).
    The problem:
    If trying to set up Out of Office through Outlook on the client PCs, we'd get an error message: 'Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.' Interestingly, it does work normally for some users.
    It works fine for all users if done through OWA.
    Tests performed:
    User 1 on PC1 has the problem. User 2 on PC2 doesn't have the problem. Both users are members of the same security groups.
    - setting up User 2 on PC 1: the problem exists;
    - setting up User 1 on PC 2: the problem exists;
    - setting up a second Outlook profile on PC2 within User 2's domain account (the one that works), for the same User 2: the problem still exists!
    I haven't been able to set up an Outlook account that works since this issue was discovered, although there are existing Outlook accounts that do not have the issue.
    Let me also point out we have another issue we are working on and which may or may not be related: the Autodiscover function in Outlook doesn't work. Test E-mail AutoConfiguration results in 'Autoconfiguration was unable to determine your settings!'.
    I can see postings in the Internet of other people having the same problem with OoO, but couldn't see a solution that fits my case: some existing accounts in Outlook are fine, other are not and newly created profiles of aforementioned working accounts do not
    work. The majority of the articles/threads I read suggest recreating the Virtual Directories in Exchange, but we did that just a month ago (when troubleshooting the Autodiscover problem) and besides if the problem is in the Virtual Directories, I would expect
    it to affect all accounts.
    Any help in resolving this problem would be greatly appreciated. Please let me know if you need other details.
    Apologies if the posting is not in the right place or not done properly - I'm still learning.

    The IIS log files on the CAS might tell you something. Depending on how your proxy server handles NAT the IP address of your connection might be from the proxy server instead of your client.
    In any case, a tool like Fiddler (http://www.telerik.com/fiddler) can be extremely helpful in working on problems like this because it can decode the SSL traffic on the client and you can see what's being sent
    and what's being received.
    Another thing to check (although it's unlikely to be your case) is whether or not your browser (when you try connecting to the autodiscover URL) thinks it's in the "Internet" zone. the "Local intranet", or at a "Trusted" site.
    The domain names you use on machines on your LAN should be excluded from being proxyed. Anything with "." in the name will be set, unless excluded, to the proxy server.
    Is the time correct on the client machine? Is it more than 5 minutes different to the Exchange machines and domain controllers? That'd be something that would cause Kerberos to fail.
    A certificate can be a problem if its expired or if it doesn't have the correct names. But I wouldn't worry about the uglog.com domain just yet. Until you get the Autodiscover working with the SCP you have bigger problems.
    If you've never used a WPAD file then don't worry about it. It's very useful if you have a complex network and you want to manage how browsers connect to servers. For example, if you have multiple proxy servers the each manage a different set of names, an/or
    if some names should bypass proxy servers entirely and just connect directly. If run a strictly Microsoft network with only Microsoft product that you can manage with GPOs (and you can enforce those GPOs on every machine -- even the BYOD ones) you probably
    don't need a WPAD.
    --- Rich Matheisen MCSE&I, Exchange MVP

  • Exchange 2007 Out of Office Certificate Error

    Hello,
    I have an Exchange 2007 Server and for some odd reason this week, we have been having issues enabling Out of Office in Outlook. It is some sort of issue with the Autodiscover service, but despite reading forum post after forum post, nothing has worked for
    me. At first when we would go into Outlook and click on Out of Office, it would freeze and then say the server is unavailable. I realized that it was trying to resolve a URL so I added a manual A record in the DNS server pointing to the local IP of the server
    and it fixed the issue, kind of. Now when we click on Out of Office Assistant, we get a security certificate error and it is driving my users crazy. I have updated the SRV record and many things, still unable to get it to work. 
    Any help would be super!! 
    Thanks!

    Hi,
    1.First of all please check the name what you are using for autodiscover service is available on SAN certificate.
    2.Please check the name resolution is happening for autodiscover namespace.
    I.e if you try to resolve autodisccover.mydomain.com (or) mail.mydomain.com in your problematic PC it should have to resolved in to cas server ip address or in some scenarios it will get resolved in to LB
    3.Then please check whether you have properly set the autodiscover internal URL in all the cas servers.
    It might be like below
     https:\\autodiscover.mydomain.com\autodiscover\autodiscover.xml
    (or)  
    https:\\mail.mydomain.com\autodiscover\autodiscover.xml
    4.Then please check for the web services url in all the cas servers and that is the major thing which will make the availability services (i.e OOF,free busy lookup) to work perfectly .
    5.In the problematic please uncheck the internet proxy exceptions.
    6.You cane use test email configuration to check whether the outlook client is fetching up the proper url for autodisocver and ews .
    7.test-outlookwebservices (we can use this command to check the fuctionality of autodiscover for an problematic user account)
    8.Please check the root certificates in the problematic client to check whether it is a expired or not .Root certificates is nothing but the one which will come by default with OS .
    9.If all the above is set as perfect but still you are facing the issue.Please follow the below one and this may be not required.
    Please export the san certificate from exchnage to pfx file which should have to include the certificate key by using MMC.Then import the pfx file in to problematic client .Let us see what happens .
    Same on my side i am having few questions about your environment .
    1.Are you facing any certificate errors in OWA .Because why i am asking please check the installed SAN certificate in exchange is valid and or it is not expired ?
    2.what is the problematic client operating system veriosn?
    Please reply me if you have any issues .
    Regards
    S.Nithyanandham

  • Out of Office not working

    Hi 
    I got stuck around a issue where in out of office is not working .. although I am able to set back out of office from outlook and OWA but do not receive any response for either internal or external .  There are no rules in-place , also tried deleting IPM.Note.Rules.OofTemplate.Microsof
    from Mfcmapi but no luck so far . Please suggest.
    Aditya Mediratta

    Hi Aditya,
    1.Please disable the out of office and re enable it again and at the same time please check the oof is enabled on the owa.
    Set-MailboxAutoReplyConfiguration “[email protected]” –AutoReplyState Disabled -InternalMessage $null -externalmessage $null
    Set-MailboxAutoReplyConfiguration “[email protected]” –AutoReplyState enabled -internalmessage "out of office" -externalmessage "out of office"
    2.Check the event logs on the mailbox server for the event ID "3004"
    3.On problematic user mailbox ,just take a backup of all the rules from outlook client and then delete those rules and then disable the OOF and re enabled it again.If we have the crossed the rules quota thenOOF message will not generated from that mailbox as
    well as we will be getting the event ID 3004 on the mailbox servers.
    If In case on the above step if you don't  wanted to delete the existing rules then we can increase the rules quota size and check the oof message is generated or not.
    Get-Mailbox –Identity "nithya" | fl RulesQuota
    Set-Mailbox –Identity "nithya" –RulesQuota 256KB
    4.To check it is for an single user or else for the whole organisation you can make use of creating the test mailboxes and check the results.
    If the problem is on the organisation wide : -
    1.Make sure exchange mailbox assistant service is running on the exchange servers.
    2.Then make sure the EWS url's are properly configured on the exchange servers as well as check the autodiscover funtionality too.
    3.Then for the remote domains to receive oof message we need to allow external oof messages on the remote domain configuration .
    Thanks & Regards S.Nithyanandham

  • Users are not able to use Outlook 2010 to view free/busy information and cannot set Out Of Office automatic reply

    Hi All,
    Please help me.
    I have an issue where users are not able to use Outlook 2010 to view free/busy information and cannot set Out Of Office automatic reply. But they are can set Out Of Office automatic reply from OWA. My exchange server is Ms Exchange 2010.
    The test E-mail AutoConfiguration failed with this error:
    Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml starting
    GetLastError=12175; httpStatus=0.
    Autodiscover to https://mydomain.com/autodiscover/autodiscover.xml Failed (0x800C8203)
    Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
    GetLastError=12007; httpStatus=0.
    Autodiscover to https://autodiscover.mydomain.com/autodiscover/autodiscover.xml Failed (0x800C8203)
    Local autodiscover for mydomain.com starting
    Local autodiscover for mydomain.com Failed (0x8004010F)
    Redirect check to http://autodiscover.mydomain.com/autodiscover/autodiscover.xml starting
    Srv Record lookup for http://autodiscover.mydomain.com/autodiscover/autodiscover.xml Failed (0x80072EE7)
    Srv Record lookup for mydomain.com starting
    Srv Record lookup for mydomain.com Failed (0x8004010F)
    Any idea?
    Thanks,
    Pieter

    OK.
    Please follow this step.
    1. As you said you are in coexistence step , so for now all endpoint already point to Exchange 2010 right?
    2. Check legacy owa redirect that you already configure
    3. In Exchange 2010 , Make sure that you already configure "Autodiscoverinternaluri" by this command set-clientaccessserver -identity "servername" -autodiscoverinternaluri
    https://autodiscover.domain.com/autodiscover/autodiscover.xml. and don't forget to create autodiscover record in DNS
    4. in Exchange 2010 , Make sure that you already configure "EWS" path by this command set-webservicesvertualdirectory -identity "XXX\Default web site name" -internalurl
    https://yourinternalurl/EWS/Exchange.asmx -externalurl https://yourexternalurl/EWS/Exchange.asmx
    5. don't forget to replicate freebusy from Exchange 2003 to Excahnge 2010 via public folder.
    You error look like client cannot get autodiscover process please check it again.

Maybe you are looking for