Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 776
  • Last Modified:

TSWeb and OWA redirect(s) on new server install

I'm in the cleanup stage of a 2000 Std  -> SBS 2003 server migration, and have a few remaining issues with OWA and TSWeb access setup.

Prior working environment on the old 2000 server, was the ability to open IE7 and type owa.domain.com and terminal.domain.com, and get to Outlook Web Access and a TS (RDP) login screen respectively. Without having to add the "/exchange" or "/tsweb" switch on the URL address bar to get to the respective application. This feature (no /exchange, etc switch required) is required to work the same on the new server.

Could use some assistance on how to do this feature setup on the new SBS 2003 server. At this point I've done a right-click on "Default Web Site" folder -> Home Directory tab -> a) Choose redirection to a url - b) Type /exchange in the text box - c) Check the "directory under this one" radio button. This eliminated the requirement for the /exchange switch, but I now get directed to the OWA logon page when I put in terminal.domain.com and do not use the appropriate switch (/tsweb  or /remote)

If someone could clarify where I need to be working to accomplish my objective - would appreciate - thanks.
0
jtreeves72
Asked:
jtreeves72
  • 3
1 Solution
 
MesthaCommented:
There are only two ways that I can think that was being done.
1. Two seperate web sites.
2. A redirect based on the URL used to access the site in the default page for the site.

The redirect method that you ahve done is not domain specific, it is site specific, so it wouldn't matter if you accessed the site with http://server/ or http://123.123.123.123/ it would be redirected.

If are you are going to use SSL (and if not, why not) then you only have the option of two seperate web sites because SSL is site specific. That will also require two different external IP addresses because neither feature reacts well to using laternative ports.

You need to look at the original server and see how that was configured, which may well save you some time.

Simon.
0
 
jtreeves72Author Commented:
Thanks Simon for responding - Will be on customer site tomorrow and will take a look at the old server and see what I can decipher - will followup on what I find -
0
 
jtreeves72Author Commented:
Wanted to provide a quick update. I haven't had the opportunity to get back to the customer site to check their web configurations. I will update when I have add'l information -
0
 
jtreeves72Author Commented:
Left this to where the customer was appending the /remote to get to their RWW site URL.  This was an acceptable solution for the customer so did not re-engage in any add'l effort on this issue -
0
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.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now