Outlook на windows 7 не подключается к exchange 2019

Posted by saifalmodares 2020-01-18T20:13:12Z

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  Let’s have a look at your virtual directories configuration, run the following commands, remove any private info (keep the changes consistent) and attach log0.txt to your reply:

  Powershell

  Start-Transcript log0.txt
  Get-OabVirtualDirectory | fl server, Name, *URL*, *auth*
  Get-WebServicesVirtualDirectory | fl server, Name, *URL*, *auth*
  Get-EcpVirtualDirectory | fl server, Name, *URL*, *auth*
  Get-ActiveSyncVirtualDirectory | fl server, Name, *URL*, *auth*
  Get-OutlookAnywhere | fl server, Name, *URL*, *hostname*, *auth*
  Get-OwaVirtualDirectory | fl server, Name, *URL*, *auth*
  Get-ClientAccessService | fl Name, OutlookAnywhereEnabled, AutodiscoverServiceInternalUri
  Get-ExchangeCertificate | fl FriendlyName, Subject, CertificateDomains, Thumbprint, Services, Issuer, *not*
  Get-MapiVirtualDirectory | fl server, Name, *URL*, *auth*
  Get-ClientAccessArray | fl
  Get-OutlookProvider
  Get-ExchangeServer | fl *version*
  Get-OrganizationConfig | fl *mapi*
  Stop-Transcript
  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  here you are

  attach_file
  Attachment
  
  tt.txt
  7.05 KB
  
  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• are you able to telnet to 443 from outlook machine ?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  Execute the following commands, it should set all the required configuration. Restart IIS on the server once done.
  Make sure also to validate that IIS (Default Website) is listening on port 443 and has a corresponding certificate bound to it for both 127.0.0.1 as well as the IP of the server.

  Powershell

  Set-OWAVirtualDirectory –Identity "OWA (default web site)" -ExternalURL https://exhost.domain.com/OWA -InternalURL https://exhost.domain.com/OWA
  Set-OABVirtualDirectory –Identity "OAB (default web site)" -ExternalURL https://exhost.domain.com/OAB -InternalURL https://exhost.domain.com/OAB
  Set-ECPVirtualDirectory –Identity "ECP (default web site)" -ExternalURL https://exhost.domain.com/ECP -InternalURL https://exhost.domain.com/ECP
  Set-WebServicesVirtualDirectory –Identity "EWS (default web site)" -ExternalUrl https://exhost.domain.com/ews/exchange.asmx -InternalURL https://exhost.domain.com/ews/exchange.asmx
  Set-ActiveSyncVirtualDirectory –Identity "Microsoft-Server-ActiveSync (default web site)" -ExternalURL https://exhost.domain.com/Microsoft-Server-ActiveSync -InternalURL https://exhost.domain.com/Microsoft-Server-ActiveSync
  Set-ClientAccessServer -Identity <YourExchangeServer> -AutoDiscoverServiceInternalUri https://exhost.domain.com/Autodiscover/Autodiscover.xml
  Set-OutlookAnywhere -InternalHostname "exhost.domain.com" -InternalClientAuthenticationMethod Ntlm -InternalClientsRequireSsl $true -ExternalHostname "exhost.domain.com" -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $true -IISAuthenticationMethods NTLM,Basic -ssloffloading:$false
  Set-MapiVirtualDirectory -Identity "mapi (Default Web Site)" -InternalUrl https://exhost.domain.com/mapi -IISAuthenticationMethods Ntlm,Negotiate,OAuth
  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  datil

  Microsoft Exchange Expert

  • check
    170
    Best Answers
  • thumb_up
    270
    Helpful Votes

  According to
  the empty external URL of client protocols in your test result, it seems that
  you login on the OWA with a internal network, right? If so, please check
  whether the MAPI feature of the mailbox which couldn’t login Outlook
  client is enabled with the command “Get-CASMailbox -Identity <Mailbox
  Name> | fl Identity,MapiHttpEnabled ”, if the MAPI is
  enabled(Empty value represents that the value is same as the OrganizationConfig
  setting) and the Outlook client isn’t supported by MAPI(From the official document:
  Opens a new windowSupportabilityand Prerequisites Opens a new window Opens a new window), you could update your client to the supported
  version:

  

  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  just checked now, i cant

  i had set a firewall rule just now but still cant telnet 433

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  Did you confirm all the Exchange services are properly running?
  Execute on the server, paste the results.

  Powershell

  netstat -ano | find ":443"
  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  

  here u r 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  Have you implemented the commands above?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  i was just about to reply, yup i did

  only on command didt go through 

  Set-OutlookAnywhere -InternalHostname «exhost.domain.com» -InternalClientAuthenticationMethod Ntlm -InternalClientsRequireSsl $true -ExternalHostname «exhost.domain.com» -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $true -IISAuthenticationMethods NTLM,Basic -ssloffloading:$false 

  this one is asking for identity value after implementing, i put the server name didnt work got error saying cannot process argument transformation on parameter identity object not founf on domain controller

  i also added «exocrpc(mail.domain.com)» and didnt work 

  please advice

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  Identity should be in the format of:
  «<ExchangeNetBIOSName>rpc (Default Web Site)»

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  still saying object not found on the dc 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

• 

  ok all commands successful now plus iis restarted 

  still not working 

  i want to add that i didnt install certificates and am running all machines as vm s

  hope this will help

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  @ivan yup it was empty 

  i am using outlook 16 and my servers are both 19

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  Did you try restarting Exchange services?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  yes i did

  ok now its doing something else

  the connection will be done and outlook asks for restart to take effect and right after i got the same message again that says connection is not available

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  Can you please provide a screenshot?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  datil

  Microsoft Exchange Expert

  • check
    170
    Best Answers
  • thumb_up
    270
    Helpful Votes

  Usually Event Viewer could help us troubleshoot some issues we encountered, so you could also view whether there are some errors in it when you encountered the unavailability connection.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  1. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  just checked the event viewer 

  i see DNS client events warning 

  saying officeclient.microsoft.com timed out 

  but it doesnt look like its related to the local dns 

  also i have AAA DNS entry for the IP vs mail sever netbios name

  plus cnames for mail, webmail and autodiscover

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  update

  now its asking for a password but still not logging me in

  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  Have you added UPN suffix to AD?
  Follow this process Opens a new window Opens a new windowto add your domain.com, afterwards at the properties of the user, navigate to the account tab and validate that your user is configured with @domain.com and not @domain.local
  Restart Exchange services, IIS admin and WWW, try again.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  no i didnt add one and the old DC we are trying to replace doesnt have UPN and is working fine 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  I’m not sure if I follow, What old DC? What is working fine?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  ok..here is a brief of what i have 

  i have a DC 2008 and exchange 2010 (on-premises) 

  the 2019 servers i installed them to migrate the current ones, the current DC doesnt have any UPN and its running fine

  i also checked the virtual directories of the current 2010 exchange they look the same with what i have on the 2019 

  the 2019 servers are running as VMware VMs on sandox subnet (no gateway, no internet access)

  thanks

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  Exchange 2019 does not support coexistence with Exchange 2010, as well it does not work in Windows 2008 level domain. Similarly, Exchange 2010 does not support co-existence with 2019.
  You can check the requirements here Opens a new window Opens a new window.
  What is the goal of your project? Migrate existing Exchange 2010 environment to Exchange 2019?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  oh sorry for not being clear 

  the new one will not coexist with the 2010

  also the migration will be done by exporting mailboxes one by one to the new 2019, i now its a lot of work but this is what my manager wants to do

  he wants a fresh exchange server

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  habanero

  Microsoft Exchange Expert

  • check
    302
    Best Answers
  • thumb_up
    526
    Helpful Votes

  You should be aware that all the configuration of user signatures, policies, etc.. will have to be redone manually.
  Before the installation of Exchange 2019, you need to upgrade the domain to the supported level. Exchange 2019 supports Windows 2012 R2.
  You can check the process here Opens a new window Opens a new window.  So all AD DCs would be Windows Server 2012 R2 Standard or Datacenter minimum.
  Afterwards, you install Exchange 2019, however, it is not a supported state and you should not be doing it.
  You might not be able to install it, as the install process will probably detect the directory in an unsupported state.
  If you do want to go to Exchange 2019 in such a way, you would have to install Exchange 2016 first, move the mailboxes manually, reconfigure everything, remove Exchange 2010. Install 2019 and do it manually once again.
  Microsoft has an excellent migration process that, if correctly planned and executed would barely cause any issue to the end user.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  i already have 2019 installed  for DC and prepared

  and web mail is working fine  without problems

  yes i am aware of all the above and going to do it after making this work

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  and i can send/receive emails through webmail  on the 2019 environment 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  thanks to everyone who helped i really appreciate your help

  finally i enabled all autodsicover authentication method and outlook is working now

  best

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Hi saifalmodares​

  actually, i also get same error after connect to exchange server 2019. it’s always asking me to enter the password, but i’t failed to login.

  can you share what configure do you use to solve your problem? and, do you added UPN to AD?

  
  Was this post helpful?
  thumb_up
  thumb_down