Applies to: Windows PowerShell 5.0
You probably ran into this error while using a Windows 10 or Windows Server 2016 Technical Preview when attempting to encrypt DSC configuratiosn, as I did. For some reason, the certificates I had been using no loneger worked. When I attempted to ecnrypt my DSC configurations I got the above error saying the the function ConvertTo-MofInstance failed and that the certificate that I was using could not be used for document encryption. It also told me what the issue was “encryption certificates must contain the data encipherment or key encipherment key usage, and include the document encryption enchanged key usage” At the time, I had no clue what that meant. To fix this continue reading….
How to Fix the Certificate
Examining the output, it says the certificate I gave the configuration cannot be used for encryption. It also points out why by saying that our certificate doesn’t have the Data Encipherment or Key Encipherment key usages. At first this turned into a short moment of insanity while I just ran the config over and over again hoping the error would go away. I even rebooted all my virtual machines a few times for good measure, but the error always returned. After a little light reading on certificates and Active Directory Certificate Services I understood what I needed to do. What I discovered was in PowerShell version 5, the version on Windows 10 and Windows Server 2016 require that the certificates have the extension Document Encryption. From what I understood it requires this to allow a longer encryption password.
Certificates Issued through Active Directory Certificate Services
So….. how do you fix it? Start by opening the Certification Authority administration tool from either a client machine with RSAT on it or by logging into the Certification Server (This is a trick don’t do it). Then follow the steps below to include document encryption into the existing certificate.
- Expand the server name within Certification Authority
- Locate Certificate Templates
- Right click select Manage
- Find the certificate issued to the machines (typically a duplicate of the Computer or workstation authentication template)
- Right click and select Properties
- Click on the Extensions tab
- Click Application Policies and then edit
- Click add
- Locate Document Encryption and double click it then hit OK
- Click OK twice to close out of both Property boxes
With the certificate extension updated you now need to re-enroll all of the certificate. To do that right click on the certificate and click “Reenroll All Certificate Holders”
With all certificate holders re-enrolled you can begin encrypting .mof files once again!
Self Signed Certificates
Another way you might have issued the certificates is by generating a self signed certificate. I’m currently not aware of how you’d modify an existing certificate, but you could use the New-SelfSignedCertificateEX to generate a new certificate. Below is a snippet of code that shows the syntax of how to accomplish that, I’m using a technique called splatting to provide the parameters.