Script

[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-19

Acquiring and setting up the hardware that you need to implement your topology requires that, prior to publishing your topology in Topology Builder, you do the following:

• Acquire the hardware for each component in the topology design that you created and saved by using Topology Builder, including all required computers and hardware load balancers. For details about how to define a topology that specifies the components needed for your deployment, see Defining the Topology in Topology Builder. For details about hardware requirements for an Enterprise pool, see Production Environment Requirements.
  
  
• Set up Active Directory Domain Services (AD DS). Setting Up AD DS includes preparing AD DS and defining all components that you want to deploy in AD DS. For details about preparing AD DS, see Preparing Active Directory Domain Services for Communications Server 2010.
  
  
• Install the operating systems and all prerequisite software on each computer on which a Microsoft Communications Server 2010 server role is to be deployed. For details about server operating systems and prerequisite software, see Preparing Your Environment.
  
  
• Set up SQL Servers, including installing all prerequisite software on each database server required to support your deployment and configuring all required SQL Server instances. This includes the SQL Server instance for the back end, as well as an instance for archiving and monitoring (if your topology design includes Archiving Server and Monitoring Server). For information about the SQL database requirements, see Supported Back-End Database Servers in the Planning documentation.
  
  
• Set up the required permissions for creating the file share. Permissions for use of file shares by Communications Server 2010 are automatically configured by Topology Builder when you publish your topology. However, the user account used to publish the topology must have full control (read/write/modify) on the file share in order for Topology Builder to configure the required permissions. For example, you can create the file share with full control granted to Domain Admins or other user group, and then require that the Topology Builder user account used to publish your topology be a member of that group.
  
  

  Warning:
  The file share for Communications Server 2010 cannot be located on the Front End Server.

• Install and set up the hardware load balancer for Web Services.
  
  

After you complete all of the preparation tasks as described in this topic, but prior to publishing the Topology, you also need to perform the other preparation tasks, including setting up Internet Information Services (IIS), configuring SQL Server, creating and configuring file shares, and configuring hardware load balancing. For details about completing each of these tasks, see Preparing the Production Environment.