Running Microsoft Office Communications Server 2007 R2 in a Virtualized Topology

This whitepaper defines the supported topologies and provides best practice recommendations for running Office Communications Server 2007 R2 and SQL Server™ 2008 in a Windows Hyper-V environment or other hypervisor technologies.

Link

OCS 2007 R2 database

Data Types and Storage

Planning a storage solution for Office Communications Server 2007 R2 requires knowing what types of data are generated and where each type is stored. The following table lists this information.

Type of data	Name of data store	Location
Persistent user data (for example, ACLs, contacts, home server or pool, scheduled conferences)	RTC	Enterprise Edition, back-end database; Standard Edition, Microsoft SQL Server 2005 Express with SP2.
Persistent Office Communications Server 2007 R2 settings	RTCConfig	Enterprise Edition, back-end database; Standard Edition, SQL Server 2005 Express with SP2.
Transient user data (for example, endpoints and subscriptions, and transient conferencing state)	RTCDyn	Enterprise Edition, back-end database; Standard Edition, SQL Server 2005 Express with SP2.
Database containing global address information used by Address Book Web query service to support Address Book search queries from Communicator Mobile for Windows clients	RTCab	Enterprise Edition, back-end database; Standard Edition, SQL Server 2005 Express with SP2.
Address Book download files created by Address Book Server and downloaded by Office Communicator, Office Communicator Phone Edition, and Office Communicator Attendant clients	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\Address Book Files on the local Standard Edition server.
Meeting content (for example, Microsoft Office PowerPoint presentations, question and answer logs, polling, chat, and uploaded content)	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\Data MCU Web\Web on the local Standard Edition server.
Meeting content metadata (XML data that describes the meeting content, such as date and time a PowerPoint presentation is uploaded)	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\Data MCU Web\Non-Web on the local Standard Edition server.
Meeting content compliance log (XML data that records content upload activities, along with the uploaded meeting content)	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in a default folder on the local Standard Edition server.
Application data files that are used internally by the application server component for the pool	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in <\Microsoft Office Communications Server 2007 R2 installation folder>\Application Host\Application Data on the local Standard Edition server.
Update files used by the client version control mechanism to update Office Communicator clients and by the Device Update Service to update unified communications (UC) devices	User-specified UNC path on Enterprise Edition Installer-created folder on Standard Edition	For Enterprise Edition, update files are stored in a user-created file share located on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition: Client update files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\AutoUpdate. Device update files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\DeviceUpdateFiles.
Monitoring Server Quality of Experience (QoE) data	QoEMetrics	Monitoring Server QoE database normally deployed on a separate computer (recommended) from the back-end database. This database is always deployed on the same server, in the same instance, as the CDR database.
Monitoring Server CDR data	LcsCDR	Monitoring Server CDR database normally deployed on a separate computer (recommended) from the back-end database. This database is always deployed on the same server, in the same instance, as the QoE database.
Archiving data	LcsLog	Archiving service database normally deployed on a separate computer (recommended) from the back-end database.
Group Chat data	User-specified database name	SQL Server 2005 or SQL Server 2008 database deployed on separate computer from the Group Chat Server.
Group Chat Web and compliance folders (to store files uploaded to the Group Chat Web service)	User-specified UNC path	A file share that can be accessed by all of the Group Chat Servers and services in the pool.
Group Chat compliance data	User-specified database name	SQL Server 2005 with SP2 or SQL Server 2008 database deployed on separate computer from the Compliance service. This can be the same database instance that is used for Group Chat data.
Transient Response Group Service data	ACDDyn	Enterprise Edition, back-end database; Standard Edition, SQL Server 2005 Express with SP2.

.

OCS 2007 R2 lcscmd

LCSCmd is a very powerful tool that makes it possible to do things such as activate servers, check server configurations, manage certificates, and prepare AD DS for Office Communications Server installation. What it doesn't do is the actual installation of the servers.

LCSCmd installs with Office Communications Server 2007 R2 Core Components (osccore.msi) and the Administration Tools (admintools.msi), but it can also be run from the CD or a share. By default you'll find LCSCmd.exe in the Program Files\Common Files\Microsoft Office Communications Server 2007 R2 folder.
Usage Instructions
lcscmd /Forest: /Action:
/PoolName:
/PoolBE:
/RefDomain:
/MeetingContentPath:
/MeetingMetaPath:
/AppDataLocation:
/ClientUpdateLocation:
[/PDCRequired:[TRUE|FALSE] ][/GlobalSettingsDC: ]
[/DC: ][/GC: ]
[/Global: ]
[/GroupDomain: ]
[/GroupDomainDC: ]
[/DBDataPath: ]
[/DBLogPath: ][/Clean:[TRUE|FALSE] ]
[/EnableArch:[TRUE|FALSE] ][/EnableCDR:[TRUE|FALSE] ]
[/EnableQoE:[TRUE|FALSE] ]
[/DynDataPath: ]
[/DynLogPath: ][/PoolFQDN: ]
[/InternalWebFQDN: ]
[/ExternalWebFQDN: ]
[/ABOutputlocation:

]
[/MeetingArchivingPath: ]
[/ABSDataPath:

]
[/ABSLogPath:

]
[/ACDDataPath: ]
[/ACDLogPath: ]
[/Force:[TRUE|FALSE] ][/L: ]
[/XML:[TRUE|FALSE] ][/?:[TRUE|FALSE] ]

/Forest Executes the action for the specified forest. If no fully
qualified domain name (FQDN) is specified, current forest is
used. It defaults to "".

/Action Takes a string specifying the action name. Valid action names
include CheckSchemaPrepState SchemaPrep CheckForestPrepState
ForestPrep ForestUnprep CheckAllDomainsPrepState CreatePool
RemovePool CheckPoolState CheckAllPoolsState
UpdatePoolBackend Diag

/PoolName Specifies the pool name.

/PoolBE Specifies the backend SQL Server instance that will be used
by the pool.

/RefDomain Specifies the reference domain FQDN.

/MeetingContentPath
Specifies the UNC path where meeting presentation content
should be located.

/MeetingMetaPath
Specifies the UNC path where meeting meta data should be
located.

/AppDataLocation
Specifies the folder where OCS Applications will write their
files.

/ClientUpdateLocation
Specifies a folder for the Client Update file store.

/PDCRequired
Specifies whether PDCs are required for the action. It
defaults to "TRUE".

/GlobalSettingsDC
Specifies the FQDN of a global settings domain DC. Must be
local domain DC if settings are in configuration container
and root DC if settings are in the system container. It
defaults to "".

/DC Specifies the FQDN of a domain DC. It defaults to "".

/GC Specifies the FQDN of a forest GC. It defaults to "".

/Global Specifies the global setting location. It defaults to "".

/GroupDomain
Specifies the FQDN of the domain where Office Communications
Server universal groups are located in. It defaults to "".

/GroupDomainDC
Specifies the FQDN of a DC in the domain where Office
Communications Server universal groups are located in. It
defaults to "".

/DBDataPath Specifies the folder where the database data file should be
located (must not end in \"). It defaults to "".

/DBLogPath Specifies the folder where the database log file should be
located (must not end in \"). It defaults to "".

/Clean Specifies whether to do a clean setup for pool backend
creation actions. It defaults to "FALSE".

/EnableArch Specifies whether archiving is enabled or not for the pool.
It defaults to "FALSE".

/EnableCDR Specifies whether to enable CDR. It defaults to "FALSE".

/EnableQoE Specifies whether to enable QoE. It defaults to "FALSE".

/DynDataPath
Specifies the folder where dynamic database data file should
be located (must not end in \"). It defaults to "".

/DynLogPath Specifies the folder where dynamic database log file should
be located (must not end in \"). It defaults to "".

/PoolFQDN Specifies DNS host name of the pool. It defaults to "".

/InternalWebFQDN
Specifies the FQDN of the internal web server. It defaults to "".

/ExternalWebFQDN
Specifies the FQDN of the external web server. It defaults to "".

/ABOutputlocation
Specifies the folder where the Address Book server will write
its files. It defaults to "".

/MeetingArchivingPath
Specifies the UNC path where meeting presentation content
archiving should be located. It defaults to "".

/ABSDataPath
Specifies the folder where Address Book Server database data
file should be located (must not end in \"). It defaults to
"".

/ABSLogPath Specifies the folder where Address Book Server database log
file should be located (must not end in \"). It defaults to
"".

/ACDDataPath
Specifies the folder where Response Group Service database
data file should be located (must not end in \"). It
defaults to "".

/ACDLogPath Specifies the folder where Response Group Service database
log file should be located (must not end in \"). It defaults
to "".

/Force Specifies whether to force task execution. It defaults to
"FALSE".

/L Specifies the log file path. If not specified, '\[][].html' is used. To
disable logging specify '-' as the log file name. It
defaults to "".

/XML Specifies whether the log file to be generated should be in
XML format instead of HTML. It defaults to "FALSE".

/? Shows help on usage. It defaults to "FALSE".

What’s new on interoperability between OCS R2 and SIP/PSTN Gateways, IP-PBXs and SIP Trunking Services.

Yann Espanet has write a nice article about interoperability of OCS 2007 R2.

Read at Unified Communication

OCS 2010 rumors from web

PBX killer, Voice CAL coming to OCS in 2010

Microsoft will ship a new version of its Office Communications Server (OCS) in 2010 and another in the following year or more, according to its TechNet Web site.

The server will include new features, including native E-911 support, designed to finally establish OCS as a PBX replacement rather than a complement, which is the positioning for the current version even with its new SIP-trunking features.

Clear Choice Test: Is Microsoft Office Communications Server your next IP PBX?

In addition, Microsoft will introduce a new Voice Client Access License (CAL) needed to access the new PBX-killer’s “enterprise-voice” features.


Microsoft is launching a promotion through its Software Assurance (SA) maintenance program to offer users up to two years free access to the new Voice CAL coming in OCS 2010.

OCS is the centerpiece of Microsoft’s unified communications strategy and includes instant messaging, presence, conference and VoIP features. In February, the company released the latest version, OCS 2007 R2.

The TechNet Web site did not provide a deep-dive on details of what the new Voice CAL includes, but in general it has all the current voice functionality in the Enterprise 2007 R2 CAL plus something entitled “enterprise ready voice – PBX Replace Voice,” Branch Survivability, E-911, PSTN Failover and Analog Device Support.

Rumors of a new Voice CAL for OCS first surfaced in February, but a blog posting on a TechNet Web site called The Three UC Amigos said that a news license will be required, and introduced a promotion to get users to commit to the new Voice CAL now.

The promotion will provide free access rights to the 2010 and 2011+ versions of the Voice CAL to any company that has SA coverage as of June 30, 2009 on their OCS Enterprise CAL or their Microsoft Enterprise CAL Suite.

Users will have to stay current on SA through the two releases of OCS.

The promotion offer also has the option of free access to only the 2010 version of the Voice CAL to those that purchase after July 1, 2009 an SA contract for their OCS Enterprise CAL or their Microsoft Enterprise CAL Suite.

Users who already have SA on OCS Enterprise CALs or their Microsoft Enterprise CAL Suite only have to keep their contracts current to get the new Voice CAL at no additional charge.

The Three UC Amigos posting said new OCS releases would come in 2010, which matches up with the Office 2010 roadmap Microsoft released Wednesday, and in “2011+.” The OCS releases were referred to as Wave 14 and Wave 15.

With Wave 14 there will be three CAL options and combinations: the Standard CAL covers IM and Presence; the Enterprise CAL adds conferencing; and the Voice CAL adds Voice.

More from Networkworld

Microsoft Office Communications Server 2007 Global Settings Migration Tool

Brief Description
Migrate OCS 2007 global settings from the System container to the Configuration container using the Microsoft Office Communications Server 2007 Global Settings Migration Tool.

Quick Details
File Name: MigrateOCS.msi
Version: 3.0.6362.105
Date Published: 12/10/2008
Language: English
Download Size: 363 KB

Overview
The Microsoft Office Communications Server 2007 Global Settings Migration Tool enables Administrators of existing deployments of OCS 2007 to migrate the OCS-specific global settings residing in Active Directory, from the root domain’s System container to the Configuration container. The migration of OCS global settings to the Configuration container provides a better solution for decentralized AD topologies.

Download

Office Communications Server 2007 R2 Documentation

Microsoft Office Communications Server 2007 R2 Documentation. Get all the R2 doc in one file