Solved

Exchange Front End Backend Server Setup question

Posted on 2010-08-28
2
448 Views
Last Modified: 2012-05-10
I am planning on making one of my exchange servers (2003 sp2) a front end server. Currently it is hosting public folders (very small 400mb) and also is responsible  for the offline address book, generating the offline address book, schedule+free busy folders, organizion forms folder, and the recipient update service as well.
I am in the process of moving the public folders over to another exchange machine now. The sever to become the front end also does NOT host any mailboxes.
I am going to be deploying it using the Front-End and Back-End Topology with a Front-End Server Behind a Firewall.

So, my question is: can I allow the front end server to continue to host the offline address book, schedule+free busy folder, organization forms folder, and the recipient update service without any issues or risks?


thanks in advance for any advice.
0
Comment
Question by:blkstrim
2 Comments
 
LVL 15

Accepted Solution

by:
GreatVargas earned 500 total points
ID: 33551120
So, my question is: can I allow the front end server to continue to host the offline address book, schedule+free busy folder, organization forms folder, and the recipient update service without any issues or risks?

answer: well the answer is no.. you should change the OAB generation server to your back end server, you should replicate all public folders to your back end server, and the best is to delete the public folder database on the front end... deleting the public folder database also implies that the system ublic folders (schedule free busy and organization forms included) stay only on the back end server.. as for the recipient update service the recommendation is the same that for the OAB... change it to the back end..

http://technet.microsoft.com/en-us/library/aa996980(EXCHG.65).aspx

http://technet.microsoft.com/en-us/library/aa997436(EXCHG.65).aspx

check this:
Dismount and delete stores if necessary:

If you are not running SMTP, dismount and delete all mailbox stores.

If you are running SMTP, leave a mailbox store mounted, but make sure the mailbox store does not contain any mailboxes. If you receive large amounts of external e-mail for public folders, you can mount a public store, as this will improve mail delivery to public folders.

so if you are using front end, not only for external client access, but also to smtp, you should keep mailbox databases.. if not delete it...

front end servers are designed to be on perimeter networks and should not contain any user or domain information, such as recipient policies and OAB
0
 

Author Comment

by:blkstrim
ID: 33559012
thanks for the information. this is perfect. Thanks again
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Suggested Solutions

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video discusses moving either the default database or any database to a new volume.

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now