Welcome to the deployment walkthrough for the Microsoft Solution for Hosted Messaging and Collaboration version 4.0 . This documentation walks you through the deployment of each of the key server types referenced in the overall solution architecture. The architecture described in this walkthrough is designed to be deployed into a lab or test environment so that you can become familiar with the various components of the solution architecture. Many of the topics and procedures can be used when performing a production environment deployment; however, such a deployment requires planning in areas not covered in this walkthrough, including security, scalability, and fault tolerance.
Please note that after you prepare and promote your first domain controller, you will log on to all of the servers that you configure using an account that is a member of the Domain Administrators group-unless the procedure specifically instructs otherwise.
Hosted Messaging and Collaboration 4.0 supports Microsoft Windows Server 2003, Service Pack 2 (SP2), except for servers running the Microsoft Provisioning System Engine. Installing Windows Server 2003, SP2 on servers running the Microsoft Provisioning System Engine will cause those servers to fail.
For more information about how this issue may impact your deployment of the solution, see Windows Server 2003, Service Pack 2 and the Microsoft Solution for Hosted Messaging and Collaboration.
The deployment walkthrough doesn't include deployment of the following Hosted Messaging and Collaboration infrastructure components and services:
- Server purposing - This is a lab deployment, and therefore you don't need a server purposing solution; as you move into production, automatedly deploying servers will become more relevant. Deployment steps for using server purposing for the Hosted Messaging and Collaboration are provided in Build Server Purposing.
- Update management - Specific steps for update management aren't included in this lab deployment because there's nothing specific to the hosting environment in general and the Hosted Messaging and Collaboration solution in particular for update management. For instructions on deploying update management in your environment, see Build Update Management.
- Customer Directory Integration - Customer Directory Integration doesn't lend itself to a lab deployment. For Customer Directory Integration deployment steps, see Build Customer Directory Integration.
Deployment of Customer Directory Integration requires requires at a minimum one external Active Directory forest - in other words, an additional domain controller.