leedesmond’s blog

OCS 2007 R2 (RTM) Installation Walkthrough Part I
OCS 2007 R2 (RTM) Installation Walkthrough Part II
OCS 2007 R2 (RTM) Installation Walkthrough Part III

See also:
Article: Moving to Office Communications Server 2007 R2
Article: Moving to Office Communications Server 2007 R2 - Part II
—

The next step on the main setup screen is to click on Deploy Standard Edition Server. There are a total of 7 steps to go through (eight in OCS 2007). Step 1 is dependent on having the Web Server (IIS) already installed plus a number of services as illustrated*.

Since we are putting R2 on Windows Server 2008 x64 and if any of the IIS role services are left out, misleading error messages will send you going around in circles until you figure out what the confusing references actually mean, such as this one here:

” Not available: IIS 6 Management Compatibility and IIS Windows Authentication role services must be installed before you Deploy Server. ”

Also, you may be prompted to install the following component before Step 1 can actually begin:

——————————–
Windows Media Format Runtime required
——————————–
The Windows Media Format Runtime is required in order to install this component. Installing the Windows Media Format Runtime may require a system restart to complete the installation. Click OK to continue with the installation.
——————————–
OK Cancel
——————————–

Re-start Step 1 after you have rebooted the computer. Prior to that, ensure that the installation account already has membership in both the RTCUniversalServerAdmins and Domain Admins. Soon after accepting the license agreement and installation path, R2 offers a number of new application services that you can find in the screen shot.

You can then accept the default to use existing service accounts named RTCService and RTCComponent that were created from the previous OCS installation. You must already known the passwords otherwise you cannot proceed further. Next, accept the default internal web farm FQDN that points to your machine (ocsr201.swissitpro.local). Leave the optional field for external web farm FQDN blank if remote access is not a topic at the moment. Similarly, acknowledge to keep the default database paths.

By far, Step 1 consumes the most time and can be a fairly lengthy process. This should not come as a surprise since multiple application services, including SQL Server 2005 database, need to be setup and properly configured on a single standard edition R2 box. Towards the end, all the services will be automatically activated before this step terminates. You can verify that the deployment log marked all actions as Success before moving on to the next step.

Right after you start Step 2 Configure Server, you can only select and configure the R2 server pool even though an OCS 2007 Standard Edition pool is already present in the domain. Doing so enables users homed on an R2 server (this first R2 machine) to use the new features on the R2 pool. Following that, you get to specify new SIP domains or pick any existing one to mark as the global SIP domain. Respectively, this values read ocsr201.swissitpro.local and swissitpro.local in our case.

The default Client Logon Settings to allow automatic discovery via DNS SRV records is recommended. Leave the check against “Use this server or pool to authenticate and redirect automatic client logon requests” as it is. The purpose here is to turn on the Director server role to facilitate this feature. Next, tick the SIP domain named above to define it as the SIP domain for automatic logon.

Again, if external access is not yet a topic, skip the External User Configuration section. Step 2 is relatively painless and it completes execution almost in a flash before you even notice.

* Windows Authentication, IIS 6 Management Compatibility (IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility, IIS 6 Scripting Tools, IIS 6 Management Console)

Technorati tags: LCS/OCS, OCS 2007 R2

2 Comments »