locked
Using new computer, existing mailbox user Outlook 2010 Auto-configuration points to the Mailbox Server rather than CAS Array ? RRS feed

  • Question

  • People,

    I'm having a problem with the current AD user account & mailbox user where they cannot get the Outlook 2010 automatically configured to point into the CAS array ?

    This is happening when the existing user get new computer replaced or login to the Terminal Server where their account never set before, it always points to the Mailbox Server instead of the Client Access Server array virtual name. 

    The work around that I provided is typing the Client Access Array address and then specify Outlook.domain.com to match the Windows NLB name (and Get-ClientAccessArray result).

    Single AD Domain forest

    AD Site DataCenter contains:
    Domain Controllers: PRODDC01-VM, PRODDC02-VM, PRODDC03-VM
    Exchange Server 2010 SP3 - CAS&HT: PRODMAIL01-VM and PRODMAIL01-VM (Configured with WNLB as outlook.domain.com)
    Exchange Server 2010 SP3 - Mailbox: PRODMAILBOX01-VM and PRODMAILBOX01-VM (no DAG is set)
    Terminal Server (RDSH 2008 R2): PRODTS01-VM ... PRODTS60-VM (when user logged in to new TS, it got the same error).

    AD Site HQ contains - This site has no issue:
    Domain Controllers: HQDC01 and HQDC02
    Workstations using Outlook 2010 and 2013

    AD Site SiteOffice1 contains - This site has problem:
    Domain Controllers: none but the majority of the workstations LOGONSERVER is pointing to PRODDC03-VM

    Workstations using Outlook 2010 and 2013
    All of the Exchange environment here is using Exchange Server 2010 SP3 for all server roles.

    Any help would be greatly appreciated.

    Thanks

    /* Server Support Specialist */


    Wednesday, April 15, 2015 6:12 AM

Answers

  • Hi,

    From your description, the Internal URLs for EWS are not pointing to the CAS array. You can reset it and check the result, using the Set-WebServicesVirtualDirectory cmdlet.

    For your reference:

    https://technet.microsoft.com/en-us/library/aa997233%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

    Hope this can be helpful to you.

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Amy Wang
    TechNet Community Support

    Wednesday, April 22, 2015 2:00 AM
    Moderator
  • To keep things simple, yes.  In fact, in our environment, the internal and external URLs across the board are identical - we made sure our internal DNS has an A record for the external "mail.company.com", so our users get identical connectivity, internally or externally.
    Wednesday, April 22, 2015 12:06 PM
  • The users have to select Repair on the Account Settings page of the profile.  I don't know of a way to automate this without destroying the existing profile, but it also isn't essential that it is done immediately.  You could do it a users have issues with Outlook, or they will get a valid profile when their computer is refreshed.

    Will Martin ...
    -join ('77696c6c406d617274696e2d66616d696c6965732e6f7267' -split '(?<=\G.{2})' | ? { $_ } | % { [char][int]"0x$_" })

    Wednesday, May 20, 2015 12:33 PM

All replies

  • How are your mailbox databases configured for the RpcClientAccessServer?  I will wager they are set for your mailbox server and not your CAS Array name.  Set them to use the CAS Array, and you will fix this issue.
    Wednesday, April 15, 2015 7:39 PM
  • How are your mailbox databases configured for the RpcClientAccessServer?  I will wager they are set for your mailbox server and not your CAS Array name.  Set them to use the CAS Array, and you will fix this issue.
    Get-MailboxDatabase | FT Name,RPCClientAccessServer cmdlet returns all consistent Outlook.domain.com as the result ?

    /* Server Support Specialist */

    Thursday, April 16, 2015 7:09 AM
  • Hi,

    Yes, the RPCClientAccessServer should point to the CAS array. What's more, I would like to clarify the following things:

    1. Run the Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri cmdlet to make sure that it displays the correct Uri.

    2. Run the Get-WebServicesVirtualDirectory | fl Identity,*auth*,*URL to ensure that URL for EWS points to the CAS array.

    Hope this can be helpful to you.

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Amy Wang
    TechNet Community Support

    Thursday, April 16, 2015 7:45 AM
    Moderator
  • Hi,

    Yes, the RPCClientAccessServer should point to the CAS array. What's more, I would like to clarify the following things:

    1. Run the Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri cmdlet to make sure that it displays the correct Uri.

    2. Run the Get-WebServicesVirtualDirectory | fl Identity,*auth*,*URL to ensure that URL for EWS points to the CAS array.

    Hope this can be helpful to you.

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Amy Wang
    TechNet Community Support

    Here's the result:

    [PS] C:\>Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri
    
    AutoDiscoverServiceInternalUri : https://PRODMAIL02-VM.domain.com/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceInternalUri : https://PRODMAIL01-VM.domain.com/Autodiscover/Autodiscover.xml

    [PS] C:\>Get-WebServicesVirtualDirectory | fl Identity,*auth*,*URL
    
    Identity                      : PRODMAIL01-VM\EWS (Default Web Site)
    CertificateAuthentication     :
    InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
    ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
    LiveIdSpNegoAuthentication    : False
    WSSecurityAuthentication      : True
    LiveIdBasicAuthentication     : False
    BasicAuthentication           : False
    DigestAuthentication          : False
    WindowsAuthentication         : True
    InternalNLBBypassUrl          : https://PRODMAIL01-VM.domain.com/ews/exchange.asmx
    InternalUrl                   : https://PRODMAIL01-VM.domain.com/EWS/Exchange.asmx
    ExternalUrl                   : https://email.domain.com/ews/exchange.asmx
    
    Identity                      : PRODMAIL02-VM\EWS (Default Web Site)
    CertificateAuthentication     :
    InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
    ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
    LiveIdSpNegoAuthentication    : False
    WSSecurityAuthentication      : True
    LiveIdBasicAuthentication     : False
    BasicAuthentication           : False
    DigestAuthentication          : False
    WindowsAuthentication         : True
    InternalNLBBypassUrl          : https://PRODMAIL02-VM.domain.com/ews/exchange.asmx
    InternalUrl                   : https://PRODMAIL02-VM.domain.com/EWS/Exchange.asmx
    ExternalUrl                   : https://email.domain.com/ews/exchange.asmx

    The IP address of email.domain.com and outlook.domain.com are the same IP address, this IP address is servec by WNLB.


    /* Server Support Specialist */

    Thursday, April 16, 2015 10:50 PM
  • Hi,

    From your description, the Internal URLs for EWS are not pointing to the CAS array. You can reset it and check the result, using the Set-WebServicesVirtualDirectory cmdlet.

    For your reference:

    https://technet.microsoft.com/en-us/library/aa997233%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

    Hope this can be helpful to you.

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Amy Wang
    TechNet Community Support

    Wednesday, April 22, 2015 2:00 AM
    Moderator
  • Hi,

    From your description, the Internal URLs for EWS are not pointing to the CAS array. You can reset it and check the result, using the Set-WebServicesVirtualDirectory cmdlet.

    For your reference:

    https://technet.microsoft.com/en-us/library/aa997233%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

    Hope this can be helpful to you.

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Amy Wang
    TechNet Community Support

    Hi Amy,

    So in this case the result returned from the Get-WebServicesVirtualDirectory | fl Identity,*auth*,*URL command should be consistent Outlook.domain.com for all Client Access Servers ?



    /* Server Support Specialist */

    Wednesday, April 22, 2015 5:04 AM
  • To keep things simple, yes.  In fact, in our environment, the internal and external URLs across the board are identical - we made sure our internal DNS has an A record for the external "mail.company.com", so our users get identical connectivity, internally or externally.
    Wednesday, April 22, 2015 12:06 PM
  • Hi,

    From your description, the Internal URLs for EWS are not pointing to the CAS array. You can reset it and check the result, using the Set-WebServicesVirtualDirectory cmdlet.

    For your reference:

    https://technet.microsoft.com/en-us/library/aa997233%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

    Hope this can be helpful to you.

    Best regards,


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Amy Wang
    TechNet Community Support

    Many thanks for the reply and clarification Amy, so all of the HT-CAS servers InternalURL must be the same to point to the same FQDN as in the Windows NLB manager ?

    is there any outage required to change those value using the powershell script on the HT-CAS servers ?


    /* Server Support Specialist */

    Tuesday, May 19, 2015 12:33 AM
  • No outage is required, but the Outlook profiles don't update automatically.  You would need to repair them to get them to change to the CAS Array name from the CAS name.

    Will Martin ...
    -join ('77696c6c406d617274696e2d66616d696c6965732e6f7267' -split '(?<=\G.{2})' | ? { $_ } | % { [char][int]"0x$_" })

    Tuesday, May 19, 2015 12:14 PM
  • No outage is required, but the Outlook profiles don't update automatically.  You would need to repair them to get them to change to the CAS Array name from the CAS name.

    Will Martin ...
    -join ('77696c6c406d617274696e2d66616d696c6965732e6f7267' -split '(?<=\G.{2})' | ? { $_ } | % { [char][int]"0x$_" })

    Many thanks Will for the reply here.

    So how do I repair this Outlook profile companywide ? is there any group policy to do it or do I have to manually reinstall Outlook for every users ?


    /* Server Support Specialist */

    Tuesday, May 19, 2015 10:21 PM
  • The users have to select Repair on the Account Settings page of the profile.  I don't know of a way to automate this without destroying the existing profile, but it also isn't essential that it is done immediately.  You could do it a users have issues with Outlook, or they will get a valid profile when their computer is refreshed.

    Will Martin ...
    -join ('77696c6c406d617274696e2d66616d696c6965732e6f7267' -split '(?<=\G.{2})' | ? { $_ } | % { [char][int]"0x$_" })

    Wednesday, May 20, 2015 12:33 PM