This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 93%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJF%3C/text%3E%3C/svg%3E)
I use PoSH-SSH for a lot of automations. The problem is that the module is unavailable when scripts are run unless I am logged in and have a PowerShell session open as that user. Here is the behavior:
I am probably just missing something obvious, but any help would be greatly appreciated. Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
What is the version of PowerShell? Does this issue occur for other users such as the administrator? Can you import the module using the full path?
VersionTable output is below. User is a local admin account, but not the Administrator account. I have tried using an explicit path, but that didn't seem to help. I saw something that said to place it in $env:ProgramFiles\WindowsPowerShell\Modules so I have yet to try that. Current locations are shown in the original post. Thanks!
Name Value
PSVersion 5.1.14393.6343
PSEdition Desktop
PSCompatibleVersions 1.0, 2.0, 3.0, 4.0
BuildVersion 10.0.14393.6343
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
I tried using the import module command below, and import-module seems to work without an error, but I still get the error following:
import-module -Name "C:\Program Files\WindowsPowerShell\Modules\Posh-SSH\2.3.0\Posh-SSH.psm1"
New-SSHSession : The term 'New-SSHSession' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
You don't say how the script is launched so I'm assuming(!) that it's run as a scheduled task. If that's the case the creation of the session is asking you to accept the certificate. A scheduled task has no UI so the script stalls.
Try adding -AcceptKey and -Force as switches when you create the new session.
The error is specifically that it cannot find/load the module. It is never getting to the connection phase.
. . . also, if the script is unavailable, check the contents of the ENV:PSModulePath variable when you run the script as a scheduled task. You may need to install the module using the -Scope AllUsers parameter.
Import-Module : The specified module 'Posh-SSH' was not loaded because no valid module file was found in any module directory.
The $Env:PSModulePath does show the correct locations. I mentioned it loads automatically when signed into an interactive session, so I don't think that the scope is the problem but I will check.
Did you read my earlier comment about the environment variable and that you may need to install the module using an appropriate scope?
Yes, I am checking on this. This could be a problem as I may have had to perform an off line installation. I did verify the module is present in the $env:programFiles\windowsPowerShellModules directory as there was some indication that it is required for all users to have access.
