Topic Last Modified: 2010-10-01

Imports your Microsoft Lync Server 2010 topology, policies, and configuration settings to either the Central Management store or to the local computer.


Import-CsConfiguration -ByteInput <Byte[]> [-Force <SwitchParameter>] [-LocalStore <SwitchParameter>]
Import-CsConfiguration -FileName <String> [-Force <SwitchParameter>] [-LocalStore <SwitchParameter>]


Parameter Required Type Description



Byte array

Reads topology information from a byte array stored in a variable. This byte array is created by using the ByteInput parameter when calling Export-CsConfiguration.

You cannot use both the ByteInput parameter and the FileName parameter in the same command.




Path to the .ZIP file created by Export-CsConfiguration. For example: -FileName "C:\". Note that you must include either the FileName or the ByteInput parameter, but not both, when calling Import-CsConfiguration.



Switch Parameter

Bypasses any prompts that would otherwise appear should a non-fatal error occur when running the command. To set the Force parameter to True, use this syntax:




Switch Parameter

Copies the configuration data to the local computer rather than the Central Management store.

Detailed Description

Computers that run Lync Server 2010 services or server roles must have a copy of the current topology, current configuration settings, current policies, and so on before they can function in their appointed role. Lync Server is responsible for ensuring that this information is passed along to each computer that needs it.

The Import-CsConfiguration and Export-CsConfiguration cmdlets are used to backup and restore your Lync Server topology, configuration settings, and policies during a Central Management store upgrade. The Export-CsConfiguration cmdlets enables you to export data to a .ZIP file; you can then use the Import-CsConfiguration cmdlet to read that .ZIP file and restore the topology, settings, and policies to the Central Management store. After that, Lync Server’s replication services will replicate the restored information to computers running services.

The ability to export and import configuration data is also used when initially configuring computers located in your perimeter network (for example, Edge Server). When configuring a computer located in the perimeter network, you must first perform a manual replication using the CsConfiguration cmdlets: you will need to export the configuration data using Export-CsConfiguration and then copy the .ZIP file to the computer in the perimeter network. After that, you can use Import-CsConfiguration and the LocalStore parameter to import the data. You only need to do this once; after that, replication will take place automatically.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Import-CsConfiguration cmdlet locally: RTCUniversalServerAdmins. In addition to being a member of RTCUniversalServerAdmins, you must also be a local administrator or have local configuration replicator permissions to run this cmdlet. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Import-CsConfiguration"}

Input Types

None. Import-CsConfiguration does not accept pipelined input.

Return Types

Import-CsConfiguration does not return any values or objects.


-------------------------- Example 1 ------------------------

Copy Code
Import-CsConfiguration -FileName "C:\"

The preceding command imports the current topology, configuration settings, and policies from a file named C:\ to the Central Management store.

-------------------------- Example 2 ------------------------

Copy Code
Import-CsConfiguration -FileName "C:\" -LocalStore

Example 2 shows how data can be initially replicated to a computer located in the perimeter network. In this example, configuration data has been exported to a file named; this file has then been copied to the C:\ folder on the computer located in the perimeter network. Import-CsConfiguration is then used to import that data, with the LocalStore parameter causing that data to be imported to the local computer instead of the Central Management store.

-------------------------- Example 3 ------------------------

Copy Code
$x = Export-CsConfiguration -AsBytes
Import-CsConfiguration -ByteInput $x -LocalStore

The two commands shown in Example 3 export the current topology, configuration settings, and policies and then import that data to the local computer, all without using a .ZIP file. To do this, the first command uses Export-CsConfiguration and the AsBytes parameter to export the current topology, configuration settings, and policies as a byte array; this byte array is stored in a variable named $x. In the second command, Import-CsConfiguration and the ByteInput parameter are used to import the information stored in $x. The LocalStore parameter causes the data to be imported to the local computer instead of the Central Management store. The net effect is that data is copied from the Central Management store to the local computer.

See Also

Other Resources