HTTPS Configuration question

Question

I've just been handed an iWS6.1 server and need to setup HTTPS. That's easy, not much different than ldap, messaging server and Portal.
But my question is "How should I provide the HTTPS service?" From a quick read of the docs, I could do 1 of 2 things.
1. Add a https listener to the current virtual web server: www.xyz.com
2. Define a new virtual server and call it wwws.xyz.com
The https service would be used to authenticate users and present pages under www.xyz.com. The big advantage I see to using wwws.xyz.com is that it would force developers to put all their https dependant code in one spot, but I could be mistaken on that assumption.
Thanks,
Roger S.

Answer 1

First of all, there is nothing wrong with letting Outlook connect via HTTP internally as well. This is actually the direction Exchange is going (in fact, in Exchange 2013 all Outlook connectivity takes place via Outlook Anywhere).
Second, it's a fallback mechanism and all that the option does is either attempt to connect first via RPC and then HTTP or first HTTP and then RPC.
Third, your Internet connection speed is also irrelevant in this case since it is your network adapter speed which counts and that is most likely your local LAN speed and even higher than that.
Anyway, to answer your question; Yes, what Outlook considers slow is configurable via the Registry.
However, since the full answer is a bit more complex, it is a bit hard to explain it here so I turned it into a blog post:
http://www.howto-outlook.com/howto/outlookanywherefastslow.htm
Robert Sparnaaij
[MVP-Outlook]
Outlook guides and more: HowTo-Outlook.com
Outlook Quick Tips: MSOutlook.info