Good afternoon,
I installed the ILO powershell cmdlets, and am very excited that I can start automating management of numerous ILOs using powershell.
The first thing I did was generate a bunch of Certificates, but hit a snag when I went to import them with the "Import-HPiLOCertificate" cmdlet. I kept getting an error saying "invalid common name" when attempting to import certificates.
Checklist:
the ILO FQDNs are entered into DNS with the correct IP address. format is HOSTNAME-ilo.domain.local
these are DL360 Gen 9, and there are 4 places you must designate "the network name" of the ILO, and I double and triple checked that all are entered correctly and the same (even upper and lower case for that matter)
the "Get-HPiLOCertificateSigningRequest" powershell cmdlet worked flawlessly to create the certificate request files (.CSR or .REQ) other than I have to write in a delay to check if status has completed generating the cert - it takes a minute or two even if you click the button in the GUI.
I have a script that signs the certificates in the CA against what is in DNS. signing works for other services (like SCOM and SCCM) and I can manually sign them as well.
Manually importing by logging into the ILO and copy / paste in the certificate dialog box works without a problem.
has anyone else encountered this?
Thanks!
Tim
Code: (simplified for this post, but will work as is)
$creds= Get-Credential Administrator
$servers = (Get-Content ILOlist.txt) #local txt file with short names like HOSTNAME-ilo
foreach ($server in $servers)
{
$ILOCSR = Get-HPiLOCertificateSigningRequest -Server $server -credential $creds
$ILOCSR.CERTIFICATE_SIGNING_REQUEST | Out-File C:\temp\Certs\ILO\$server.req -width 64 -Encoding ascii
}