Install FE OCS

8/6/2019 Install FE OCS

1/12

Steps to install an FE server (Enterprise deployment)

Install the pre-requisites

In order to install the front end server, we need to have following components installed on theserver:

Microsoft Visual C++ 2005 SP1

Net framework 2.0IIS

If you haven't installed these two components, the OCS installation will prompt you to installthese. Please follow the following steps to install them
http://www.ocspedia.com/FE/PreReq-FE.htmhttp://www.ocspedia.com/FE/PreReq-FE.htm


2/12

Decide the topology

What are two different topologies?

We can install the OCS FE using any one of the following two topologies!

Consolidated Topologies:If you select consolidated topology, the front-end server, the Web Components Server,

the Web Conferencing Server, and the A/V Conferencing Server are installed together on

each Enterprise Edition Server within a pool.

-It reduces the number of hardware servers required while maintaining high availability.

-It simplifies the deployment and administration.

-Reduced throughput per server.

-Recommended for the organization that plan to support only instant messaging and

presence.

Expanded Topologies:

If you select expanded topology, the front-end server, the Web Components Server, the

Web Conferencing Server, and the A/V Conferencing Server is installed on a dedicated

computer. A Web Components Server can be collocated with each front-end server.

-It increases the number of hardware servers required while maintaining high availability.

-Recommended for the organizations for which high availability and maximum

performance throughput are important.

-provides benefits with regard to scalability and high availability, but creates additional

complexity in the administration and deployment of the pool.
http://www.ocspedia.com/FE/DecTopology.htmhttp://www.ocspedia.com/FE/DecTopology.htm


3/12

Prepare the Active Directory

Why do we prepare the active directory and what does happen during this process?

What are the steps to prepare the active directory? : Active Directory preparationinvolves schema preparation, forest preparation and domain preparation.

What does happen during Active Directory preparation?:

During the Schema Prep extends the schema in Active Directory to include classes and attributes specificto Office Communications Server 2007.

The Prep Forest step creates Office Communications Server objects in the forest rootdomain Systems container if the default option is selected or in the configuration

container if you choose. These objects contain global settings and information about your

Office Communications Server deployment. Prep Forest also creates OfficeCommunications Server objects in the configuration container that contain property sets

and display specifiers used by Office Communications Server.

The Prep Domain step adds the necessary ACEs to universal groups that grant

permissions to host and manage users within the domain. Prep Domain is required in alldomains where you want to deploy Office Communications Servers and any domains

where your Office Communications Server users will reside. The task is run once in each
http://www.ocspedia.com/FE/Prep_AD.htmhttp://www.ocspedia.com/FE/Prep_AD.htm


4/12

domain.Prep Domain create ACEs on the domain root and three built-in containers:

Users, Computers, and Domain Controllers. The following tables list these ACEs. All

ACEs are inherited, unless noted otherwise.

Steps to complete the Active Directory preparation

Followings are the steps to prepare the Active Directory before we install an OCS Server

Schema Preparation


5/12


6/12

Forest Preparation


7/12


8/12


9/12

Domain Preparation


10/12


11/12

Install the SQL Server

SQL Server versions

Before you deploy Enterprise Edition Server, install SQL Server 2005 with Service Pack 1 (32-bit or 64-bit)or SQL Server 2000 with Service Pack 4 on a dedicated computer.

Hardware requirement

Personal computer with a 3.2 gigahertz (GHz) dual processor with hyperthreading

2 18 gigabyte (GB) hard disk space with 15000 rpm SCSI

1 MB cache

2 gigabyte (GB) of RAM

1 gigabit per second (Gb/s) network adapter

Important links for the SQL Server

SQL Server TechCenter: http://technet.microsoft.com/en-us/sqlserver/default.aspx

SQL Server Learning: http://www.microsoft.com/sql/techinfo/default.mspx

How to install the SQL Server : http://support.microsoft.com/kb/303747

Deploy the Enterprise Pool

Configure the Load Balancer

Load Balancer

The load balancer performs the critical role of delivering scalability and high availability across multipleservers connected to a centralized database on the Office Communications Server, Back-End Databaseserver.

Only one load balancer is required, but you can optionally create two logical load

balancers--one for the front-end servers and one for the Web Components Server--if you

deploy Enterprise Edition in an expanded configuration. If you want to employ twological load balancers, you can configure two virtual IP (VIP) addresses on one physical

load balancer or you can configure two separate physical load balancers. In either case,

you must create one load balancer FQDN for the front-end servers to use and anotherload balancer FQDN for the Web Components Server to use.

Note: You don't need a Load Balancer if you have only one FE server.

Required Ports on the Load Balancer Virtual IP Address

Port(s) Required Virtual IP (if you have more than one Port Use
http://www.ocspedia.com/FE/Install_SQL.htmhttp://technet.microsoft.com/en-us/sqlserver/default.aspxhttp://www.microsoft.com/sql/techinfo/default.mspxhttp://support.microsoft.com/kb/303747http://www.ocspedia.com/FE/LoadBalancer.htmhttp://www.ocspedia.com/FE/Install_SQL.htmhttp://technet.microsoft.com/en-us/sqlserver/default.aspxhttp://www.microsoft.com/sql/techinfo/default.mspxhttp://support.microsoft.com/kb/303747http://www.ocspedia.com/FE/LoadBalancer.htm


12/12

logical load balancer)

5060 Load balancer VIP used by the front-end

server(s)SIP communication

5061 Load balancer VIP used by the front-end

server(s)

SIP communication over TLS

135 Load balancer VIP used by the front-endserver(s)

To move users from a pool (a remoteDCOM-based database operation); To

enable server-side allow and blockfunctionality for users

80 Both load balancer VIPs Communication with the AddressBook Server (ABS)

443 Load balancer VIP used by the front-endserver(s)

HTTPS traffic to the pool URLs

444 Load balancer VIP used by the WebComponents Server

Communication between the focus(Office Communications Server

component that manages conferencestate) and the conferencing servers

Important links for the NLB

Network Load Balancer technical overview

Configure the DNS Settings
http://technet.microsoft.com/en-us/library/bb742455.aspxhttp://www.ocspedia.com/FE/DNS_POOL.htmhttp://technet.microsoft.com/en-us/library/bb742455.aspxhttp://www.ocspedia.com/FE/DNS_POOL.htm

Documents

Install FE OCS