Re: Owa issues

  • From: "Kern, Tom" <tkern@xxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 12 Jul 2005 18:49:32 -0400

In exchange 2k, the home dir points to the M: drive(i know this is no longer 
used in ex2k3).
what can i do so users can just point to the fqdn w/o specifying the exchange 
dir?
thanks

-----Original Message-----
From: A. Michael Salim [mailto:msalim@xxxxxxxxxxxx]
Sent: Tuesday, July 12, 2005 6:22 PM
To: [ExchangeList]
Subject: [exchangelist] Re: Owa issues


http://www.MSExchange.org/

Hi,

> Hi, I just installed my first Exchange2k3 server and I'm confused about owa.
> In exchange 2k, all I had to do was point my browser to the exhange ip or dns 
> name and it worked.
> In exchange2k3, I get "page under construction".
> Is there an additional setting I need to click?
> I'm not running a front end server.
> Just one exchange2k3 on win2k3 sp 1(for both win and exchange).

If you did the standard install you need to specify the /Exchange virtual
directory in the URL i.e. add /Exchange at the end like so:

https://.../Exchange

Best regards
Mike


------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as: 
tkern@xxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx


Other related posts: