pspki Discussions Rss Feed

New Post: Import-module pskpi error

Camelot — Mon, 29 Apr 2013 09:47:56 GMT

looks like you have strange encoding issue. Try to fix these weird characters with normal ones.

New Post: Import-module pskpi error

lvnhjj — Mon, 29 Apr 2013 05:53:25 GMT

Hi，Camelot.
because when i was trying to import module pspki
i get the error like below.
i think the powershell can not regonize those tow strange command . 1 朏unction 2 朚odule two
Although i have corrected to function and module , it didn't work.
so, i have to make the "#" before those two line to annotate it .

Export-ModuleMember <<<< 朏unction @(Get-Command 朚odule $ExecutionContext.SessionState.Module | Where-Object {$Rest
rictedFunctions -notcontains $_.Name})
- CategoryInfo : InvalidArgument: (:) [Export-ModuleMember], ParameterBindingException
- FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.ExportModuleMemberCommand
Export-ModuleMember -Alias @(Get-Command <<<< 朚odule $ExecutionContext.SessionState.Module)
- CategoryInfo : ObjectNotFound: (朚odule:String) [Get-Command], CommandNotFoundException
- FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.GetCommandCommand

New Post: Import-module pskpi error

Camelot — Sat, 27 Apr 2013 07:09:09 GMT

lvnhjj wrote:

HI，Guys
you can modify the psm1file in the line 202 and 203 like below,
take attention for the "#"

export module members

Export-ModuleMember 朏unction @(Get-Command 朚odule $ExecutionContext.SessionState.Module | Where-Object {$RestrictedFunctions -notcontains $_.Name})

Export-ModuleMember -Alias @(Get-Command 朚odule $ExecutionContext.SessionState.Module)

why do I need to change there anything? I think, Export-ModuleMember commands are executed correctly.

New Post: Import-module pskpi error

lvnhjj — Sat, 27 Apr 2013 07:00:36 GMT

HI，Guys
you can modify the psm1file in the line 202 and 203 like below,
take attention for the "#"

export module members

Export-ModuleMember 朏unction @(Get-Command 朚odule $ExecutionContext.SessionState.Module | Where-Object {$RestrictedFunctions -notcontains $_.Name})

Export-ModuleMember -Alias @(Get-Command 朚odule $ExecutionContext.SessionState.Module)

New Post: Import-module pskpi error

lvnhjj — Sat, 27 Apr 2013 06:39:37 GMT

sorry ，i have mistyped pspki for pskpi。
OMG！！！

New Post: Import-module pskpi error

lvnhjj — Sat, 27 Apr 2013 03:42:15 GMT

when i was trying to import the module to ps,
i got the error like this
also i have tryed to replace the psm1 file in the below link
https://pspki.codeplex.com/workitem/30

Import-Module : The module to process 'PSPKI.psm1', listed in field 'ModuleToProcess' of module manifest 'C:\Windows\sy
stem32\WindowsPowerShell\v1.0\Modules\PSPKI\PSPKI.psd1' was not processed because no valid module was found in any modu
le directory.
At line:24 char:34
+                     Import-Module <<<<  $_.Name -ErrorAction SilentlyContinue
    + CategoryInfo          : ResourceUnavailable: (PSPKI:String) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : Modules_ModuleFileNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand__

New Post: Source Code

Camelot — Sun, 14 Apr 2013 09:58:27 GMT

Sources are available: https://pspki.codeplex.com/releases/view/101174

New Post: Source Code for PKI.Core.dll

Camelot — Sun, 14 Apr 2013 09:57:41 GMT

finally, the source code for PKI.Core.dll library is published: https://pspki.codeplex.com/releases/view/101174

New Post: Source Code for PKI.Core.dll

Camelot — Mon, 28 Jan 2013 08:13:19 GMT

I have plans to pull out PKI.Core.dll sources in the next release.

New Post: Source Code for PKI.Core.dll

harperse — Wed, 09 Jan 2013 13:13:36 GMT

Vadims,

Would you consider publishing the source for the PKI.Core.dll? I would like to implement the scripts in my enterprise, but the obvious sensitive nature of the environment keeps us from using any untrusted closed-source DLLs.

Sean

New Post: Can't load the module via remote

Camelot — Fri, 16 Nov 2012 13:24:29 GMT

Hi, PSPKI is not supported to run in remote sessions (via PS Remoting) due to its design and there are no plans to add this support. Module already uses (or intended to use) remote connections to CA servers. If you will run PSPKI module in remote sessions the module will become unusable because of credential delegation issue. Here is a short example:

1) ComputerA (your worksation) -> ComputerC (CA server)

2) ComputerA (your worksation) -> ComputerB -> ComputerC (CA server).

when you run your script on ComputerA and access CA server on ComputerC, the script will work fine, because you are authenticated directly.

When you run commands remotely on ComputerB, the script will fail, because ServerB has delegated credentials and they cannot be used to authenticate you on ComputerC. To resolve this you have to do either:

1) allow credential delegation for ComputerB. Many administrators don't like this option, because it is unsecure. ComputerB will be able to authenticate anyone on other computers and you are in risk of network compromise if only single ComputerB is compromised.

2) use explicit credentail transfer: CredSSP. This is alternate approach. This is more secure way to delegate credentials, however it requires additional configuration, explixit CredSSP use. Also I never tested CredSSP in remoting with smart cards and can't guarantee that this would work as expected.

In addition, I put a lot of effort to make commands in the module to support remote systems as much as possible (though, certain commands runs only locally, however). My main idea is to use the module on administrator's workstation (not directly on CA servers), so he is able to perform required PKI-related management tasks without having to log on to CA servers. That is, if you want to collect some reports about revoked certificates, you should run the module locally, collect all required data from remote CA servers and process them locally too.

New Post: Can't load the module via remote

digiflex — Fri, 16 Nov 2012 10:26:27 GMT

Hi Guys,

Currently, i try to trigger a script with serverA on serverB. I load the PSPKI module In the script on serverB. But thats not possible.

When i trigger ther script on ther serverB with the following code:

Invoke-Command -ComputerName 'serverB' -ScriptBlock {&'E:\Scripts\Dev\Thomas\CA\CAUserRevokedReport - Copy.ps1'}

I receive the message that my remote server have the Powershell version 1.0 but the server is an 2008R2 and Powershell 2.0 is installed by default.

An colleague Peter Kriegel from the german powershell technet forum means that the script works with the command get-host to match the powershell versions but the better way is to use the environmet variable $PSVersionTable. I think so too and can explain my issue with that. Because an Remote session with get-host return allways the version 1.0. This problem is also not solved in the version 3 of Powershell. Have you already an fix for it or an workarround?

best regards
Thomas

New Post: Exclude autoenroll certificates

Camelot — Fri, 12 Oct 2012 08:23:51 GMT

unfortunately, there is no way to determine whether the certificate was issued during autoenrollment or manual request process.

BTW, depending on your DNS configuration, you can use short CA host name (NetBIOS name).

New Post: Exclude autoenroll certificates

jyrkis700 — Fri, 12 Oct 2012 07:23:32 GMT

I would like to list all issued certificates except autoenrollment ones.
My script shows all issued. How to change this code that autoenrollment ones are excluded?
***********************************
$caname = $computername.ToLower()

$domaindns = $ENV:USERDNSDOMAIN.ToLower()

$todaysdate = Get-Date$

enddate = $todaysdate.AddMonths(2)

$issuedcerts = Get-CertificationAuthority “$caname.$domaindns” | Get-IssuedRequest -property * -Filter "NotAfter -ge $todaysdate", "NotAfter -le $enddate" | sort-object NotAfter, NotBefore

New Post: Error occured while running Import-Module PSPKI

Camelot — Mon, 24 Sep 2012 08:38:47 GMT

Enjoy ADCS automation with Windows PowerShel!

New Post: Error occured while running Import-Module PSPKI

har77 — Mon, 24 Sep 2012 08:07:08 GMT

Hi,

That solved my problem.

Thank you.

New Post: Error occured while running Import-Module PSPKI

Camelot — Fri, 21 Sep 2012 10:58:26 GMT

Hi, it looks like you haven't installed ADCS RSAT tools. If you are using client operating system, install RSAT, if you are using server OS, add required RSAT components in Server Manager.

New Post: Error occured while running Import-Module PSPKI

har77 — Fri, 21 Sep 2012 05:55:27 GMT

Hi,

After installing the PS PKI v2.0.exe I ran the Import-Module PSPKI command. But I keep getting the following error,

PS C:\Windows\system32> import-module PSPKI
Write-ErrorMessage : Exception of type 'Microsoft.PowerShell.Commands.WriteErrorException' was thrown.
At C:\Users\...\Documents\WindowsPowerShell\Modules\PSPKI\PSPKI.psm1:117 char:26
+ catch {Write-ErrorMessage <<<< -Source "CAPIUnavailable"}
+ CategoryInfo : NotImplemented: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : NotImplementedException,Write-ErrorMessage

What shall I do to overcome this issue?

Thank you.

New Post: Source Code

Camelot — Thu, 09 Aug 2012 14:51:46 GMT

Unfotunately .NET Library sources are not yet available.

New Post: Source Code

andrewwillett — Thu, 09 Aug 2012 12:39:37 GMT

Hi,

Is there any source code for the underlying .NET libraries?

Thanks,

Andrew.