Link to home
Start Free TrialLog in
Avatar of jtreeves72
jtreeves72

asked on

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.
ASKER CERTIFIED SOLUTION
Avatar of Mestha
Mestha
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jtreeves72
jtreeves72

ASKER

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 -
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 -
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 -