The
Note: |
---|
Ensure that the user who runs the
|
Use the following as an example.
Copy Code | |
---|---|
LCSCmd.exe /Forest[:<forest FQDN>] /Action:CreatePool /PoolName:<Pool Name> /PoolBE:<Pool BackEnd Server name\SQL Server instance name> [/PoolFQDN:<Pool FQDN>] [/InternalWebFQDN:<Internal Web FQDN>] /RefDomain:<domain FQDN> /AppDataLocation:<Application Data UNC Path> /ClientUpdateLocation:<UNC path to NTFS folder> [/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}]] [/EndableQoE:{TRUE|FALSE}] [/ExternalWebFQDN:<External Web FQDN>] [/ABSDataPath:<address book server DB data path>] [/ABSLogPath:<address book server DB log path>] [/Force:{TRUE|FALSE}] |
Such as:
Copy Code | |
---|---|
LCSCmd.exe /Forest /Action:CreatePool /PoolName:Pool01 /RefDomain:woodgrovebank.com /MeetingContentPath:\\OCSShares\MeetingContent /MeetingMetaPath:\\OCSShares\Metadata /AppDataLocation:\\OCSShares\AppData /ClientUpdateLocation:\\OCSShares\ClientUpdate |
Be sure not to include a backslash (\) at the end of a folder
path. Doing so results in a command-line parsing error. You will
also receive an error if you specify only one of the database path
values. If you specify a value for any of the database paths
(DBDataPath, DBLogPath, DynDataPath, DynLogPath, ABSDataPath,
ABSLogPath, ACDDataPath, ACDLogPath), you must specify values for
all these paths. (This is done because if you specify a value for
one path, the
If the user who runs the
If necessary, you can force
After this action is completed, activate Enterprise Edition servers to the pool. Activation fails if the action cannot find the pool on the root domain global catalog server used during activation. Other points to remember when undertaking this action include:
- RTCDomainServerAdmins credentials are required for the domain
where the pool is deployed.
- Local administrator credentials are required on the Enterprise
pool back-end server.
- Run the task from an Enterprise pool back-end server if
possible.