Making an internal web site visible to the world

Preface: I'm an absolute web neophyte. I believe this is a fairly easy one to answer, but I don't have time to do all the research and trial-and-error.

We upgraded to a new Exchange 2010 server last summer, but I still have my old (Exch20003) box running mainly as an NTLM box, but also still hosting a couple web pages under the same default directory (inetpub\wwwroot\....)  These pages were publicly visible by virtue of the OWA url (the directories were simply appended to the main url - ie http:\\\library\ ) How can I 'publish' those web pages without revealing the
Who is Participating?
simonlimonConnect With a Mentor Commented:
Without revealing that it is on a different server, you mean?

You can do that with web publishing rules, you just have to publish the proper path to a different server. That also means that you shouldn't use the wildcard for the web publishing of the owa website?

Example, when you published the OWA website, the paths included are "/owa, /exchpub, /ews, ..."

You can create a new website, pointing to a new web server and using the paths on the "old" server which that application uses.

But be aware, you cannot mix authentication methods on the same port and on the same IP, or listener.

I mean that you cannot publish a public anonymous web site on the same IP and listener as the one that requires preauthentication.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.