• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 111
  • Last Modified:

faultfinding autodiscovery

have installed a new exchange 2013 email server,  web OWA , mobiles and IPAD's all work ok.
But MS outlook on the desktops wont open with the error saying you need to sync with the exchange before you can open the .OST.
having run testconnectivity.microsoft.com a number of times and making several modifications to the DNS I still keep getting the error.
Host autodiscover.domain couldn't be resolved in DNS InfoDomainNonexistent.

has anyone any solutions
0
Alan Duck
Asked:
Alan Duck
  • 5
  • 3
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
Autodiscover internally and externally work in different ways.
Externally you need to have either autodiscover.example.com resolve to the Exchange server and be listed in the SSL certificate, or have SRV records for Autodiscover.

Internally, the client queries the domain for the value of get-clientaccessserver | select identity, autodiscoverserviceinternaluri

The host name listed needs to resolve to the Exchange server, and be listed on the SSL certificate. As you cannot get internal names on the SSL certificates, that would need to be an external host name with a split DNS.
http://semb.ee/hostnames2013

Simon.
0
 
Alan DuckAuthor Commented:
I have run the script as suggested it did through up this error below

[PS] C:\Windows\system32>Set-OWAVirtualDirectory -identity "mail-server.bsc.local\owa (Default Web Site)" -InternalURL h
ttps://mail.bcs.co.uk/owa -ExternalURL https://mail.bcs.co.uk/owa
The operation couldn't be performed because object 'mail-server.bsc.local\owa (Default Web Site)' couldn't be found on
'mail-server.bcs.local'.
    + CategoryInfo          : NotSpecified: (:) [Set-OwaVirtualDirectory], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : [Server=mail-SERVER,RequestId=063afefb-8521-489b-a01d-732047b6e797,TimeStamp=21/11/2014 1
   5:58:52] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 16B9E02D,Microsoft.Exchange.Management.SystemC
  onfigurationTasks.SetOwaVirtualDirectory
    + PSComputerName        : mail-server.bcs.local

also a couple out outlook had connected and are appearing to work but the email server setting in these are a little strange its is (0433aca6-6842-4eba-82bb-c34dcd27043b@bcs.co.uk)

any suggestions
0
 
Simon Butler (Sembee)ConsultantCommented:
The result you got back was correct.
All users on Exchange 2013 have a unique endpoint instead of a server name. Therefore what you are seeing is what I would expect.

As for the script error - is OWA on the default site? You can set the virtual directory manually through ECP. If that was the only one to fail then that is probably what I would do.

Simon.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Alan DuckAuthor Commented:
hi it seem that after making these changes on the MS outlook programs I still get the error
Cannot start Microsoft Outlook
the set of folders Cannot be opened  you must connect to Microsoft exchange with a current profile   before
you can synchronise your folders with your outlook data File (.ost)

even those I have check the mail setting over and over.
any Ideas.
0
 
Simon Butler (Sembee)ConsultantCommented:
The usually means the client cannot connect to the server. On Exchange 2013 it only uses Outlook Anywhere, so you need to ensure the host name configured within the Outlook Anywhere configuration is correct.

Simon.
0
 
Alan DuckAuthor Commented:
I will check that
0
 
Alan DuckAuthor Commented:
it appears now the computers on the domain work ok , only offsite laptops causing problems and I think that's a security problem.
0
 
Alan DuckAuthor Commented:
worked well
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now