Register-PSSessionConfiguration - 'Cannot find drive'

I am attempting to register a PSSession configuration after creating a new PSSession configuration file. The params I am using are -path, -name, -securitydescriptorsddl, -runascredential. (I am following along with Don’s CBT Nuggets demo).

However I’m running into this error executing the cmdlet:

dir : Cannot find drive. A drive with the name ‘WSMan’ does not exist.
At line:98 char:3

  • dir ‘WSMan:\localhost\Plugin’ -Force:$force | ? { $_.name -like “$filter” } | …
  • + CategoryInfo          : ObjectNotFound: (WSMan:String) [Get-ChildItem], DriveNotFoundException
    + FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand
    
    

New-Item : A parameter cannot be found that matches parameter name ‘file’.
At line:72 char:48

  •     new-item -path WSMan:\localhost\Plugin -file "$filepath" -name "$pluginN ...
    
  •                                            ~~~~~
    
    • CategoryInfo : InvalidArgument: (:slight_smile: [New-Item], ParameterBindingException
    • FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.NewItemCommand

Any suggestions on how to troubleshoot are welcome. Thanks!

If Remoting has not been enabled on the local computer, than the Wsman: drive won’t exist.

-facepalm-

I’m sure I’m just late to the party here, but the custom endpoints feature is awesome! This is going to really influence how our team works. Many thanks to the Powerhell team and this community.

Hi Travis,

It’s a biggie for my team at work as well. Will finally be able to offload some of the simple tasks that need admin access to our first line folks.

Worthwhile having a check of

https://channel9.msdn.com/Events/TechEd/NorthAmerica/2014/DCIM-B362#fbid=

If you’re interested in the next stage of how constrained endpoints can be implemented.