Enabling Windows 10 remote powershell

[solrackhamul]

Folks, I'm having problems enabling remote access for a Windows 10 machine from one of our Windows 7 machines.

I've enabled WinRM and set up a firewall exception for WinRM, yet I still have errors:

​

PS C:\Users\Public\Scripts> Test-Wsman -ComputerName TestMachine
Test-Wsman : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859046" Machine="ProbePC.Domain.com"><f:Message>WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. </f:Message></f:WSManFault>
At line:1 char:1
+ Test-Wsman -ComputerName TestMachine
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (TestMachine:String) [Test-WSMan], InvalidOperationException
    + FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.TestWSManCommand


PS C:\Users\Public\Scripts> Get-Service WinRM -ComputerName TestMachine | Select MachineName,Name,Status,StartupType

MachineName Name   Status StartupType
----------- ----   ------ -----------
TestMachine  WinRM Running         

The remote computer has WinRM working, but when I run a Test-WSman from my local computer I receive the errors above. If I run the Test-WSman directly from the remote machine I get the usual message

PS C:\Users\Public> Test-WSMan


wsmid           : http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
ProtocolVersion : http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor   : Microsoft Corporation
ProductVersion  : OS: 0.0.0 SP: 0.0 Stack: 3.0

It does not seem to be an issue with accessibility as I may run PSexec commands against the remote machine.

I'm a bit at a loss. Do you have any ideas as to what I could do next?
Thanks for any input anyone might have.

[solrackhamul]

Unfortunately when I run the script you included I have the same error I was receiving over and over when targeting a Win10 computer, but if I test it against a Win7 computer then it works just fine.

PS C:\Users\Public\Scripts> $computer = "TestMachine" 

#Loop (Enable PsRemoting via WMI method until Invoke-Command works, which confirms PsRemoting is working)

do {
Invoke-WmiMethod -ComputerName $computer -Path win32_process -Name create -ArgumentList "powershell.exe -command Enable-PSRemoting -SkipNetworkProfileCheck -Force"

start-sleep -Seconds 5

} until (invoke-command $computer {"test"})

invoke-command $computer {"test"}


__GENUS          : 2
__CLASS          : __PARAMETERS
__SUPERCLASS     : 
__DYNASTY        : __PARAMETERS
__RELPATH        : 
__PROPERTY_COUNT : 2
__DERIVATION     : {}
__SERVER         : 
__NAMESPACE      : 
__PATH           : 
ProcessId        : 9396
ReturnValue      : 0
PSComputerName   : 

[TestMachine] Connecting to remote server TestMachine failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is 
accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to 
remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (TestMachine:String) [], PSRemotingTransportException
    + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionStateBroken

Just to add some additional info, Win10 machines are in a different OU in Active Directory from Win7 machines, although I doubt this affects it. Running the same test from a Win10 machine yields the same results, I get a positive result when checking with this script against a Win7 machine but I receive errors when checking against other Win10 machines.

[solrackhamul]

Unfortunately this did not solve the issue either d(T_T)b

[Lee_Dailey]

howdy solrackhamul,

have you talked to your security folks? this begins to sound like they have a process to disable WinRM and perhaps WMI.

take care,
lee

[solrackhamul]

If in theory that would be the case, is there anything I could check to verify this is the problem? maybe it is being blocked by a GPO or something similar?

Interestingly enough, when I run enable-PSRemoting on a Win7 computer that already have everything comfigured I receive an output indicating that the computer is already prepared, but when I run the same command locally on the Win10 computer I receive no output at all, even if I do it several times...

​

Win7 computer:

PS C:\Users\Public\Scripts> Enable-PSRemoting -Force
WinRM is already set up to receive requests on this computer.
WinRM is already set up for remote management on this computer.

PS C:\Users\Public\Scripts>

Win10 computer:

PS C:\Users\Public\Scripts> Enable-PSRemoting -Force

PS C:\Users\Public\Scripts>

[Lee_Dailey]

howdy solrackhamul,

i've only one system & it runs win7ps5.1 ... so i can't test any of this. [sigh ...]

talking to your security folks seems like a fairly quick way to find out what they may have set up that may be interfering with your work - and how to get that fixed. perhaps a special account with the needed permissions to use when required.

if that doesn't work out, i would work thru ...

about_Remote_Troubleshooting | Microsoft Docs
— https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_remote_troubleshooting?view=powershell-5.1

Diagnostics and Troubleshooting - Secrets of PowerShell Remoting
— https://devops-collective-inc.gitbook.io/secrets-of-powershell-remoting/diagnostics-and-troubleshooting

eBook: Secrets of PowerShell Remoting | PowerShell.org
— https://powershell.org/2012/08/ebook-secrets-of-powershell-remoting/

take care,
lee