部署标准版OCS.doc

Microsoft Communications Server2010 (Beta)Standard Edition Deployment GuideThis document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. This document is confidential and proprietary to Microsoft. It is disclosed and can be used only pursuant to a non-disclosure agreement. Copyright 2010 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Outlook, SQL Server, Visio, Visual C+, Windows, Windows Media, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.ContentsIntroduction1Lab Reference Architecture1Lab Requirements2Server Requirements2Client Requirements4Installing Communications Server 2010 Standard Edition4Preparing Active Directory5Preparing the First Standard Edition Server5Installing Topology Builder and Admin Tools7Configuring the Topology9Configuring Simple URLs9Defining a Topology11Beginning a Topology11Configuring Server Roles13Publishing a Topology20Installing the Standard Edition Front End Server23Installing the Back-End Database28Installing the A/V Conferencing Server28Installing the Edge Server28Installing Certificates on the Front End Servers29Creating Front End Server Certificates29Assigning Front End Server Certificates33Installing Certificates on the Edge Server34Adding a Standard Edition Server to an Existing Enterprise Deployment34IntroductionThis document describes how to set up a Microsoft Communications Server 2010 (Beta) Standard Edition server. Although the specific example used in the document is a lab deployment, the same procedures apply to deploying Communications Server in an operational environment. Lab Reference ArchitecturePreliminary documentation and subject to changeThe reference architecture that we will deploy in this document is shown in the figure below.Lab Reference ArchitectureThe following table lists each physical and logical FQDN and corresponding DNS entry in the topology. This example assumes that the fictitious company Contoso has assigned a pool of Internet-facing static IP addresses in the range of through 0, inclusive, and that the name resolution shown in the next table for IP addresses in this range exist in the Internet. Lab FQDN and DNS ConfigurationComponentDescriptionFQDNIPDomain controllerPhysical Front End Server 1Physical Front End poolLEdge ServerPhysical 0extEIP/PBX gateway (not a server role)Physical computerpstnGW.0Reverse proxy (not a server role)Physical computerintRP.0extRP.:443Internal Web URL overrideLogicalintSDNS A Record to:External Web servicesLogicalextSMeet simple URLLDNS A Record to:Administrative simple URLLDNS A Record to:Dial-in simple URLLDNS A Record to:Lab RequirementsPreliminary documentation and subject to changeThis section lists the requirements for the topology shown in “Lab Reference Architecture” earlier in this guide.Server RequirementsPreliminary documentation and subject to changeBefore you deploy Communication Server 2010, you must have in place the infrastructure to support the reference topology. Each computer that runs Communications Server 2010 must meet the following requirements: A 64-bit edition of the Windows Server 2008 R2 operating system, or a 64-bit edition of Windows Server 2008 with Service Pack 2 or later service pack All updates installed from Windows Update The Web Components Server, which is collocated on the Front End Server, requires IIS 7.0 with the following role services installed: Static Content Default Document Directory Browsing HTTP Errors HTTP Redirection ASP.NET .NET Extensibility Internet Server API (ISAPI) Extensions ISAPI Filters HTTP Logging Logging Tools Tracing Anonymous, Basic, and Windows Authentication enabled Request Filtering Static Content Compression IIS Management Console and Scripts and ToolsTo install the IIS 7.0 role services, open a Command Prompt window. At a command prompt, type the following, and then press RETURN:ServerManagerCmd.exe -Install Web-Server Web-Http-Redirect Web-Scripting-Tools Web-Windows-Auth Web-Asp-Net Web-Log-Libraries Web-Http-Tracing Web-Basic-Auth .NET Framework 3.5 with SP1 or later service pack Microsoft Visual C+ 2008 Redistributable x64 9.0.30729.4148. If you do not have this redistributable, Setup will install it for you. Windows PowerShell 2.0. You must remove any earlier versions of Windows PowerShell before you install this one. Windows Server 2008 R2 meets this requirement. You can download the Update for Windows Server 2008 (KB968930), which includes Windows PowerShell 2.0, at /downloads/details.aspx?FamilyId=863e7d01-fb1b-4d3e-b07d-766a0a2def0b&displaylang=en. For Beta, while not required to install the Topology Builder, the Backward Compatibility components for SQL Server 2005, version 8.05.2312 are required for running the Install-CsDatabase cmdlets. In certain cases, one or more of these cmdlets are called from within Topology Builder. This includes the cmdlets for creation of the Central Management Store (CMS) and the Local Management Store, the SQL Express instances on Standard Edition Front End server, and if deploying an Enterprise Edition server, the databases on the Back End SQL server. The Backward Compatibility components for SQL Server 2005, version 8.05.2312 are available on the installation media. Microsoft SQL Server 2008 Native ClientAdditional requirements are as follows: The Microsoft Silverlight 4 RC 4.0.50303.0 browser plug-in must be installed on the computer that is running the Communications Server Control Panel. This version of Silverlight is available at /fwlink/?LinkID=167220 Windows Media Format, which is automatically installed by Setup during Step 2, is required. Message Queuing Services and Directory Service Integration are required on the Front End servers. However, do not install Message Queuing HTTP support. Otherwise, additional IIS configuration might be required. On any domain member computer (except a Domain Controller), including Front End Servers, from which you prepare the Active Directory Domain Services, you must add the Active Directory Remote Management tools. This is not needed for the Front End server installation, only the Active Directory preparation. To do so, open a Command Prompt window, and then do one of the following: On Windows Server 2008 SP2, at a command prompt, type the following, and then press RETURN:ServerManagerCmd.exe Install RSAT-ADDC On Windows Server 2008 R2, you need to import the servermanager module first. From a Powershell console, type the following and press ENTER.Import-Module servermanager Again, from the PowerShell console, type the following and press ENTER. Add-WindowsFeature RSAT-ADDS Then, at a command prompt, type the following, and then press RETURN:ServerManagerCmd.exe Install RSAT-ADDSTo run Communications Server 2010 (Beta) Setup, you must be a Local Administrator and a Domain User.In order to publish and enable a topology from Topology Builder, you must log on as a member of the DomainAdmins and the RTCUniversalServerAdmin groups.A member of the DomainAdmins group can delegate publishing and enabling a topology to other users or groups.In order to administer the topology by using the Communications Server Control Panel, you must be logged on as a member of the CSAdministrator group. Client RequirementsPreliminary documentation and subject to changeFor details about client requirements, see “Client Planning Overview” in the Planning and Architecture documentation.Installing Communications Server 2010 Standard Edition Preliminary documentation and subject to changeThis section provides the steps to deploy Communications Server Standard Edition as the only Front End Server, two collocated SQL Server Express instances (rtc and rtclocal), a collocated A/V Conferencing Server, and a separate Edge Server. This configuration provides internal and external users with: Instant messaging Presence Web conferencing A/V conferencingThe steps to install Communications Server 2010 Standard Edition (Beta) are:1. Prepare Active Directory2. Prepare the first Standard Edition Server3. Install Topology Builder and the Admin Tools4. Configure and publish the Standard Edition topology5. Install the Standard Edition server by running Install or Update Communications Server System, Steps 2, 3 and 4 (Step 1 is completed by doing the above steps 1-4)Preparing Active DirectoryPreliminary documentation and subject to changeBefore you install Communications Server 2010, you must prepare the Active Directory Domain Services. For details, see the Active Directory Guide.Preparing the First Standard Edition ServerPreliminary documentation and subject to changeTo prepare the first Standard Edition server:1. From the installation media on the computer meeting the requirements described above, and logged on as a local Administrator and a Domain User, run SetupSetup.exe.2. If you are prompted to install the Microsoft Visual C+ 2008 distributable, click Yes.3. On the Microsoft Communications Server 2010 (Beta) Installation Location page, click OK.4. On the End User License Agreement page, click I accept, and then click OK. This step is required before you can continue.5. On the Communications Server 2010 Deployment Wizard page, click Prepare first Standard Edition server.Note: However, you should only run this step for the first and only Front End server in your deployment. If you have an existing Standard Edition server or one or more existing Enterprise Edition servers, do not run this step. Instead, click Install or Update Communications Server System instead, and run Step 1. 6. Click Next.7. On the Executing Commands page, when the task status is shown as Completed, click Finish. 8. On the Communications Server 2010 Deployment Wizard page, click Exit.Installing Topology Builder and Admin ToolsPreliminary documentation and subject to changeThe computer where you install Topology Builder must meet the following requirements: A 64-bit edition of one of the following operating systems: Windows 7, Windows Server 2008 R2, Windows Server 2008 with Service Pack (SP) 2 or later service pack, Windows Vista with SP2 or later service pack .NET Framework 3.5 with SP1 or later service pack Microsoft Visual C+ 2008 Redistributable x64 9.0.30729.4148. If you do not have this redistributable, Setup will install it for you. Windows PowerShell 2.0. You must uninstall any earlier versions of Windows PowerShell before you install this one. Windows Server 2008 R2 meets this requirement. You can download the Update for Windows Server 2008 (KB968930), which includes Windows PowerShell 2.0, at /downloads/details.aspx?FamilyId=863e7d01-fb1b-4d3e-b07d-766a0a2def0b&displaylang=en. Message Queuing Services and Directory Service Integration are required on the Front End servers. However, do not install Message Queuing HTTP support. Otherwise, additional IIS configuration might be required. For this beta release, while not required to install the Topology Builder, the Backward Compatibility components for SQL Server 2005, version 8.05.2312 are required for running the Install-CsDatabase cmdlets. In certain cases, one or more of these cmdlets are called from within Topology Builder. This includes the cmdlets for creation of the Central Management Store (CMS) and the Local Management Store, the SQL Express instances on Standard Edition Front End server, and if deploying an Enterprise Edition server, the databases on the Back End SQL server. The Backward Compatibility components for SQL Server 2005, version 8.05.2312 are available on the installation media.In order to publish and enable a topology from Topology Builder, you must log on as a member of the DomainAdmins and the RTCUniversalServerAdmin groups.A member of the DomainAdmins group can delegate publishing and enabling a topology to other users or groups.In order to administer the topology by using the Communications Server 2010 (Beta) Control Panel, you must be logged on as a member of the CSAdministrator group.If your computer meets these requirements, you are ready to install Topology Builder.To install the Topology Builder:1. From the installation media on the Standard Edition server, and logged on as a Local Administrator and a Domain User, run Setupamd64Setup.exe.2. If you are prompted to install the Microsoft Visual C+ 2008 distributable, click Yes.3. On the Microsoft Communications Server 2010 (Beta) Installation Location page, click OK.4. On the End User License Agreement page, click I accept, and then click OK. This step is required before you can continue.5. On the Microsoft Communications Server 2010 (Beta) Deployment Wizard page, click Install Topology Builder. You are not required to prepare the Active Directory Domain Services before you install the Topology Builder, but you must do so before you publish a topology.6. When the installation is successfully completed, as indicated by the green check, click Exit.Configuring the Topology Preliminary documentation and subject to changeMicrosoft Communications Server 2010 processes message traffic by using topology information that you publish to the Central Management Store. In order to ensure that the topology is valid, we recommend that you publish and enable your topology by using Microsoft Communications Server 2010 Topology Builder. If you modify the topology later, you can also republish the topology by using Topology Builder.This section will help you use Topology Builder to configure the Standard Edition deployment. It covers the following topics: Configuring Simple URLs Defining a Topology Beginning a Topology Configuring Server Roles Publishing a Topology Configuring Simple URLs Preliminary documentation and subject to changeWhen you define a topology, Topology Builder will prompt you to provide simple URLs. Simple URLs provide an easy way for users to access Communications Server functionality. The following simple URLs are required: Meet. The location of services for managing meetings. There must be one, and only one, active meet simple URL for each SIP domain in your deployment. Administration. The location of the Communications Server Control Panel. Dialin. The location of dial-in conferencing services.You must define one meet simple URL for each SIP domain, and for this beta release you must also define a dial-in simple URL and an administrative simple URL.If you decide now what those URLs will be, you can simply enter the information while Topology Builder is running. This section explains the rules for creating simple URLs. Getting these URLs right in the beginning will prevent you from having to reconfigure certificates and change DNS records later on. Each simple URL that you create must conform to the following rules: Must use secure HTTP (HTTPS). Must be unique across all existing active and inactive simple URLs for all SIP domains in your deployment. Must not be the prefix of any other existing simple URL for all SIP domains in your deployment. Cannot include port information. For example, the following URLs are invalid:o :445 o :443/Meet Must identify the URLs supported function as meet, dialin, or admin.The syntax of the URL can follow three forms. In the simplest, the relevant functionality is indicated as a host name affixed to the domain name. The general form is as follows: https:/.The following table provides specific examples. Simple URLAcceptable ExampleMeet Dial-in Administrative In the second form, the relevant functionality can be identified as a path qualifier. The general form is as follows:https:/The following table provides specific examples.Simple URLAcceptable ExampleMeet/MeetDial-in /DialinAdministrative/AdminIn the third form, you can use the FQDN of the Web farm, as shown in the following examples:Simple URLAcceptable ExampleMeethttps:/MeetDial-in https:/DialinAdministrativehttps:/AdminYou must mark one, and only one, meet simple URL as active in Topology Builder.If you use the third form, the following virtua