Prerequisites
Before you install Office Communications Server 2007 R2 Standard Edition, you must deploy Internet Information Services (IIS). On a computer running IIS 7.0 on Windows Server 2008, you need to configure IIS to run in IIS 6.0 compatibility mode. The following steps describes the installation process.
Open
Server Manager.
Select
Next.
Select
Web Server (IIS).
Select
Add Required Features.
Select
Next.
Select
Next.
- Select ASP.NET
- Select Windows Authentication
- Select IIS 6 Management Compatibility
- Select IIS 6 Metabase Compatibility
- Select IIS 6 WMI Compatibility
- Select IIS 6 Scripting Tools
- Select IIS 6 Management Console
Select
Close.
The Microsoft Visual C++ Redistributable Package, must also be installed on the computer for Office Communications Server 2007 R2 to run correctly.
Execute vcredist_x64.exe from OCS 2007 R2 installation media.
Select
Next.
Select
Install.
Select
Finish.
After setup remove temporary files that are erroneously generated by the installer into the system root directory. See knowledge base article
http://support.microsoft.com/kb/950683.
Install Standard Edition Server
If you run the Deployment Tool, Setup automatically installs Microsoft SQL Server 2005 Express Edition with SP2 for the back-end database. You do not need to install this component separately.
Execute
setupse.exe.
Select
Yes.
Select
OK.
Selec
t
OK.
Select
Next.
Select
Next.
Select
Next.
Deselect all options and select
Next.
Select
Next.
Select
Next.
Select
Next.
Select
Finish.
Configure Standard Edition Server
After you install Standard Edition server, use the Configure Server Wizard to configure it.
Execute
Configure Server.
Select
Next.
Select
Next.
Select
Next.
Select
Clients will be manually configured for logon. Select
Next.
Select
Next.
Select
Next.
Select
Finish.
Configure Certificate
Office Communications Server requires certificates on each Server in order to use MTLS (TLS with mutual authentication). All Office Communications Servers use MTLS to communicate with one another. Each client will also need to trust the certificate that the server is using in order to connect to the server by using TLS.
Before request a certificate is necessary to create a request.inf file as described in the following figure.
From a command prompt create a new certificate request file using the following command:
certreq –new request.inf StandardOCS.req
To request the certificate use the following command or use the web interface from the issuing Certification Authority named XYZ.
certreq –submit -config XYZ.it.net\IssuingCA1 StandardOCS.req StandardOCS.cer
Select
Configure Certificate.
Select
Next.
Select
Next.
Select
Next.
Select
Next.
Select
Next.
Configure Web Components Server
Log on to the server running the Web Components Server as a member of the Administrators group.
1. Click Start, click Administrative Tools, and then click the Internet Information Services (IIS) Manager.
2. In the Connections pane, expand the Web Components Server.
3. Expand Sites, and then click Default Web Site.
In the Default Web Site Home pane, under IIS click
Authentication. In the Actions pane, click
Bindings.
In the Site Bindings dialog box, click
Add.
In the Add Site Bindings dialog box, in the Type drop-down, click https.
In the SSL certificate drop-down, click the certificate that you want to use for the Web Components Server.
Click
OK.
Select
Close.
Select
Exit.
Start Services
The final step in OCS 2007 R2 setup is related to start your Office Communications Server 2007 R2 services.
Select
Start Services.
Select
Next.
Select
Next.
Install Administrative Tools
The procedure for installing the administrative tools (not installed during OCS 2007 R2 Setup) is illustrated in the following steps.
To install the 32-bit version of the OCS R2 32-bit Administrative Tools is available in the “\Support\i386” directory on the 64-bit media.
The required pre-requisites are also located in this directory, and
must be installed in the following order:
1.
sqlncli.msi (SQL Server Native Client – contains the SQL OLE DB and SQL ODBC drivers in on native DLL)
2.
vcredist_x86.exe (x86 VC++ 2008 redistributable)
3.
NET Framework 3.5 SP1 (download it here from Microsoft’s Web Site or use \Setup\amd64\dotnetfx35.exe)
4.
OCSCore.msi (OCS 2007 R2 Core Components)
5.
AdminTools.msi (Office Communications Server 2007 R2 Administrative Tools)
Appendix B – Address Book configuration
The users populated in the Address Book Server files can be controlled based on certain Active Directory Attributes listed in the
AbAttribute table in
rtc database.
To see in address book files only users enabled for Office Communications Server you need to change a value in
msRTCSIP-PrimaryUserAddress attribute from default (hex: 8020800 dec: 134350848) to (hex:
8028000 dec:
134381568).
After you modify the AbAttribute table, you can refresh the data in the AbUserEntry table by running this command:
abserver.exe –regenUR.
Then, you can update the file in the Address Book Server file store by starting a manual
-syncNow operation.
Note: For advanced address book configurations refer to the following
link.
