Thanks for the replies, the issue is only in Outlook as the users can access their mailbox via OWA.ĪutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-ServiceĪutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596ĮXCHSERVER is 2010, and EXCHSERVER01 is 2013Īnother interesting issue I observed is, when I power down my Exchange 2010 server some clients who's Outlook works fine are unable to open outlook when exchange 2010 is powered off even though nothing exists on this server anymore.
Get-ClientAccessServer | Select Identity,Name,*Autodiscover* In Exchange side, please run the following command: Please collect the information in the Log tab and Results tab. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service. Open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar. Please follow the steps below to check autodiscover service for the "Exchange server unavailable" users : If users can access OWA but can’t connect to Exchange server from Outlook, the issue may be related to autodiscover service which is used to get Exchange services for Outlook client. If users in this site can’t access mailbox from both OWA and Outlook, please collect any event logs in Exchange server for further analysis. Please check whether these problematic users can access their mailboxes from Outlook Web App (OWA). The site that Exchange is in we have 2 DCs and both are GCs as well.
#Musica anni 80 90 download windows
What should I test for or check? I verified the remote site DC is set as a "GC" in AD Sites and Services so what is the issue? The remote site is a Windows 2003 R2 server and our domain functionality is 2013. My question here is, why can't this client computer detect the GC? I want to fix the issue at the core and not use registry hacks to get Outlook to work. The only way I can get the client Outlook to work is if I manually add "DS Server" in the registry ( ) and point to the DC that is local to the Exchange I can resolve the server internally to the internal IP (traceroute and ping) from the affected client. We use Split DNS configuration for Exchange as recommended by MS. When I try to re-create their profile, I am unable to "autodiscover" it. The message they get is "Exchange server unavailable". My issue is that one particular site that has AD/DNS, some clients are unable to connect to Exchange using Outlook. My end users are a mix of Office 2010 SP1 and Office 2013 and we have various remote sites that have a local AD/DNS/DHCP server against which the remote clients authenticate, etc. I recently upgraded my environment from Exchange 2010 SP2 to Exchange 2013 SP1 CU5.
0 kommentar(er)
