Yes, it's a known issue of IIS7.
There are some scripts that change the redirection on root and then reverse the changes on all VDs one by one.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Exchange / Exchweb / Public - all had /owa redirects. Previously I saw Autodiscover had it but I fixed it - I just didnt think to check these other ones. I believe when I changed all these back it resolved that autodiscover issue. I wonder if changing the default website to forward all requests to http://mail.company.com over to https://mail.hytorc.com/owa propogated to everything else. If that is the case and as it was said here - I should not change anything in IIS if I can change it in Exchange Shell, does that mean there is another way to set this type of forwarding in shell?Well everyone. Problem is solved. There might be a few minor hiccups and I have to modify the profile on each outlook install to make it work - but it works. I will be setting that up and seeing if I can figure out an easier way to perhaps package a fix for my users. After that I'm going to dig a bit deeper in everyone's threads here including Rhoderick's blog so I get a better understanding on how everything fits together.
Thanks a lot for everyone's help.
Ultimate the problem lied within some of the sites like Public pointing to /owa for some odd reason (perhaps a change propagated down).
That does not explain why autodiscover was not working. Anyway, it's good to hear the problem is resolved.
↧
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Well everyone. Problem is solved. There might be a few minor hiccups and I have to modify the profile on each outlook install to make it work - but it works. I will be setting that up and seeing if I can figure out an easier way to perhaps package a fix for my users. After that I'm going to dig a bit deeper in everyone's threads here including Rhoderick's blog so I get a better understanding on how everything fits together.
Thanks a lot for everyone's help.
Ultimate the problem lied within some of the sites like Public pointing to /owa for some odd reason (perhaps a change propagated down).
That does not explain why autodiscover was not working. Anyway, it's good to hear the problem is resolved.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
my msstd is set correctly, but I think it maybe best for me to set:
Set-OutlookProvider EXPR -CertPrincipalName noneThis way it doesn't require one in there. I am looking into setting this up and if there are any downsides.
If you're running Outlook 2010 RTM, it may not work for you.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
I think this is the last part of the issue to just get this working. If I create a new profile it nags none stop for a username and password. If I cancel and check it is setup to the cas array address as the server name and teh exchange proxy settings match the above. 'mail.company.com' and msstd: cas01.domain.local with basic authentication.
If I take an existing user getting the old security warning and go into account settings - I can click on repair mailbox. This seems to fix the issue and when they launch Outlook they do not get the nagging credentials you get when creating a new profile.
Odd since they both have the same exchange proxy settings.
This indicate you have ever changed the OA hostname
↧
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Well I do have those settings in mine. When I create a new profile it prompts for credentials and if you get to this screen it shows it all filled out.
What's the subject name of your SSL cert? It's cas01.xxx.local? If not, you need to change your OA hostname or run Set-OutlookProvider
↧
Serious Autodiscover issue after replacing CAS/HUB Server
I removed require SSL and set it to Ignore for Autodiscover. Now autodiscover is completing successfully when I do the Outlook test. I still get the error window but this is progress.
That indicates it's 95% due to cert problem.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Please stop adding and changing things in your environment. There was no need to configure a CAS Array or NLB.
You really want to understand what is going on, fix it -> and only then start to add other complexity.
By any chance are you doing any form of redirect so users do not have to add /OWA or use https:// for the URL?
Cheers,
Rhoderick
Microsoft Premier Field Engineer, Exchange
Blog:http://blogs.technet.com/rmilne Twitter:
LinkedIn:
Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
That's right. Adding CAS array will give you HA but it can't resolve existing problem. This change should be done after the current issue is cleared.
To be 100% (sorry), the CAS Array on its own does not give you HA. We still need some form of load balancing. i think you are inferring that, but I prefer it spelled out for others reading this in the future.Cheers,
Rhoderick
Microsoft Premier Field Engineer, Exchange
Blog:http://blogs.technet.com/rmilne Twitter:
LinkedIn:
Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Of course CAS itself does not provide HA, you need NLB or HLB. And I'm afraid nobody can achieve 100% accuracy in forum.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Nice to hear that the issue was resolved.
You can mark the thread answered, this will help others.
ExchangeGeek
(MCITP,Enterprise Messaging Administrator)
**My posts are provided “AS IS” without warranty of any kind**
↧
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Well everyone. Problem is solved. There might be a few minor hiccups and I have to modify the profile on each outlook install to make it work - but it works. I will be setting that up and seeing if I can figure out an easier way to perhaps package a fix for my users. After that I'm going to dig a bit deeper in everyone's threads here including Rhoderick's blog so I get a better understanding on how everything fits together.
Thanks a lot for everyone's help.
Ultimate the problem lied within some of the sites like Public pointing to /owa for some odd reason (perhaps a change propagated down).
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Hello Help Desk..."
:)
Cheers,
Rhoderick
Microsoft Premier Field Engineer, Exchange
Blog:Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Yes - that was fixed. Remember I do Exchange and not Outlook, so when it say it prompts, its really the Auth prompt coming from Exchange. The save password is kind of OK, but what happens when the password gets changed at the end of the month....
Cheers,
Rhoderick
Microsoft Premier Field Engineer, Exchange
Blog:http://blogs.technet.com/rmilne Twitter:
LinkedIn:
Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
I am leaving it on Basic for now for the sake of just resolving the problem. On the brightside I learned a lot about how things are setup and to not mess around in IIS and do everything in Exchange if at all possible. Still not 100% yet but I'm going to start making changes to local workstations and see if I have more issues.
It just prompts for the password the first attempt.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
"Hello Help Desk..."The save password is kind of OK, but what happens when the password gets changed at the end of the month....
↧
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Yes - that was fixed. Remember I do Exchange and not Outlook, so when it say it prompts, its really the Auth prompt coming from Exchange. The save password is kind of OK, but what happens when the password gets changed at the end of the month....
Cheers,
Rhoderick
Microsoft Premier Field Engineer, Exchange
Blog:Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Rhoderick,
Internally I have had Basic setup in the past and never had prompts for credentials. I will check out the link to see if it works to just switch to NTLM. That would obviously be ideal!
Well this article is explaining why basic was working before (since Outlook seems to save the credentials once you put it in once). I'll read through. Thanks
↧
Serious Autodiscover issue after replacing CAS/HUB Server
Rhoderick,
Internally I have had Basic setup in the past and never had prompts for credentials. I will check out the link to see if it works to just switch to NTLM. That would obviously be ideal!
↧
Serious Autodiscover issue after replacing CAS/HUB Server
my msstd is set correctly, but I think it maybe best for me to set:
Set-OutlookProvider EXPR -CertPrincipalName noneThis way it doesn't require one in there. I am looking into setting this up and if there are any downsides.
http://blogs.technet.com/b/exchange/archive/2008/09/29/3406352.aspx
Its a very good article on this.
ExchangeGeek
(MCITP,Enterprise Messaging Administrator)
**My posts are provided “AS IS” without warranty of any kind**
↧
↧
Serious Autodiscover issue after replacing CAS/HUB Server
@ExchangeGeek - why are you showing him an OA screen with Basic auth and expecting no credential prompts? Also if Centixo does not have a wildcard cert that is not the right value to put in the MSSTD field. As Martina already said be carefuly about making changes in IIS - they will be lost.....
Basic auth will always prompt - use NTLM instead.
http://blogs.technet.com/b/exchange/archive/2010/07/16/3410408.aspx
Make the change, restartIIS then re-test and advise please Centixo. Though your users will be interrupted if you run IISRESET. You could recycle the AutoD apppool, but iisreset is simpler to explain :)
Cheers,
Rhoderick
Microsoft Premier Field Engineer, Exchange
Blog:Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
my msstd is set correctly, but I think it maybe best for me to set:
Set-OutlookProvider EXPR -CertPrincipalName none
This way it doesn't require one in there. I am looking into setting this up and if there are any downsides.
↧
Serious Autodiscover issue after replacing CAS/HUB Server
I think this is the last part of the issue to just get this working. If I create a new profile it nags none stop for a username and password. If I cancel and check it is setup to the cas array address as the server name and teh exchange proxy settings match the above. 'mail.company.com' and msstd: cas01.domain.local with basic authentication.
If I take an existing user getting the old security warning and go into account settings - I can click on repair mailbox. This seems to fix the issue and when they launch Outlook they do not get the nagging credentials you get when creating a new profile.
Odd since they both have the same exchange proxy settings.
Set-OutlookProvider EXPR -CertPrincipalName msstd:mail.company.com
This will do the trick.ExchangeGeek
(MCITP,Enterprise Messaging Administrator)
**My posts are provided “AS IS” without warranty of any kind**
↧
