Let me start out by saying that I’ve dabbled with Exchange, but I’m definitely not a master.
I’m volunteering for a medical clinic (non-profit). There’s about 60 users who are split into 4 different groups that due to compliance and the organizational structure need to be completely separate
. I'm talking separate login domains, different GAL, no ability to share outside of the group, etc.
They want Exchange 2010 now for all of these users in what as I understand it is basically mimicing a hosted service provider, just internally.
I know that Exchange 2010 SP1 now supports mupti-tenancy. I’ve set up the same functionality with Exchange 2003 years ago (http://www.msexchange.org/tutorials/Shared_Hosting_Exchange_2003_Part1.html
), but I understand that a lot has changed since then.
The good news is that we’re starting from scratch here with no need for a migration, modifying an existing domain, or anything like that. Users will connect using the Outlook Web App or whatever RPC over HTTPS is called in ex2010.
I’m looking to setup only 2 boxes, one as the domain controller and one as the exchange 2010 server (member server), yes with all roles on it (no budget for more hardware). For all intents and purposes, consider these 2 servers to be on a separate network than the internal networks at the clinic, behind their own firewall with a different public IP addresses.
I’ve read through:
(from early June)
(modified Aug 25, but mostly about general stuff)
and all of the information and all of the other links here: http://social.technet.microsoft.com/wiki/contents/articles/exchange-2010-sp1-information-for-hosted-service-providers.aspx
I’m looking for suggestions from people who might have already done something like this.