-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Consistent way to enable PSRemoting #4528
Copy link
Copy link
Closed
Labels
Area-SideBySiderelated to ability to run PS7 side-by-side with WinPS or different versions of PS7related to ability to run PS7 side-by-side with WinPS or different versions of PS7Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugOS-WindowsResolution-FixedThe issue is fixed.The issue is fixed.WG-RemotingPSRP issues with any transport layerPSRP issues with any transport layer
Milestone
Metadata
Metadata
Assignees
Labels
Area-SideBySiderelated to ability to run PS7 side-by-side with WinPS or different versions of PS7related to ability to run PS7 side-by-side with WinPS or different versions of PS7Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugOS-WindowsResolution-FixedThe issue is fixed.The issue is fixed.WG-RemotingPSRP issues with any transport layerPSRP issues with any transport layer
We have internally been referring to this as the "Nano Server Scenario" aka headless, remote-only remoting activation. The idea is that we need a way to register a non-running instance of PowerShell Core with WinRM. In Nano Server, you can create a remote session (
New-PSSession)to the instance of Windows PowerShell running on the system. Once in that session (Enter-PSSession), you can unzip PowerShell Core on Nano Server to make it available for use. The only way to register the new instance of PowerShell Core as a WinRM endpoint is to runInstall-PowerShellRemoting.ps1from within the current Windows PowerShell remote session.Enable-PSRemoting works to register the running instance of PowerShell Core with WinRM, but the script
Install-PowerShellRemoting.ps1is the only solution to this problem. We should consider building that functionality into a new cmdlet or an existing cmdlet to make it more permanent.Environment data
Windows
Beta.5