Windows 10: Trying to generate a custom CSR using certificates snap-in. Only legacy crypto providers...

I'm trying to generate a custom CSR but if I choose no template CNG key. I will get the error "One or more of the object's poroperties are missing or invalid".The request has the following parameters edited for PII protectionCN=<my initials>, C=<My Country>, O=<My company>, OU=<my department>, E=<my email>Extensions: Key Usage = Digital Signature, Extended Key Usage = Client AuthenticationChoosing No template Legacy Key, will work but I want an ECC key and the legacy providers don't support ECC.This is apparently not a common failure. Google finds very few

:)

 

CSR V4.0 Dongle "malfunction"

Hi, Carter,

Try these steps from Johan van Mierlo

In the search type" Device manager" and open it.

Click on the small arrow next to either "Bluetooth" or "Universal Serial Bus controllers"

Right click on "CSR" and select Update Driver

Select" Browse my computer for driver update"

Select on bottom "Let me pick from a list of available drivers on my Computer"

Select "Generic bluetooth Driver"

https://answers.microsoft.com/en-us/windows/for...

 

Creating a User certificate CSR for default admin account

Hello, we plan on deploying factory fresh Windows 10 machines to our users direct from manufacturer. They will initially connect to our VPN for 'domain-joining' of their factory fresh laptops,

However, our VPN connection requires a user certificate for authentication.

How can I generate a generic 'admin' user certificate for deployment to all of these factory fresh computers BEFORE they connect to our domain ?

I have already tried creating a CSR on another domain joined machine and submitting this to our CA however I am unable to alter the 'Issued to' and 'Subject' fields to a generic 'admin' username.

Thank you for any help.

 

Issue installing certificate chain on Windows Mobile 6.5

Hi my Friend, in case you havent noticed im from Portugal, US President Obama was here yesterday and love it, so you may too!

I know the solution, your problem is about Root CA which has an hash Algoritm SHA256, and the devices with WM6 doesnt support that yet. I understand your concern about security, but you should do this Precise steps.

• On your CA, you must remove CA Services from your server. Reboot later so.
• Add CA Role again, but this time, choose Hash Algoritm to be SHA1 or MD5 (It's very important choosing this one's because the devices doesnt understand new hashes, such as sha512). This selection is for generate your root CA default cert.
  In compensation of swaping the old one for this, try to select the maximum bits which are 4096
• Go to Exchange Web Server, in IIS Role create csr text file, save it to a network drive.
• Again in your CA server, paste the csr content in the web page localhost/certsrv, after select sucessive steps to get in advanced completion csr.
• download the new client certificate and place-it in your web access server and switch it in your Forefront Server.
• Done try to syncronize And voila.

1. Dont forget to Export the new CA certificate in x.509 Bin mode without pki of course,

2. and export Client Certificate in *.pfx file.

Import again, but this time by the sequence mentioned above.

I hope this help you.