From an architectural standpoint, a public folder server is almost identical to a mailbox server. The only difference is that the server's stores contain public folders rather than mailboxes.
Generally speaking, public folder servers aren't usually as resource-intensive as mailbox servers, because the information within the public folders isn't as dynamic (that's not to say that public folders are static).
If a server is acting solely as a public folder server, you can generally get away with lower-end hardware than what you would need to use for your mailbox servers.
While disk capacity is almost always an issue with public folder servers, using multiple RAID arrays for better performance is probably going to be overkill.
A PRIMER ON SERVER ROLES AND EXCHANGE HARDWARE
Part 1: Microsoft's hardware recommendations
Part 2: Server roles
Part 3: Mail servers
Part 4: Public folder servers
Part 5: Bridgehead servers
Part 6: Gateway servers
Part 7: Front-end servers
Part 8: Conclusion
Part 9: Related links
|ABOUT THE AUTHOR:|
| Brien M. Posey, MCSE
Brien is a Microsoft Most Valuable Professional for his work with Windows 2000 Server and IIS. He has served as CIO for a nationwide chain of hospitals and was once in charge of IT security for Fort Knox. As a freelance technical writer, he has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies.
Copyright 2005 TechTarget