Filter
Top Products
Appendix H-Setting the MCU for Integration Into Microsoft Environment
Polycom, Inc. H-45
28 Click the Browse button.
The Open dialog box appears, letting you select the certificate file(s) to send to the MCU.
Depending on the method used when the certificate file(s) were created, send the
certificate file(s) to the MCU according to the contents of the file set that was created:
— The certificate files pkey.pem, cert.pem and a certPassword.txt. The files were created
by a Certificate Authority and are sent as is to the MCU together with the required
password contained in the certPassword.txt file.
This is the recommended method.
— The files pkey.pem and cert.pem. The certificate files were created by a Certificate
Authority and are sent as is to the MCU.
— A *.pfx file and a certPassword.txt file. The file certPassword.txt is manually created if
the *.pfx file was created by the OCS using a password. The *.pfx file will be
converted internally by the MCU using the password included in the
certPassword.txt into three certificate files named pkey.pem and cert.pem.
— A *.pfx file if the certificate file was created in the OCS without using a password.
The *.pfx file will be converted internally by the MCU into three certificate files
named pkey.pem and cert.pem.
29 In the file browser, select all files to be sent in one operation according to the contents of
the set:
— One *.pfx file, or
— Two files: one *.pfx file and certPassword.txt, or
— Three files:pkey.pem, cert.pem and certPassword.txt
30 Click Open.
The selected file(s) appear in the Install Files path.
31 Click Install.
The files are sent to the MCU and the Install File dialog box closes.
32
In the Default IP Service - Networking IP dialog box, click OK.