• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 253
  • Last Modified:

Configuring OWA in Exchange 2003

We are currently using a single Microsoft Windows 2003 Standard Server in conjunction with Exchange Server 2003. Everything is working fine, but I have been asked to provide remote access for some users, to enable them to access e-mail when in other locations.
I have read about OWA, but have never set this up before. Does anyone know of any documents which provide step by step instructions suitable for first time users, like me?
0
nigelbeatson
Asked:
nigelbeatson
  • 4
  • 3
  • 3
  • +1
2 Solutions
 
e_vanheelCommented:
http://www.verisign.com/support/ssl-certificates-support/install-ssl-certificate.html

For help on installing a certificate so the email is secure across the web.  You don't need to purchase the certificate from Verisign, they just have good step-by-step documentation on how to do it.
0
 
SembeeCommented:
OWA is configured by default.
There is nothing to setup.
If you browse to http://servername/exchange then you should find that you can access OWA.

The only additional configuration that you should make is to add an SSL certificate as already outlined, which will make the server secure by not sending everything across in the clear.

Everything else is outside of Exchange -

- opening the relevant ports on your firewall (443 if you are using SSL)
- setting up a host name in your DNS for OWA. If you are receiving email directly by SMTP then you may already have a host name that you can use - mail.domain.com for example.

Simon.
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
nigelbeatsonAuthor Commented:
wow, there are so many things here! Just to get things clear, firstly if we do not want to use SSL certificates, can we just access our existing server already by logging on using a browser pointed at http://ourservername/exchange?
For basic connections (without SSL) what port do we need to open up in our firewall?
I presume it would be a good idea to get this working first, before applying SSL security certificates.
If we do not purchase an SSL certificate, where do we get one from.
We do receive e-mail directly by SMTP, so what format does a DNS record need to be in for OWA.
It seems their is nothing to do on our server, other than opening up a port on the firewall, but what name do we use for our server? I am a little confused, as I am unsure how our locally named server would be visible for remote access. ie do we use the IP address, or the actual server name.
0
 
e_vanheelCommented:
OWA is just a website.  You will need to insure that users can gain access via port 80.  

You will need to change your firewall so a user can goto a URL like: http://webmail.yourco.com/exchange and it will route / allow traffic to goto the internal address.

Once you have that working the only additional change will be opening port 443 for the SSL connection.
0
 
nigelbeatsonAuthor Commented:
Thankyou for your help. That seems to be a little clearer now, but what about the security certificates?
Do we need to purchase those, or are is there part and parcel of Exchange/2003 Server?
0
 
e_vanheelCommented:
You can purchase them from many vendors or depending on your environment create your own if you have a Certificate Authority (CA).  The easiest way is to just buy one.  They are not that expensive for a basic web server cert.

I would get the "un-secure" OWA working first.  You can purchase the SSL cert and just not install it until you have the rest working.
0
 
SembeeCommented:
I always recommend purchasing certificates for OWA. You don't have to spend US$400 with Verisign, you can get them for $20 a year from somewhere like http://www.certificatesforexchange.com, GoDaddy or RapidSSL (GeoTrust).

I also tend to suggest testing it inside on http first, but I never open port 80 to the world from an inside network - even for testing.

Simon.
0
 
nigelbeatsonAuthor Commented:
Thanks Simon,

$20 per year sounds OK for the certificate, is that per mailbox, or can we use the same certificate for any remote user?

Your last comment confused me a little. How can we test it out thoroughly using http, if we do not open up a port in our firewall?
0
 
SembeeCommented:
SSL certificates are per server, not per mailbox.
You can test the functionality of Exchange on http inside the firewall. Browse to http://servername/exchange and see if it works. There is no reason why it shouldn't.
If it doesn't work inside then it will not work outside. Exchange doesn't care where you connect from.

Simon.
0
 
nigelbeatsonAuthor Commented:
Thanks everyone for your assistance.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

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