Tell me more ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am trying to enable Powershell remoting on a Windows 2008 R2 Server, running in workgroup mode.

I ran the command Enable-PSRemoting in the PowerShell Console.

PS C:\Windows\system32> Enable-PSRemoting

WinRM Quick Configuration Running command "Set-WSManQuickConfig" to enable this machine for remote management through WinRM service  This includes:
    1. Starting or restarting (if already started) the WinRM service
    2. Setting the WinRM service type to auto start
    3. Creating a listener to accept requests on any IP address
    4. Enabling firewall exception for WS-Management traffic (for http only).

Do you want to continue? [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): y WinRM already is set up to receive requests on this machine. Set-WSManQuickConfig : Access is denied. At line:50 char:33
+             Set-WSManQuickConfig <<<<  -force
    + CategoryInfo          : InvalidOperation: (:) [Set-WSManQuickConfig], InvalidOperationException
    + FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.SetWSManQuickConfigCommand

I am logged in as a member of the Administrators Group, and running the Console As Administrator.

share|improve this question
can you try run "winrm quickconfig" from command line (not PowerShell). I believe it's doing exactly the same as Enable-PSRemoting in PowerShell – user978511 Nov 28 '11 at 8:08
It gives the same result: Access is denied – Peter Lundsby Nov 28 '11 at 22:54
1  
Why was this closed as off-topic, running Powershell scripts on remote servers seems very much within the scope of Stackoverflow! – Peter Lundsby Dec 1 '11 at 15:49
@Peter Lundsby - Probably because if you have the right command, but it's not working on the server, that's more a server issue than a programming one. – Driftpeasant Dec 5 '11 at 21:39

migrated from stackoverflow.com Dec 5 '11 at 21:22

1 Answer

For any issue with Power Shell Remoting, there are two important resources.

The first is help about_Remote_Troubleshooting, which is an extensive reference.

The second is an internet search for the error you're getting. I found a PowerShell team blog post that had this checklist:

  1. My machine is connected to domain.
  2. I am logged in as administrator
  3. PowerShell is launched elevated.
  4. My password is not blank

Does one of those fix your issue?

share|improve this answer
windows 7 home, blank password was my issue! – Chris Stavropoulos Dec 15 '12 at 20:35

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.