I've made a copy of the Computer\/Machine template and modified it in such a way that we are able to supply the subject name in the request. Made one machine able to request these certificates and of course added admin approval. Now I can create a computer certificate by requesting one from the new Template and filling in the custom CN and subject alt name (don't forget the alt name, else it won't work!), also don't forget to tick the \"Make private key exportable\" option!<\/p>\n
Export the cert+key and import it on the pc that needs the computer cert. Voila… works for now…<\/p>\n
This is actually a relatively quick and easy fix, although I will admit, not so pretty. If you want to use this workaround to, please be aware of the security implications and be vigilant on the security settings and admin approval of this new template.<\/p>\n<\/blockquote>\n
Im Laufe des Threads gibt es dann die R\u00fcckmeldung zu einem weiteren Workaround: Sobald man den Credential Guard unter Windows 10 V1803 aktiviert, klappt der Zertifikatsbezug wieder. Der Credential Guard steht aber nur unter Windows 10 Enterprise zur Verf\u00fcgung. Wie schreibt mein Tipp-Geber: <\/p>\n
\nKann best\u00e4tigen dass es sich verh\u00e4lt wie beschrieben. Mit Credential Guard alles gut, ohne schlecht. Bitter f\u00fcr die, die Pro haben.<\/p>\n<\/blockquote>\n
Tja, Administratoren mit Windows 10 V1803 Pro schauen bez\u00fcglich des Credential Guard in die R\u00f6hre und m\u00fcssen eine der oben skizzierten Ma\u00dfnahmen \u00fcber Ex- und Import versuchen. <\/p>\n","protected":false},"excerpt":{"rendered":"
Zum Wochenstart noch eine kleine Information f\u00fcr Administratoren in Firmenumgebungen. Windows 10 V1803-Clients k\u00f6nnen wohl keine Enterprise CA (Computer Zertifikate) beziehen. Hier einige Informationen zum Thema.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3694],"tags":[24,4378],"class_list":["post-205311","post","type-post","status-publish","format-standard","hentry","category-windows-10","tag-problem","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/205311","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=205311"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/205311\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=205311"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=205311"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=205311"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![](\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2015\/01\/win102.jpg\")
Zum Wochenstart noch eine kleine Information f\u00fcr Administratoren in Firmenumgebungen. Windows 10 V1803-Clients k\u00f6nnen wohl keine Enterprise CA (Computer Zertifikate) beziehen. Hier einige Informationen zum Thema. <\/p>\n![\"Discussion\"](\"https:\/\/web.archive.org\/web\/20220416205448\/https:\/\/i1.social.s-msft.com\/globalresources\/Images\/trans.gif?cver=0%0d%0a\"\/)