Microsoft Exchange 2003 - Clients
Introduction to Exchange 2003 - Clients
These days when it comes to collecting your Exchange email, you are spoilt for choice. Exchange 2003 clients seem to grow by the week, firstly there is the Outlook 200x family of MAPI clients, then there is Outlook Express with POP3, IMAP4 (and NNTP). Perhaps the biggest increase is in OWA (Outlook Web Access). Lastly comes a technology with a future - OMA (Mobile Access).
Topics for Exchange 2003 Clients
In a nutshell, OWA in Exchange 2003 supports the full Outlook feature set. A sign that this version of the web client has come of age is that people are now complaining that OWA has too many features!
To connect to the Exchange 2003 server, simply type
I particularly appreciate having the Rules Wizard and a the spell checker. The new OWA, looks and feels like Outlook. You even have navigation settings and preview - now called Reading Pane. Best of all, a right-click now produces the short cut menu, just like other Windows programs.
It makes sense for administrators to configure and publicise the use of UPN (user principle names) so that OWA users can logon with their email address. For those concerned about the security of their messages or their signature OWA now supports S/MIME encryption and signature verification.
There also improvements to the calendar so that you can reply to meeting requests and receive reminders using OWA.
Note: Select the Premier version of OWA unless you have a very old browser.
Here is a free tool to monitor your Exchange Server. Download and install the utility, then inspect your mail queues, monitor the Exchange server's memory, confirm there is enough disk space and check the CPU utilization.
This is the real deal - there is no catch. SolarWinds provides this fully-functioning freebie, as part of their commitment to supporting the network management community.
Active Directory Users and Computers
As with previous versions of Exchange, OWA is available to each user by default. To check the settings, launch Active Directory Users and Computers, navigate to the User object then examine the Exchange features tab. See here.
Outlook 2003 leverages Kerberos security to decrease password theft. OWA clients can take advantage of Kerberos as it operates at both front-end and back-end servers.
Cached mode creates a local data file that Outlook uses for all foreground activity. It then contacts the Exchange server in the background. Exchange / Outlook traffic is compressed on low bandwidth connections. What is more if server connection is lost, Outlook just carries without hesitation until the server comes back on line.
To configure the Outlook 2003 client, navigate to the Control Panel, Mail icon. Select setting to connect to Exchange 2003.
There has been a technical development in that Outlook 2003 (the MAPI clients), can now use RPC over HTTP, Microsoft says this removes the need to use a VPN. The port number for this arrangement are Port 80 front-end servers in the de-military zone. While on the back-end server, you need to open port 593 (End point mapper) and ports 6001,2 and 4 for Exchange. You may also need to edit the registry on the Proxy server to reflect the use of these ports, here is the relevant registry setting:
Note you cannot leave FQDN, you must enter a real value.
Import users from a spreadsheet, complete with their mailbox. Just provide a list of the users with the fields in the top row, and save as .csv file. Then launch this FREE utility, match your Exchange fields with AD's attributes, click and import the users. Optionally, you can provide the name of the OU where the new mailboxes will be born.
OWA has arrived and is here to stay. I am certain that in Exchange 2003 you can find the thin client / browser combination to suit your organization.
If you like this page then please share it with your friends