Hi All,
I am trying to customise ESXi 5.0 installation by using PowerCLI image builder and VMware depot file as the base. i need to add some NIC drivers during the customization and create a bundle .zip file to be used during autodeploy.
Using Image Builder through PowerCLI, I am able to use Add-EsxSoftwareDepot to add the base VMware Autodeploy depot file and also add the NIC driver as software packages (using Add-EsxSoftwarePackage).
I am also able to export the new profile image to a bundle or ISO.
Using the bundle when I try to run the Export-EsxImageProfile command it throws an error “Could not find a trusted signer”. This is because the NIC drivers are self-signed by the vendor and not signed by a trusted source.
At this stage I am able to get through using –NoSignatureCheck and proceed with creating the .zip or ISO file.
Now when I connect to the vCenter server using PowerCLI and create a New-DeployRule I face the same error. "Could not find trusted signer"
This time, I see that the new deploy rule command doesn’t have a –NoSignature check parameter.
I extracted the ZIP and added the certificates in the VIB to vCenter server’s trusted root. I ran the New-DeployRule command again, and still face the same error.
I am looking for a workaround for this so that I can test the new NIC’s. I have tried to make this work by changing the acceptance level to CommunitySupported and also the Set-ExecutionPolicy in PowerShell to Bypass/Allsinged/RemoteSigned. Still I face the same error.
thanks...