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.

For each action associated with a context, there are several parameters you can specify. Lets use the Server context as an example. Suppose you want to activate a Standard Edition server. You do this by using the server context with the activate action, like this.

LCSCmd /server /action:activate

However, if you run this command youll receive an error. The Server context applies to several different types of servers: Standard Edition, Enterprise Edition, Proxy Servers, and Edge Servers. The preceding command did not specify which type of server role to activate. To do that, include the /Role parameter, in this case specifying SE for Standard Edition.

LCSCmd /server /action:activate /role:SE

Action parameters will be discussed in detail in the Task-Based Scenarios section. However, there are several parameters that are global to almost all actions and contexts. This table shows a list of parameters you can specify with almost any context or action.

Parameter Description


Specifies the log file path. If not specified, %TEMP%\<ActionName>[<Date>][<Time>].html is used. To disable logging, use a dash character (-) as the log file name.


Specifies whether the log file to be generated should be in XML format instead of HTML.


Shows Help on usage.

LCSCmd also provides a set of parameters for domain controller and global catalog server discovery, listed in the following table. If you specify these parameters at any time during deployment, continue to specify the parameters (and the same parameter values) for subsequent actions.

Parameter Description


Specifies whether the primary domain controllers (PDCs) are required for the action. If not specified, TRUE is used. You can set this parameter to FALSE if the PDCs (in the current or specified domain and the root domain) are unavailable or if network connectivity to the PDCs is poor.

For most network issues, /PDCRequired:FALSE is the only parameter you will need to use. The other parameters in this table, used to specify a specific domain controller or global catalog server, are optional.


Specifies the fully qualified domain name (FQDN) of the global catalog server that you want to use. You must also specify /PDCRequired:FALSE to override automatic discovery of a global catalog server.


Specifies the FQDN of a domain controller in the domain where Office Communications Servers reside. You must also specify /PDCRequired:FALSE to override automatic discovery of the PDC.


Specifies the FQDN of the domain controller (DC) of a global settings domain. If the settings are in a configuration container this must be a local domain DC. If the settings are in the system container, this must be a root DC.


Specifies the FQDN of a domain controller in the domain where Office Communications Server universal groups are located. You must also specify /PDCRequired:FALSE to override automatic discovery of the primary domain controller.

When you run LCSCmd.exe, the command automatically discovers the global catalog server and PDCs. If you experience problems because these servers are unavailable or network connectivity is poor, you can use these optional parameters to specify the global catalog server or domain controllers to use instead.