Building the Cert file to create a new Trusted Point in UCS
Creating the Trusted Point in UCS Manager
https://www.derekseaman.com/2012/04/install-trusted-ssl-certificate-in.html https://community.cisco.com/t5/unified-computing-system/pki-cert-issue-ucs-manager/td-p/2004407
0 Comments
Applying a Certificate to a Dell iDRAC Controller when using an internal Enterprise CA using ADCS
Applying an internal SSL certificates to devices to make sure all devices can be opened easily and without warnings in all browsers. These directions have worked so far on all recent versions of iDRAC (7, 8, & 9). Note the Gotcha in step 6 when using an internal CA.
When using an internal Microsoft Certificate Authority, there was a small gotcha installing an SSL certificate on the PRTG web interface.
Use this article in order to install the SSL certificate on the PRTG server. You will also need OpenSSL installed on a machine as well: kb.paessler.com/en/topic/283-how-can-i-use-a-trusted-ssl-certificate-with-the-prtg-web-interface#reply-713 There is only ONE thing to note on this procedure. The COMMON NAME you give the certificate during the OpenSSL process is apparently not used at all with PRTG. So you will want to add ALL the Subject Alternative Names in the additional attributes portion of the request in IIS on CertSrv including the primary name you might use to access the server's web interface. For example, on a server named PRTG1 you would included all these SANs: san:ipaddress=10.10.10.15&dns=prtg1&dns=prtg1.internaldomain.com Which Translates to the following in the SAN portion of the cert: IP Address=10.10.10.15 DNS Name=prtg1 DNS Name=prtg1.internaldomain.com This allows us to hit PRTG from any of those names without a certificate warning. |
|