Click More Settings. On Outgoing Server tab, enable outgoing authentication. I'm having the same trouble adding my new NBN account to outlook 2016 and followed your previous advice but when I click next I get a reoccuring loop asking for the password to the bigpond server. Setting up Bigpond email in Outlook 2016. Jul 05, 2016  If you changed your autodiscover.buildingexcellentschools.org to be a CNAME that points directly to autodiscover.outlook.com then this should prevent that popup from happening as *.outlook.com is part of the default Outlook whitelist.

Hello, we have installed an Loadmaster HA and 3 MS Exchange 2016 Server. The Loadmaster is configured via Exchange 2016 HTTPS Reencrypted Template and all virtual Services works fine. Only if I try to config Outlook Clients via Autodiscover, I get a Redirect Warning Message. If I disable the 'Exchange 2016 HTTPS Reencrypted - HTTP Redirect' Virtual Service, no Redirect Warning Message appears. But now, if an User types the http-Adress in the browser to connect OWA, the browser shows 'Connection Failed'. How can I modify the Virtual Services, that all works correct. Thanks Thomas.

When I opened iMessage the message vanished. I checked on my phone and there was no record of of the message. I checked on a macbook and I do see that two iMessages were sent, and neither of these shows up on the phone and pad. Why isnt my imessage working for text messages on mac. Setting up iMessage to receive messages on your iPhone, iPad, and Mac shouldn't be rocket science, but it's not exactly the easiest thing to get working properly. With iMessage on your Mac, you can send unlimited messages to any Mac, iPhone, iPad and iPod user who uses iMessage. However, many users encountered the issue of Mac iMessage not working sometimes. Well, what is the mean of iMessage not working on Mac, it may stucking on a display, it may won’t receiving messages, or it may saying Not. There are lots of reasons why iMessage can stop working: it could be an issue with Apple's iMessage server, a problem with the Messages app, or your settings could need adjusting. If you’ve been trying to send iMessages using your iPhone and all of your messages are suddenly appearing in green bubbles, then iMessage isn’t working correctly on your iPhone. In this article, I’ll explain what iMessage is and how to diagnose and fix problems with iMessage on your iPhone, iPad, and iPod.

I manage a server running SBS 2011 and Exchange Server 2010. I've just had my first run-in with the joys of Outlook 2016 and needing properly configured autodiscover. I say that I manage the server, but I'm really in training, and by training I mean i've had to learn just about everything on my own.

I need some assistance getting autodiscover to work properly. My boss says it is, but if it was outlook 2016 would be working properly, so I don't think it is. I've found some tutorials on how to do it using the shell, but it just says the command can't be found. Any and all help would be greatly appreciated, as I am completely lost.

I cant paste any urls, because 'my account isnt activated' and they won't activate it for me. Regardless, when i type in that code i get back the autodiscover.xml except the full url i cant find and ssl certificate on the certification authority and the error i get back from the exrca basically says that it cant find/there isnt a ssl certificate.

So i'm guessing i'll have to make one then? Hey Caleb, I am not exactly sure what you mean by 'my account isn't activated'.

Where are you pasting these commands? We would need the entire output from exrca.com to be sure, but if it says you don't have an SSL that could actually be caused by a number of reasons. First, is that you don't have a certificate from a trusted 3rd party authority. You can check what certificates you have installed by running Get-ExchangeCertificate from the Exchange Management Shell. Second, you don't have any DNS records for autodiscover with your external DNS provider, or, you have a wildcard DNS entry that is directing autodiscover requests to the wrong place. I often see these wildcard 'catch-all' DNS entries that redirect all misspellings to where your website is hosted causing a failure. Third, Autodiscover can't find an autodiscover A record or SRV record and it is defaulting back to the root domain which is likely being sent to your hosting company for your website.

This can cause a failure. Fourth, you have an SSL certificate but it is not enable for Exchange Web Services (IIS). If you can copy the whole EXRCA.COM output here we can pinpoint the exact failure. Find me on Find me on.

Hey Caleb, What's the command you are trying to run that can't be found? Keep in mind any Exchange commands need to be run from the Exchange Management Shell. To test whether autodiscover is working I recommend using. Its a site Microsoft provides that has a ton of different Exchange tests, including Autodiscover. This is a good starting point to tell you whether it is working or not.