[This is preliminary documentation and is subject to change. Blank topics are included as placeholders.]

Imports a certificate for use with Microsoft Communications Server 2010. If a certificate is not acquired by using the Request-CsCertificate cmdlet, then that certificate must be imported before it can be assigned to a Communications Server server role.

Syntax


Import-CsCertificate -Path <String> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Password <String>] [-PrivateKeyExportable <$true \| $false>] [-Report <String>] [-WhatIf [<SwitchParameter>]]

Import-CsCertificate -Path <String> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Password <String>] [-PrivateKeyExportable <$true | $false>] [-Report <String>] [-WhatIf [<SwitchParameter>]]

Parameters

Parameter	Required	Type	Description
Path	Required	String	Full path to the certificate file to be imported. For example: –Path "C:\Certificates\WebServer.cer".
PrivateKeyExportable	Optional	Boolean	When set to True, ensures that the private key portion of the certificate can be read by the Network Service account.
Password	Optional	String	Password associated with the certificate file.
Report	Optional	String	Enables you to specify a file path for the log file created when the cmdlet runs. For example: -Report "C:\Logs\Certificates.xml"
Force	Optional	Switch Parameter
WhatIf	Optional	Switch Parameter	Describes what would happen if you executed the command without actually executing the command.
Confirm	Optional	Switch Parameter	Prompts you for confirmation before executing the command.

Detailed Description

Communications Server 2010 uses certificates as a way for servers and server roles to verify their identities; for example, Edge Servers use certificates to verify that the computer they are communicating with really is a Front End Server and vice versa. In order to fully implement Communications Server you will need to have the appropriate certificates assigned to the appropriate server roles.

In order for certificates to be assigned to a Communications Server role those certificates must be made known to Communications Server. If you use the Request-CsCertificate cmdlet to acquire new certificates those certificates will automatically be available for use with Communications Server. However, you might have other certificates (in .cer or .pfx format) that were not acquired using Request-CsCertificate. In that case, you must use Import-CsCertificate to import the certificates, a process that makes those certificates available for assignment to a Communications Server server role.

Return Types

Import-CsCertificate imports instances of the Microsoft.Rtc.management.Deployment.CertificateReference object.

Examples

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

	Copy Code
Import-CsCertificate -Path "C:\Certificates\WebServer.cer" -PrivateKeyExportable $True

The command shown in Example 1 imports the certificate C:\Certificates\WebServer.cer. After the command completes, the certificate will then be available to be assigned to a server role.