Link to home
Start Free TrialLog in
Avatar of JAM-Tech
JAM-Tech

asked on

Auto Account Setup not filling in user account information

I have recently carried out a complete system shut down in preparation for an electrical audit.  After carrying this out and bringing everything back online their have been a couple of issues with our Exchange environment.

The auto discover feature in outlook is no longer detecting the user account that is logged in when setting up outlook for the first time.

There is also an issue with updating the gal causing outlook to now freeze.

The environment is Exchange 2010 and Outlook 2010 in a VMware virtual environment.

So far I have checked internal and external dns records, resolved the certificate using an ssl checker, reset the virtual directory and re-added the internal and external autodiscover urls (not too sure why these went missing).



Here are a few extracts from relevant shell commands:

[PS] C:\Windows\system32>get-autodiscovervirtualdirectory | fl


RunspaceId                      : 76e26df1-98bc-4f42-8b41-d72ec65ff22d
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://exchange2.domain.co.uk/W3SVC/1/ROOT/Autodiscover
Path                            : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags         : {}
ExtendedProtectionSPNList       : {}
Server                          : exchange2
InternalUrl                     :
ExternalUrl                     :
AdminDisplayName                :
ExchangeVersion                 : 0.10 (14.0.100.0)
DistinguishedName               : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=exchange2,CN=Servers,CN=E
                                  xchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=JAMREC,CN=
                                  Microsoft Exchange,CN=Services,CN=Configuration,DC=jamrec,DC=jamjobs,DC=co,DC=uk
Identity                        : exchange2\Autodiscover (Default Web Site)
Guid                            : e2e20214-0667-4b51-bd61-41ad58a9cde9
ObjectCategory                  : domain.co.uk/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass                     : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged                     : 23/07/2012 11:03:32
WhenCreated                     : 23/07/2012 10:50:13
WhenChangedUTC                  : 23/07/2012 10:03:32
WhenCreatedUTC                  : 23/07/2012 09:50:13
OrganizationId                  :
OriginatingServer               : dc1.domain.co.uk
IsValid                         : True

RunspaceId                      : 76e26df1-98bc-4f42-8b41-d72ec65ff22d
Name                            : Autodiscover (Default Web Site)
InternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods   : {Basic, Ntlm, WindowsIntegrated}
LiveIdSpNegoAuthentication      : False
WSSecurityAuthentication        : False
LiveIdBasicAuthentication       : False
BasicAuthentication             : True
DigestAuthentication            : False
WindowsAuthentication           : True
MetabasePath                    : IIS://cas.domain.co.uk/W3SVC/1/ROOT/Autodiscover
Path                            : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags         : {}
ExtendedProtectionSPNList       : {}
Server                          : cas
InternalUrl                     : https://cas.domain.co.uk/autodiscover/autodiscover.xml
ExternalUrl                     : https://autodiscover.domain.co.uk/autodiscover/autodiscover.xml
AdminDisplayName                :
ExchangeVersion                 : 0.10 (14.0.100.0)
DistinguishedName               : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=cas,CN=Servers,CN=E
                                  xchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=JAMREC,CN=
                                  Microsoft Exchange,CN=Services,CN=Configuration,DC=jamrec,DC=jamjobs,DC=co,DC=uk
Identity                        : cas\Autodiscover (Default Web Site)
Guid                            : c2fef98b-2201-4a1a-80f2-e8d9c2f096e9
ObjectCategory                  : domain.co.uk/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass                     : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged                     : 28/08/2013 08:13:58
WhenCreated                     : 27/08/2013 14:24:15
WhenChangedUTC                  : 28/08/2013 07:13:58
WhenCreatedUTC                  : 27/08/2013 13:24:15
OrganizationId                  :
OriginatingServer               : dc1.domain.co.uk
IsValid                         : True


[PS] C:\Windows\system32>get-clientaccessserver | fl


RunspaceId                           : 76e26df1-98bc-4f42-8b41-d72ec65ff22d
Name                                 : cas
Fqdn                                 : cas.domain.co.uk
OutlookAnywhereEnabled               : True
AutoDiscoverServiceCN                : cas
AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri       : https://cas.domain.co.uk/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope                : {Sale}
AlternateServiceAccountConfiguration :
IrmLogEnabled                        : True
IrmLogMaxAge                         : 30.00:00:00
IrmLogMaxDirectorySize               : 250 MB (262,144,000 bytes)
IrmLogMaxFileSize                    : 10 MB (10,485,760 bytes)
IrmLogPath                           : C:\Program Files\Microsoft\Exchange Server\V14\Logging\IRMLogs
MigrationLogLoggingLevel             : Information
MigrationLogFilePath                 :
MigrationLogMaxAge                   : 180.00:00:00
MigrationLogMaxDirectorySize         : 10 GB (10,737,418,240 bytes)
MigrationLogMaxFileSize              : 100 MB (104,857,600 bytes)
IsValid                              : True
ExchangeVersion                      : 0.1 (8.0.535.0)
DistinguishedName                    : CN=cas,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=A
                                       dministrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuratio
                                       n,DC=domain,DC=domain1,DC=co,DC=uk
Identity                             : cas
Guid                                 : 0c496370-01b6-4b2b-83ce-16115a28e688
ObjectCategory                       : domain.co.uk/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass                          : {top, server, msExchExchangeServer}
WhenChanged                          : 25/04/2013 15:58:48
WhenCreated                          : 16/04/2012 09:49:49
WhenChangedUTC                       : 25/04/2013 14:58:48
WhenCreatedUTC                       : 16/04/2012 08:49:49
OrganizationId                       :
OriginatingServer                    : dc1.domain.co.uk

RunspaceId                           : 76e26df1-98bc-4f42-8b41-d72ec65ff22d
Name                                 : server2
Fqdn                                 : server2.domain.co.uk
OutlookAnywhereEnabled               : False
AutoDiscoverServiceCN                : server2
AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri       : https://server2.domain.co.uk/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope                : {London}
AlternateServiceAccountConfiguration :
IrmLogEnabled                        : True
IrmLogMaxAge                         : 30.00:00:00
IrmLogMaxDirectorySize               : 250 MB (262,144,000 bytes)
IrmLogMaxFileSize                    : 10 MB (10,485,760 bytes)
IrmLogPath                           : C:\Program Files\Microsoft\Exchange Server\V14\Logging\IRMLogs
MigrationLogLoggingLevel             : Information
MigrationLogFilePath                 :
MigrationLogMaxAge                   : 180.00:00:00
MigrationLogMaxDirectorySize         : 10 GB (10,737,418,240 bytes)
MigrationLogMaxFileSize              : 100 MB (104,857,600 bytes)
IsValid                              : True
ExchangeVersion                      : 0.1 (8.0.535.0)
DistinguishedName                    : CN=server2,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=A
                                       dministrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuratio
                                       n,DC=domain,DC=domain1,DC=co,DC=uk
Identity                             : server2
Guid                                 : 55848932-b4ad-4ab4-be26-59b5d690e37d
ObjectCategory                       : domain.co.uk/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass                          : {top, server, msExchExchangeServer}
WhenChanged                          : 12/04/2013 08:21:28
WhenCreated                          : 23/07/2012 10:43:12
WhenChangedUTC                       : 12/04/2013 07:21:28
WhenCreatedUTC                       : 23/07/2012 09:43:12
OrganizationId                       :
OriginatingServer                    : dc1.domain.co.uk

[PS] C:\Windows\system32>get-exchangecertificate | fl


AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
                     ule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : various entries omitted
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=domain-dc2-CA, DC=domain, DC=domain1, DC=co, DC=uk
NotAfter           : 25/04/2015 15:47:54
NotBefore          : 25/04/2013 15:47:54
PublicKeySize      : 2048
RootCAType         : Enterprise
SerialNumber       : 6CFE81F9000000000267
Services           : IMAP, POP, IIS, SMTP
Status             : Valid
Subject            : CN=...com, OU=MsExchange, O=domain, L=Manchester, S=Manchester, C=GB
Thumbprint         : 7B41ECDB43F569A31630C76657483089C7A1F0A2

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
                     ule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : various entries omitted
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : CN=domain-dc2-CA, DC=domain, DC=domain1, DC=co, DC=uk
NotAfter           : 25/04/2015 14:30:28
NotBefore          : 25/04/2013 14:30:28
PublicKeySize      : 2048
RootCAType         : Enterprise
SerialNumber       : 6CB7A0BE000000000266
Services           : SMTP
Status             : Valid
Subject            : CN=autodiscover.sas.com, OU=MsExchange, O=JAM Recruitment, L=Manchester, S=Manchester, C=GB
Thumbprint         : 66BD2BCFB3DE83111EFA918610686A34832A0F2E

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
                     ule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {cas, cas.domain.domain1.co.uk}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=cas
NotAfter           : 25/04/2018 14:06:00
NotBefore          : 25/04/2013 14:06:00
PublicKeySize      : 2048
RootCAType         : None
SerialNumber       : 6153CD1B500EBDBD41D964E02BBF25EF
Services           : SMTP
Status             : Valid
Subject            : CN=cas
Thumbprint         : F572911615F95CFFB795030FAE08D6A6B4CF95F3

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
                     ule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains : {outlook.domainruitment.co.uk, www.outlook.domainruitment.co.uk, cas.domain.domain1.co.uk,
                                    various entries omitted
HasPrivateKey      : True
IsSelfSigned       : False
Issuer             : SERIALNUMBER=98798798, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.
                     com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
NotAfter           : 17/04/2015 17:22:06
NotBefore          : 27/04/2012 15:21:33
PublicKeySize      : 2048
RootCAType         : ThirdParty
SerialNumber       : adh89y72398123
Services           : SMTP
Status             : Valid
Subject            : CN=outlook.domainruitment.co.uk, OU=Domain Control Validated, O=outlook.domainruitment.co.uk
Thumbprint         : 272216686BF9703E4871F652D161B360A40E7C9F

AccessRules        : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessR
                     ule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAcc
                     essRule}
CertificateDomains : {cas, cas.domain.domain1.co.uk}
HasPrivateKey      : True
IsSelfSigned       : True
Issuer             : CN=cas
NotAfter           : 16/04/2017 09:51:03
NotBefore          : 16/04/2012 09:51:03
PublicKeySize      : 2048
RootCAType         : None
SerialNumber       : 30BB6F20B3BC2BBC4E9694DED2C7459A
Services           : SMTP
Status             : Valid
Subject            : CN=cas
Thumbprint         : DDBC015CD31140298F2D64E824D3D5F7535E4B60
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Do an Autodiscover test from Outlook.

http://semb.ee/adt

What does that return?

Simon.
Avatar of JAM-Tech
JAM-Tech

ASKER

Hi Simon,

After re-adding the auto discovery urls it works without a problem.
The issue of adding an account and having it auto fill an AD users details is still present, so is the gal update issue.

I've attached the screenshots for the test.

Thanks,
Capture.JPG
Capture1.JPG
"After re-adding the auto discovery urls it works without a problem."

It isn't clear what you did there.

If you set internal and external URLs on the Autodiscover virtual directory then that shouldn't have done anything. They aren't used, and in a default configuration are blank.

Simon.
Before I added them the test failed, after adding them it worked!  I've not carried out any other work except for resetting the virtual directory, after resetting it I tested autoconfiguration using the same way as you requested and it failed.  After adding the urls it worked.

The problem is that I still cannot get outlook to autodetect the user.
The URLs should be blank. I don't know why it works with them included because the information isn't used.

If the clients are members of the domain, then they query the domain for the Autodiscover value which is listed here:

get-clientaccessserver | select identity, autodiscoverserviceinternaluri

Therefore check that URL is correct and resolves to the right place. The host name needs to be the on the SSL certificate.

Simon.
Hi Simon,

I tested both URLs (one for each site) and I am prompted for credentials and then put through to the xml.

The strange thing is that this only started happening after the power down of our network which would mean that everything was in place and working before but for some reason stopped.  Certificates in that case will be registered and configured as required, or should be for it to have been working.

Also this is the "Auto Account Setup" screen within Outlook 2010 that is not automatically filling in the users information (just to be clear).

Thanks,
Outlook pulls that information from the domain, so it will only work with domain joined members. For everyone else you have to enter the information.
I will confess, I don't actually know how Outlook does it - it isn't something I have seen go wrong before. It would tend to suggest that something isn't running correctly on the domain and Outlook cannot query it.

Simon.
I appreciate the help so far Simon.

All domain processes are running as normal.

Anyone else want to put their thoughts in?
Hi Simon,

After reviewing the xml file again I am getting the following:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Autodiscover><Response><Error Time="09:29:51.3539299" Id="3116042342"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>
If you browse to the Autodiscover path with a browser, that is what I would expect to see, because your Browser isn't Outlook.
However I was under the impression the problem wasn't with Autodiscover but before that process even starts.

Simon.
The problem is when I open Outlook as a user for the first time it gets to the Auto Account Setup screen which should then automatically fill in the users email address and pick up the password.  Unfortunately this does not happen.

I can enter the details manually and it works, I'm just puzzled why it's now stopped working.
ASKER CERTIFIED SOLUTION
Avatar of JAM-Tech
JAM-Tech

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Resolved myself