Updating 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.

This topic describes the UpdatePoolBackend action.

UpdatePoolBackend Action

The UpdatePoolBackend action updates an existing SQL back-end database while preserving the Enterprise pool. This procedure:

  • Should be run during a planned downtime period.

  • Requires you to stop each Enterprise Edition Server within an Enterprise pool.

  • Requires that data be exported from old databases in a scale-up scenario and then imported into new back-end databases after the UpdatePoolBackend action is completed.

  • Requires a user with RTCDomainServerAdmins credentials.

  • Requires the /PoolName and /Poolbe parameters.

An example of the syntax for the UpdatePoolBackend action is:

LCSCmd.exe /Forest[:<forest FQDN>] /Action:UpdatePoolBackend /PoolName:<Pool Name> /Poolbe:<Pool BackEnd server FQDN\SQL instance name>

Such as:

LCSCmd.exe /Forest /Action:UpdatePoolBackend /PoolName:Pool01 /Poolbe:Pool01Backend.childdomain.domain.com\sql_server_instance_name

For more information about pools, such as Importing or Export settings see Exporting and Importing Settings later in this document.

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.