Creating Pools
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 CreatePool action starts an Enterprise pool deployment by creating the necessary Active Directory Pool and Trusted Server objects. CreatePool also builds an Enterprise pool back-end with User and Configuration Databases. CreatePool also grants access permissions to the shared folders used to store Address Book information, meeting content, and meeting metadata.
Note
Ensure that the user who runs the CreatePool action has been granted Full Control of the shared folders specified by the command. If you run the CreatePool action without full administrative control of the shared folders, the CreatePool action will fail.
Use the following as an example:
LCSCmd.exe /Forest[:<forest FQDN>] /Action:CreatePool /PoolName:<Pool Name> /Poolbe:<Pool BackEnd Server name\SQL instance name> [/PoolFQDN:<Pool FQDN>] [/InternalWebFQDN:<Internal Web FQDN>] /RefDomain:<domain FQDN> /DBDataPath:<path> /DBLogPath:<path> [/dbsetupfilepath:<path>] /DynDataPath:<Dynamic DB data path> /DynLogPath:<Dynamic DB log path> [/ABOutputlocation:<UNC path to NTFS shared folder for Address Book information>] /MeetingContentPath:<UNC path to NTFS shared folder for meeting content> /MeetingMetaPath:<UNC path to NTFS shared folder for meeting metadata> [/MeetingArchivingPath:<UNC path to NTFS shared folder for archiving meeting content and meeting activities>] [/GroupDomain:<Group Domain FQDN>] [/Clean[:{TRUE|FALSE}]] [/EnableArch[:{TRUE|FALSE}]] [/EnableCDR[:{TRUE|FALSE}]] [/ExternalWebFQDN:<External Web FQDN>] [/Force[:{TRUE|FALSE}]] [/Force]
Such as:
LCSCmd.exe /Forest /Action:CreatePool /PoolName:Pool01 /Poolbe:Pool01-backend\Live /PoolFQDN:Pool01.corp.woodgrovebank.com /InternalWebFQDN:Pool01.corp.woodgrovebank.com /RefDomain:corp.woodgrovebank.com /dbdatapath:e:\Microsoft\LC Data/dblogpath:d:\Microsoft\LC Log /DynDataPath:e:\Microsoft\LC DynData /DynLogPath:d:\Microsoft\LC DynLog /ABOutputlocation:\\OCSShares\ABS /MeetingContentPath:\\OCSShares\MeetingData /MeetingMetaPath:\\OCSShares\MetaData
Note
Ensure you do not include a backslash () at the end of a folder path or it will result in a command-line parsing error.
If the user who runs the CreatePool action does not have Full Control of the shared folders specified by the command, if the folder path is not in UNC format, or if the shared folders are not on an NTFS partition, then the CreatePool action will not complete successfully. If necessary, you can force CreatePool to complete even if there are problems granting access permissions to the shared folder, and then manually grant access permissions to the shared folders. To do so, run the CreatePool action including the /Force parameter. After CreatePool is complete, you can search the log file for "Action Error" messages to see what steps you need to manually complete.
After this action is completed, activate Enterprise Edition Server servers to the pool. Activation fails if the action cannot find the pool on the root domain global catalog server used during activation.
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.