asked on

Outlook 2010 email autoconfigure always pointing to Mailbox Server not the CAS Array name ?

Hi All,

I'm having strange issue with my newly created user in my remote AD site where newly configured PC for existing user, their Outlook is failed to be automatically configured, because the name of the CAS Array where all users in my HQ office is using is replaced by one of the Mailbox Server (in some of the AD sites but not in the Head Quarter office).

The CAS Array: Outlook.domain.com is pingable from the workstation
Workaround: is to manually type the CAS Array FQDN above.

Any idea where to troubleshoot or check please ?

Albert Widjaja

ASKER

Here is my topology layout roughly:

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)

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

Mike

Sounds like an issue with autodiscovery. Have you confirmed that your autodiscover URL's are still pointing to your CAS Array?

Albert Widjaja

ASKER

how ?

is it from the CAS array member using Get-AutodiscoverVirtualDirectory | fl ?

there was no changes doneto the Exchange Servers this year.

Will Szymkowski

As stated it is likely due to auto-discover. This is the mechanism where the mailbox is mapped to the Outlook session automatically.

From the users machine hold ctrl+right click the Outlook icon in the System Tray and select Test Email Auto Configuration.

Run the Autodiscover test and check the results tab. Look for Autodiscover URL and see where it is pointing to.

Will.

Albert Widjaja

ASKER

Here's the result from the Powershell

[PS] C:\Windows\system32>

Get-AutodiscoverVirtualDirectory | fl

Open in new window

RunspaceId : b929d268-4308-42a2-949e-ffc505fb61a9
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://PRODMAIL01-VM.domain.com/W3SVC/1/ROOT/Autodiscover
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
Server : PRODMAIL01-VM
InternalUrl :
ExternalUrl :
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=PRODMAIL01-VM,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
Identity : PRODMAIL01-VM\Autodiscover (Default Web Site)
Guid : adc66b9a-20ac-44c7-bab5-7f708493e015
ObjectCategory : domain.com/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged : 10/11/2012 4:24:06 PM
WhenCreated : 17/01/2011 10:29:02 AM
WhenChangedUTC : 10/11/2012 5:24:06 AM
WhenCreatedUTC : 16/01/2011 11:29:02 PM
OrganizationId :
OriginatingServer : PRODDC03-VM.domain.com
IsValid : True

RunspaceId : b929d268-4308-42a2-949e-ffc505fb61a9
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://PRODMAIL02-VM.domain.com/W3SVC/1/ROOT/Autodiscover
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
Server : PRODMAIL02-VM
InternalUrl :
ExternalUrl :
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=PRODMAIL02-VM,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
Identity : PRODMAIL02-VM\Autodiscover (Default Web Site)
Guid : 66b6e80e-5b15-47d9-b2cf-cb3cfa59411e
ObjectCategory : domain.com/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged : 10/11/2012 4:24:06 PM
WhenCreated : 19/01/2011 12:22:46 PM
WhenChangedUTC : 10/11/2012 5:24:06 AM
WhenCreatedUTC : 19/01/2011 1:22:46 AM
OrganizationId :
OriginatingServer : PRODDC03-VM.domain.com
IsValid : True

Albert Widjaja

ASKER

@Will & Shadowless: Yeah Ithought so, but this is happening on the existing AD user account with new replaced computer so start from scratch due to PC refresh.

Mike

run this

Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

Albert Widjaja

ASKER

one thing that I notice, is that you cannot test the Outlook Autodiscover from the Outlook system tray then Right Clcik option because the email profile is not set up yet.

Albert Widjaja

ASKER

Here's the result:

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl


Identity    : PRODMAIL01-VM\EWS (Default Web Site)
InternalUrl : https://PRODMAIL01-VM.domain.com/EWS/Exchange.asmx
ExternalUrl : https://email.domain.com/ews/exchange.asmx

Identity    : PRODMAIL02-VM\EWS (Default Web Site)
InternalUrl : https://PRODMAIL02-VM.domain.com/EWS/Exchange.asmx
ExternalUrl : https://email.domain.com/ews/exchange.asmx

Open in new window

SOLUTION

Mike

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Albert Widjaja

ASKER

yes, it is confirmed the affected user was in a mailbox server 01 where database contains her mailbox. Therefore in the textbox filed during the email profile setup was listed PRODMAIL01-VM

The server value is somehow set to the proper mailbox server but it must be set to the WNLB or CAS Array name.

SOLUTION

Mike

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Albert Widjaja

ASKER

@Shadow: yes that's what I mean.

the reply above was regarding the Outlook profile in the new workstation.

Mike

Have you tried adding the user's mailbox on another workstation?

SOLUTION

Guy Lidbetter

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Albert Widjaja

ASKER

@Guy: sure, so I assume those test must be done through the affected users workstation ?

Guy Lidbetter

That's right... we need to establish what it can see on the network.

Albert Widjaja

ASKER

Guy, I can ping the Autodiscover address from the affected new computer in the affected AD site.

ASKER CERTIFIED SOLUTION

Guy Lidbetter

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Albert Widjaja

ASKER

ok, so in this case to change the InternalURL using the powershell below:

Get-TransportServer | Set-WebServicesVirtualDirectory -InternalUrl "https://mail.domain.com/ews/exchange.asmx"

Open in new window

is there any outage expected or it can be done during the business hours ?

Albert Widjaja

ASKER

ok, so if I move all of my mailboxes to Office 365, does this problem will go away because Office 365 is always perfect with no issue at all ?

SOLUTION

Guy Lidbetter

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial