Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Preparing Exchange Server 2003 for OWA

Preparing Exchange Server 2003 for OWA

Ratings: (0)|Views: 72|Likes:
Published by vinay kumar

More info:

Published by: vinay kumar on Apr 27, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Preparing Exchange Server 2003 for OWA
Your Exchange Server 2003 generally behaves as Backend Server and every user hasHTTP as an allowed protocol. So you do not have to configure anything on your BackendServers unless you want to prevent some of your users from accessing their mailboxusing OWA. This can be done quite easily via Active Directory Users and Computers inthe user properties.
Figure 1: Enabling OWA for a user
The next step is installing and configuring your Frontend Server. The easiest way to dothis is to install it as a second Exchange Server in your organization. After that weshould enable it to act as a Frontend Server. This can be generally done in the propertiesof your Exchange Server in Exchange System Manager.
Figure 2: Configuring a Frontend Server
If we choose this configuration the server changes from using the DAVEx process (to actas Backend Server) to the ExProx process (acting as Frontend Server). The next step is toreboot the server to make the changes take effect.Then we should go through the following steps to make the Frontend Server a genuineFrontend by disabling all unnessecary services. On your Frontend Server you must havethe following services running, every other service may be stopped without any trouble.
Exchange System Attendant
Exchange Routing EngineYou really do not need to run the Exchange Information Store, because there should not be any public folders or mailboxes on your Frontend Server. The best practice is todismount and delete all databases on your server and then disable the ExchangeInformation Store Service.
After you have successfully placed this server in the perimeter network (also known asDMZ) we now have to configure the appropriate ports on the firewall(s) to make our server run.On the intranet firewall (which connects the DMZ and the internal network) we have toopen the following ports:
For Exchange Communication:
Port 80 for HTTP
Port 691 for Link State Algorithm routing protocol
For Active Directory communication:
Port 389 for LDAP (TCP and UDP)
Port 3268 for Global Catalog Server LDAP (TCP)
Port 88 for Kerberos Authentication (TCP and UDP)
: You should now configure the DSAccess service for perimeter networks on your Frontend Server. At first you should disable the check for available disk space atnetlogon by using RPC. This can be done by changing the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDSAccessRegistry Value: DisableNetlogonCheck Value Type: REG_DWORDValue Data: 1
In addition to this you should prevent DSAccess from pinging domain controllers. Thiscan be done by creating the following key on your Frontend Server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeDSAccessRegistry Value: LdapKeepAliveSecsValue Type: REG_DWORDValue Data: 0
Then you should configure your Exchange Frontend Server to connect to the DC and GCyou want by editing the server properties in Exchange System Manager.
For DNS communication:
Port 53 for DNS (TCP and UDP)
For RPC communication:
Port 135 – RPC endpoint mapper (TCP)
Ports 1024 and higher for RPC servicesNote:
You can limit RPCs across the firewall by editing the registry of all your DCs. Youshould now change the registry setting of the following key:

Activity (7)

You've already reviewed this. Edit your review.
1 hundred reads
Bharat Raj liked this
tech1 liked this
Sanjay Kambli liked this
batalia liked this
it_man liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->