RSA Private Key on Provisioning

[amarsden]

We have an application.

On installation it installs a certificate.  This certificate installs a Private Key (or so I believe) into C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys

This key, I think is keyed to the PC - so the one created in Provisioning is no good.

When the software runs I get

"Object contains only the public half of a key pair. A private key must also be provided"

Which is the same error message I get on a non-virtual PC when I remove the private key in the folder above.

Any ideas anyone?

Cheers

ACM

[irigoyen]

Hi, same problem...!

Does anyone have a solution?

[sjesse]

The snapvol.cfg is excluding it in appvolume templates. you either need to edit that file, or easier is just do the installs and then go to the folder C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys and grab the files that are created after the installs and copy them out. Then use something like uem to copy them back on logon. As long as your build machine is a direct clone of your paren image, this should work, and I'm doing this now for a similar problem.