Hi, We have the situation where we are trying to move from a single BE A/P cluster, to 2 FE (NLB'd), with the single BE A/P cluster. The only question I have is regarding SSL. We have never published OWA externally before. By default we obviously have the website: http://nlb name/exchange How do people normally publish their OWA sites externally... do people give it a completely unique subdomain type name like: https://owa.company.com/exchange Or do people simply add a virtual directory onto their existing company website called /exchange which then points to their OWA server? I am really confused about all this.. Also when we request our SSL certificate, does the common name have to contain the /exchange etc?? Any help would be most appreciated?
On Tue, 1 Apr 2008 01:02:01 -0700, UselessUser wrote: > How do people normally publish their OWA sites externally... do people give > it a completely unique subdomain type name like: > > https://owa.company.com/exchange I've seen companies doing like this. > Or do people simply add a virtual directory onto their existing company > website called /exchange which then points to their OWA server? I am really > confused about all this.. I've also seen people doing this. It depends on your company and what you want to do with the web access. Both ways are possible, just a different way to publish (and if you have a solution to publish subdirectories to different servers.. isa could do..) > Also when we request our SSL certificate, does the common name have to > contain the /exchange etc?? It's just the domain part. eg. owa.company.com the /exchange part can be ommitted. bg christoph
