Step 1 OCS2007PB Deployment (Extend your ADS Schema)
Before you can run OCS2007 you need to extend your schema first. Before you can extend your Schema you must take care of the following steps. These steps are crucial before doing anything. In this technical explanation of deploying OCS2007 e-office will choose the Enterprise Pool in a Expanded Topology as an example. This information is based on Microsoft Office Communications Server 2007 Public Beta.
Step 1. Determine Key Planning Decisions
Discusses the main decision points you need to consider before selecting a topology.
Step 2. Select Your Topology
Presents several sample deployments based on size and desired functionality. These topologies are intended to guide you through the possible options available when you plan your deployment.
Step 3. Plan for Your Deployment Path
Summarizes important things you need to know before you begin any Office Communications Server deployment and provides an overview of the deployment process.
Step 4. Prepare Your Infrastructure
Discusses the prerequisites for the Active Directory® Domain Services and for supported topologies, including certificate and DNS requirements.
Step 5. Review Hardware Requirements
Lists hardware and software requirements for Office Communications Server 2007 server roles and clients.
Step 6. Plan for External User Access
Provides guidelines for deploying Office Communications Server 2007 in your perimeter network for the purpose of supporting messaging, presence, and conferencing with users connecting from outside your organization firewall.
Step 7. Plan for Address Book Server
Discusses requirements for supporting the Address Book Server, including IIS (Internet Information Services), network file share, and required disk space.
Step 8. Plan to Deploy Load Balancers
Examines hardware load balancer requirements and configurations for an Enterprise pool. Also discusses the advantages of using hardware load balancers with edge server arrays.
Step 9. Plan for High Availability and Fault Tolerance
Provides guidelines for assuring high availability and describes Office Communications Server 2007 features for optimizing availability and fault tolerance.
Step 10. Plan for Database Storage
Discusses storage requirements for the various databases and file shares that are required by Office Communications Server 2007, including storage requirements for Archiving and CDR (Call Detail Records) database and new messaging support for rich text format. Also discusses RAID (DAS), NAS, and SAN tradeoffs, as well as basic calculations of disk space needed per meeting and per pool, based on numbers of users.
Step 11. Plan for Compliance and Usage Analysis
Describes how to meet compliance requirements for archiving and call data recording. Before going to the next step get an clear answer on the steps 1-11.
Prepare your Active Directory (Schema)
What Does Prep Schema Do?The Prep Schema step extends the schema in Active Directory to include classes and attributes specific to Office Communications Server 2007. This is the first procedure run to prepare your environment for your Office Communications Server 2007 deployment. This procedure is required and run only once in the Active Directory forest.
Office Communications Server 2007 adds new classes and attributes and objects to the Active Directory schema.
You can deploy Office Communications Server 2007 using either one of two methods:
· The Deployment Tool using Setup.exe.
· Command-line tool, LcsCmd.exe, provided on the CD.
In this example e-office will use the OCS Deployment Tool to install and configure OCS.
(1) Log on to a server in your forest with Schema Admins credentials and administrator credentials on the schema master. The first step is the most crucial step because you need to have the correct rights within your Active Directory. Contact your administrator or check it again before proceeding.
(2) In the Office Communications Server installation folder or CD, run Setup.exe to start the Deployment Tool.
Select one of the following:
For Standard Edition, click Deploy Standard Edition Server.
For Enterprise Edition, click Deploy Enterprise Pool in a Consolidated Topology or Deploy Enterprise Pool in an Expanded Topology. We will use Enterprise Pool in an Expanded Topology.
(3) Click Prepare Active Directory.
(4) At Prep Schema, click Run.
(5) On the Welcome to the Schema Preparation Wizard page, click Next.
(6) Select the default option, Schema files are located in the same directory as Setup, and then click Next.
(7) On the Ready to Prepare Active Directory Schema page, review your current settings before clicking Next.
(8) On the Schema Preparation Wizard has completed page, click View Log. Under the Action column, expand Schema Prep. Look for Execution Result at the end of each task to verify Prep Schema completed successfully. Close the log when you finish.
As an example of that need to see the following results:
(9) Click Finish.
(10)Wait for Active Directory replication to complete or force replication to all the domain controllers listed in the Active Directory Sites and Services snap-in for the forest root domain controller before continuing to Prep Forest.
The next step in the deployment process of OCS2007PB is to extend and prep your forest. Refer to Step 2 OCS2007PB Deployment (Extend your ADS Forest)
