GRitchie Posted January 28, 2016 Posted January 28, 2016 When I run a test on Microsoft Test Connectivity I get given the following error. I am currently having a few teething issues with Exchange / Outlook, so I assume this is related. Any ideas on a fix? I'm not overly confident in Exchange, so as much help as you can give would be great!
silvestre Posted January 28, 2016 Posted January 28, 2016 Can you expand on what problems you are having with exchange / outlook also version of exchange server and service packs
GRitchie Posted January 28, 2016 Author Posted January 28, 2016 Outlook main problem is that contacts aren't showing properly in distribution groups. Also, outlook won't autodiscover on current 2010 clients (unless I reinstall office). It doesn't autodiscover outside of the LAN, it also doesn't autodiscover on 2016. On top of that, it doesn't work on the LAN on mobiles?
silvestre Posted January 28, 2016 Posted January 28, 2016 What version of Exchange do you have? The problems you mentioned was it working correctly before? Did you make any changes to the exchange server? Upgrades? The reason for me asking if it was working earlier is because Exchange need to be configured Autodiscover Service Both internally and externally on your DNS.
GRitchie Posted January 28, 2016 Author Posted January 28, 2016 It's never worked properly since I set it up, just got most staff on the Web App for now! It's Exchange 2013 No changes, aside from the bog standard Windows updates as and when they come!
Jonesminor Posted January 28, 2016 Posted January 28, 2016 re auto discover.. how is your DNS configured for accessing exchange? In powershell.. Get-ActiveSyncVirtualDirectory | fl internalurl,externalurl Get-AutoDiscoverVirtualDirectory | fl internalurl,externalurl Get-ECPVirtualDirectory | fl internalurl,externalurl Get-OabVirtualDirectory | fl internalurl,externalurl Get-WebServicesVirtualDirectory | fl internalurl,externalurl Make sure these are correct and can be resolved internally. --
GRitchie Posted January 28, 2016 Author Posted January 28, 2016 Ran those: Get-ActiveSyncVirtualDirectory | fl internalurl,externalurl Internal and External = http://mail.domainname.co.uk/Microsoft-Server-ActiveSync Get-AutoDiscoverVirtualDirectory | fl internalurl,externalurl Internal and External = blank Get-ECPVirtualDirectory | fl internalurl,externalurl Internal and External = http://mail.domainname.co.uk/ECP Get-OabVirtualDirectory | fl internalurl,externalurl Internal and External = http://mail.domainname.co.uk/OAB Get-WebServicesVirtualDirectory | fl internalurl,externalurl Internal and External = http://mail.domainname.co.uk/exchange.asmx
silvestre Posted January 28, 2016 Posted January 28, 2016 check out this article Configure External and Internal URL in Exchange 2013 You will need to make changes to your server from step 3.
GRitchie Posted January 28, 2016 Author Posted January 28, 2016 Done that, however Get-AutoDiscoverVirtualDirectory | fl internalurl,externalurl still returns blank?
silvestre Posted January 28, 2016 Posted January 28, 2016 Did you run this command from step 7 in Exchange powershell? ( not the normal powershell) [PS] c:\windows\system32>Set-ClientAccessServer -Identity MBG-MAIL -AutoDiscoverServiceInternalUri https://autodiscover.mustbegeek.com/Autodiscover/Autodiscover.xml
silvestre Posted January 28, 2016 Posted January 28, 2016 Run this Get-AutodiscoverVirtualDirectory -server EXCHANGE | Set-AutodiscoverVirtualDirectory -ExternalUrl ‘https://mail.DOMAIN.ca/Autodiscover/Autodiscover.xml’ -InternalUrl ‘https://mail.DOMAIN.ca/Autodiscover/Autodiscover.xml’ and then check Get-AutoDiscoverVirtualDirectory | fl internalurl,externalurl
GRitchie Posted January 28, 2016 Author Posted January 28, 2016 Error: A parameter cannot be found that matches parameter name 'ExternalUrl' How I hate Exchange shell red writing!!
silvestre Posted January 28, 2016 Posted January 28, 2016 Are your internal URL's similar to the external URL's,
silvestre Posted January 28, 2016 Posted January 28, 2016 Try running this and check again Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri “https://mail.domain.com/Autodiscover/Autodiscover.xml”
GRitchie Posted January 28, 2016 Author Posted January 28, 2016 Not sure what you mean @silvestre To your second comment, that command worked
GRitchie Posted January 28, 2016 Author Posted January 28, 2016 However it hasn't worked when I re-run Get-AutoDiscoverVirtualDirectory | fl internalurl,externalurl
silvestre Posted January 28, 2016 Posted January 28, 2016 Get-ClientAccessServer casserver1 | fl *InternalUri*
GRitchie Posted January 28, 2016 Author Posted January 28, 2016 replcaed casserver1 with CPS-MSX (servername) and that's now returned the correct autodiscover path
silvestre Posted January 28, 2016 Posted January 28, 2016 Can you run this again I have replace InternalUrl with InternalUri and same for external. Get-AutodiscoverVirtualDirectory -server EXCHANGE | Set-AutodiscoverVirtualDirectory -ExternalUri ‘https://mail.DOMAIN.ca/Autodiscover/Autodiscover.xml’ -InternalUri ‘https://mail.DOMAIN.ca/Autodiscover/Autodiscover.xml’ and then check Get-AutoDiscoverVirtualDirectory | fl internalurl,externalurl
GRitchie Posted January 28, 2016 Author Posted January 28, 2016 Same error, but for parameter 'ExtranlUri'
silvestre Posted January 28, 2016 Posted January 28, 2016 Can you test out with a client if it autodiscovers the exchange server.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now