Mixed Exchange 2003 \exchange 2007 environment. Autodiscover url is set to mail.company.com. The cert has autodiscover.company.com as well, but someone configured autodiscover url to use mail.company.com. Split DNS, mail.comapny.com resolved to ISA externally and internally to CAS servers DNS round robin. There was no SRV record has been created for autodiscover. Created it recently and since then users connected to LAN are seeing the dreaded pop up "Allow this website to configure xxx@xx.xom serevr settings" Click allow. The internal users should connect to autodiscover via SCP right? 1. Test-outlookwebservices - autodiscover tested successfully 2. Test-emailAutoConfiguration shows it can contact autodiscover via scp and was successful. what is causing the pop up in Outlook for internal clients?

Yes internal users should be using SCP. However keep in mind that internal clients can sometimes connect over outlook anywhere if you have the outlook anywhere settings in outlook. Go to one of the users who go this pop up and ctrl + right click his outlook icon on the bottom right tray and select connection status, make sure he's actually connecting over TCP and not HTTP. Outlook Anywhere Settings Outlook, uncheck both. On fast networks, connect using HTTP first, then connect using TCP On slow networks, connect using HTTP first, then connect using TCPJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Creating the SCR record is the cause of the popup. You should remove it. If you have a zone for domain.com and have clients that are not on the domain, then you could just add autodiscover to the zone. You only need to use something other than autodiscover (so SRV, redirect etc) if autodiscover.example.com is not in your SSL certificate. That isn't the case here, so you are creating configurations that you don't need. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Yes, that's what it turned out to be. Thanks so much.

I totally agree with you, but I have inherited this environment and that is how it was configured. I am working on correcting many of these issues.