Comments on this page are supposed to improve article content and no technical support is provided. For technical questions, please visit project home page at: GitHub
Vadims Podāns
Vadims Podāns 15.05.2019 20:08 (GMT+3) Get-CATemplate

One workaround is to import the PSPKI command with prefix. Syntax:

Import-Module PSPKI -Prefix PSPKI

after that, all commands from PSPKI module will have prefix "PSPKI", e.g. Get-PSPKICATemplate. You can choose any prefix you prefer.

another workaround is to use explicit module prefix when calling a command:

AdcsAdministration\Get-CATemplate # will execute Get-CATemplate from AdcsAdministration module

PSPKI\Get-CATemplate # will execute Get-CATemplate from PSPKI module


IvoR 15.05.2019 19:48 (GMT+3) Get-CATemplate

The command "Get-CATemplate" is also available on the Microsoft side:


How can I use only the command from the ADCSadministration?

Vadims Podāns
Vadims Podāns 22.04.2019 12:36 (GMT+3) Approve-CertificateRequest

> How to provide credentials for the command, a'la Submit-CertificateRequest?

there is no way to provide custom credentials to management commands. Submit-CertificateRequest command supports custom credentials only when using CEP/CES enrollment web services. With DCOM custom credentials are not supported.

Stan 18.04.2019 11:21 (GMT+3) Approve-CertificateRequest

Hi Vadim,

How to provide credentials for the command, a'la Submit-CertificateRequest?

Stan 18.04.2019 10:45 (GMT+3) Get-IssuedRequest

$EFSTemplate = <OID of the template>
$certList = Get-IssuedRequest -CertificationAuthority <CA> -Filter "CertificateTemplate -eq $EFSTemplate" -Property *

$certList is an array of certificate information objects. This gets dump of all information about certificates.

What you're after is probably Request.RequestAttributes which provides info which PC ordered the cert and on whos behalf, then Request.RequesterName to find which user did that. The certificates are issued per user, not per computer.
Hope this helps.