Preparing Enterprise Pools for Office Communications Server
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
The following Forest-related actions prepare, create, check, remove or update an Enterprise pool. These actions include:
| Action | Description |
|---|---|
CreatePool |
Initial procedure for deploying an Enterprise pool. For more information, see Creating Pools. |
CheckPoolState |
Verifies a pool in a forest. For more information, see Checking Pools. |
CheckAllPoolsState |
Verifies and lists all Standard and Enterprise pools in a forest. For more information, see Checking Pools. |
RemovePool |
Removes an Enterprise pool. For more information, see Removing Pools. |
UpdatePoolBackend |
Allows changes to a back-end without compromising an existing Enterprise pool. For more information, see Updating Pools. |
When you run LCSCmd.exe, the command automatically discovers the global catalog server and primary domain controllers. If you experience problems because these servers are unavailable or network connectivity is poor, you can use optional parameters to specify the global catalog server or domain controllers to use instead. For more information, see Optional LCSCmd.exe Parameters for Domain Controller and Global Catalog Server Discovery later in this document.
An example of the syntax used with pool actions:
LCSCmd.exe /Forest[:<Forest FQDN>] /Action:<action name> /PoolName:<pool name> /PoolBE:<SQL instance name (computer\instance name)> /RefDomain:<Domain FQDN> /DBDataPath:<DB data file path> /DBLogPath:<DB log file path> /DynDataPath:<Dynamic DB data path> /DynLogPath:<Dynamic DB log path> /MeetingContentPath:<Meeting content UNC path> /MeetingMetaPath:<Meeting meta data UNC path> /PoolFQDN:<Pool FQDN> /InternalWebFQDN:<Internal Web FQDN> /ABOutputlocation:<UNC Path to NTFS Folder> [/PDCRequired[:{TRUE|FALSE}]] ][/RootDC:<DC FQDN>] [/DC:<domain controller FQDN>][/GC:<GC FQDN>] [/Global:{Configuration | System}] [/GroupDomain:<Group Domain FQDN>] [/GroupDomainDC:<Group Domain DC FQDN>] [/Clean[:{TRUE|FALSE}]] ][/EnableArch[:{TRUE|FALSE}]] [/EnableCDR[:{TRUE|FALSE}]] [/ExternalWebFQDN:<External Web FQDN>] [/MeetingArchivingPath:<Meeting content archiving UNC path>] [/Force[:{TRUE|FALSE}]] [/L:<log file path>] [/XML[:{TRUE|FALSE}]] [/?[:{TRUE|FALSE}]]
The parameters used in the preceding example are described in the following table.
| Parameter | Description |
|---|---|
/Forest |
<Forest FQDN> |
/Action |
<Action name> |
/PoolName |
<Pool name> |
/PoolBE |
<SQL instance name (computer\instance name)> |
/RefDomain |
<Domain FQDN> |
/DBDataPath |
<Database data file path> |
/DBLogPath |
<Database log file path> |
/DynDataPath |
<Dynamic Database data path> |
/DynLogPath |
<Dynamic Database log path> |
/MeetingContentPath |
<Meeting content UNC path> |
/MeetingMetaPath |
<Meeting meta data UNC path> |
/Global |
{Configuration | System} |
/GroupDomain |
<Group Domain FQDN> |
/Clean |
[{TRUE|FALSE}] |
/EnableArch |
[{TRUE|FALSE}] |
/EnableCDR |
[{TRUE|FALSE}] |
/PoolFQDN |
<Pool FQDN> |
/InternalWebFQDN |
<Internal Web FQDN> |
/ExternalWebFQDN |
<External Web FQDN> |
/ABOutputlocation |
<UNC Path to NTFS Folder> |
/MeetingArchivingPath |
<Meeting content archiving UNC path> |
/Force |
[{TRUE|FALSE}] |
/L |
<Log file path> |
/XML |
[{TRUE|FALSE}] |
/? |
[{TRUE|FALSE}] |
The /Clean switch will replace any existing databases. Use the /DBSetupFilePath parameter (described in LCSCmd.exe Parameters and Switches) to find the DBsetup script and the related database configuration files, otherwise the LSCmd.exe command searches for it from the folder from which it is run. There is no option to select the database name.