Windows 10: Powershell Enter-PSSession -useSSL

Hi,


Would you please confirm that the following should work when trying to connect a remote session to a host with self-signed certificate:

WinRM HTTPS listener configured with ComputerFQDN and self-signed certificate, HTTPS/ComputerFQDN:5986 SPN set


Enter-PSSession ComputerFQDN -UseSSL -SessionOption New-PSSessionOption -IncludePortInSPN -SkipCACheck


Many thanks.
Klaus

:)

 

Enable and use Powershell remoting

I have a Windows 10 Professional (Anniversary Update) machine PC1 with user user1 (Administrator) and a Windows 7 Professional machine PC2 with user user2 (Administrator). They both belong to a workgroup (not a domain) called MYWORKGROUP and they are in the same LAN, with private addresses (192.168.1.x).

Running Powershell as Administrator from user1 in PC1, I followed this guide as suggested in the comments and I also included PC1 in the list of trusted hosts of PC2 with

as suggested in the answer.

Then I logged in PC2 as user2 and ran from Powershell console

I gave my username as PC1\User2 and my PC1 password. Then I ran

The error it gives is now:

In such a scenario, what else should be done in order to make the Powershell console in PC2 able to run remote commands in PC1?

Note that user user2 exists in both PC1 and PC2 with (now) the same password; anyway, in PC1 it is not Administrator. Maybe should it?

 

Powershell ISE 10 stopped working during refresh - Same commands in Powershell work fine

1. Clean install Windows 10

2. Running script in Powershell ISE 10.0.10240.16384 that worked fine in Windows 8.1

3. Random error (stopped working) apparently due to Refresh in the command Add-on "Failed to refresh ShowCommandRefreshError"

4. Same commands work fine in Powershell 10.0.10240.16384 (i.e. not the ISE)

5. Set of commands for info because the commands as such seem not to be the cause

6. I also used the command
New-PSSession -ComputerName compname in Windows 8.1 but this gives a refresh error under Windows 10

Set-ItemWSMan:\localhost\Client\TrustedHosts–Value compname-Force

Enter-PSSession-ComputerNamecompname

Restart-Service-NameMSSQLSERVER-Force-WarningActionSilentlyContinue

Restart-Service-NameW3SVC-Force-WarningActionSilentlyContinue

Restart-Service-NameReportServer-Force-WarningActionSilentlyContinue

Restart-WebAppPool-NameByteinvest

Restart-WebAppPool-NameNavorming

Restart-WebAppPool-NameNavormingTienen

Exit-PSSession

 

PowerShell instead of Commandline in Creators Update

Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

Edit: Not that it matters...I use both regularly. *Toast :toast: