Get-PSSessionConfiguration Microsoft.PowerShell
Or:Set-PSSessionConfiguration Microsoft.PowerShell -ShowSecurityDescriptorUI
Whether or not that's to blame depends on exactly what kind of error you're getting. People never share error messages, it's very frustrating :)
Test-WSMan -ComputerName Server
You might also just go for "telnet" and see if you can hit the port.(New-Object System.Net.Sockets.TcpClient).Connect('Server', 5985)
Nothing means it worked, and error... well you know.Get-ChildItem WSMan:\localhost\Listener | ForEach-Object {
$listener = $_ | Select-Object Name
Get-ChildItem $_.PSPath | ForEach-Object {
$listener | Add-Member $_.Name $_.Value
}
$listener
}
Get-CimInstance preferentially uses WS-Management connections (remoting), therefore it derives rights from that. You can force Get-CimInstance to use DCOM (as Get-WmiObject does), which gives you one fewer service to consider.
Open in new window