Hi all,
I get more and more reports from the users of my ESXi-Customizer-PS script that they run into errors with the latest release 6.3 R1 of PowerCLI.
With one of them I confirmed that the issue is not specific to my script, but also occurs after manually running commands like these:
Add-ESXSoftwareDepot "https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml"
Add-ESXSoftwareDepot "https://vibsdepot.v-front.de"
$CloneIP = Get-EsxImageProfile "ESXi-6.0.0-20160302001-standard"
$MyProfile = New-EsxImageprofile -CloneProfile $CloneIP -Vendor $CloneIP.Vendor -Name ($CloneIP.Name + "-customized") -Description ($CloneIP.Description + " (customized)")
$vib = Get-EsxSoftwarePackage "net-atl1"
$MyProfile.AcceptanceLevel = $vib.AcceptanceLevel
Add-EsxSoftwarePackage -SoftwarePackage $vib -Imageprofile $MyProfile
$outfile = (Get-ChildItem env:temp).Value + "\" + $MyProfile.Name + ".iso"
"Exporting to $outfile"
Export-EsxImageprofile -Imageprofile $MyProfile.Name -ExportToISO -FilePath $outfile
The Export-EsxImageProfile command throws the error
Cannot instantiate 'certified' policy: VibSign module missing.
Unfortunately I cannot reproduce this error myself, but I got reports of at least three different users experiencing this issue.
Can anyone of the developers jump in and explain, what this error means, or how to troubleshoot it?
Thanks
Andreas
thanks for logging this, we are looking into it at the moment and will update you with our findings soon.
Try inserting the -NoSignatureCheck flag in the Export-EsxImageProfile line as shown in the below example:
PowerCLI c:\vm> Export-EsxImageProfile –ImageProfile Image1 –FilePath ESXi-6.0.0-2494585-
aacraid-b41024.iso –NoSignatureCheck -ExportToIso
I was unable to create a ESXI6 ISO containing drivers for my Adaptec 6805 card due to the error you reported. All other examples on the web omitted this flag, though the examples were posted prior to the release of PowerCLI 6.3. I found this argument in Adaptec documentation buried within the zipped driver folder and inserted it, then created the ISO with no issue.
Hope this helps.
According to the Release Notes this issue has been fixed in PowerCLI 6.3 R1 Patch 1.
So far I have not got any feedback from concerned users. Can anyone who has experienced this issue confirm that it is fixed in Patch 1?