Visit the remote machine with an admin account, so that you can perform the modifications.
Check your PowerShell version:
Open the PowerShell application as administrator (right click: 'run as Administrator').
Run the following command:
We should receive a summary, like this:
Major Minor Build Revision
----- ----- ------ --------
5 1 18362 1
If the Major version flag is lower, than 5, then our PowerShell verzion is not suitable to refresh an an account's service password.
(In this webpage you can find latest version of PowerShell: https://github.com/PowerShell/PowerShell/releases)
0. Jelentkezzünk be a távoli gépre Távoli Asztali kapcsolattal (vagy 1-Klikk segítségével)
- Check, if the PowerShellRemoting is enabled or not. Run PowerShell-t as administrator, and run the following command.
The connection is not opened by default, but if yes: this is the feedback of a working session: (State: Opened)
If this is not the case, it will take around 20 secs to display red error messages.
- To establish the connection we should turn PowerShellRemoting ON. The following command makes this able. (notice: P.Shell should run as admin still)
This might will trigger further error messages, when network type is public. The PowerShellRemoting expects a private network as a type. We have 2 solutions for this problem:
a. If we want to ignore this isssue, then we can 'force' the setting:
Enable-PSRemoting -SkipNetworkProfileCheck -Force
Now we should not see further error. If there are still any:
b. Set the network type as private. This is the command for it:
Set-NetConnectionProfile -NetworkCategory Private
(the result can be checked by this instruction: Get-NetConnectionProfile).
Now retry with the previous command: Enable-PSRemoting -SkipNetworkProfileCheck -Force
If we see similar feedbacks, it is recommended to hit 'Y' one-by-one.
Enter the initial command again in P.Shell: New-PSSession
In case of flawless settings (and operation), de connection should be establisted, so session State will be Opened.