Skip to content

CrossForest PKI Connect-CertificationAuthority doesn't show displayname #177

@DanTheMan-NL

Description

@DanTheMan-NL

Whenever I use Connect-CertificationAuthority -ComputerName {FQDN} to a CA in a different forest I receive an output without the displayname:

DisplayName                              ComputerName              IsAccessible ServiceStatus Type
-----------                              ------------              ------------ ------------- ----
                                         FQDN.example.com     True         Running       Enterprise Subordinate CA

Appearently the displayname is necessary for other commands to function properly because when I use this command output with another command I receive this error:

PS C:\windows\system32> Connect-CertificationAuthority -ComputerName {FQDN} | Get-PendingRequest
Get-AdcsDatabaseRow : Exception calling "GetDbReader" with "1" argument(s): "CCertView::OpenConnection: The RPC server is unavailable. 0x800706ba (WIN32: 1722 RPC_S_SERVER_UNAVAILABLE)"
At C:\Program Files\WindowsPowerShell\Modules\pspki\3.7.2\Server\Get-PendingRequest.ps1:23 char:13
+             Get-AdcsDatabaseRow `
+             ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-AdcsDatabaseRow

I have not synced the CA objects with the forest where this management server is stationed and I'm not willing to do that because of security- and operational reasons.

In this issue I read this should be possible without syncing the objects: #26

Is there anyway to do this? I really want to use PSPKI on a management server in a different forest without having to sync the CA objects to this forest.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ResearchRequires additional research or specification clarification

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions