I've been looking for a quick way to run "winrm quickconfig" via group policy.  I figure it has to be group policy since elevated privileges are required but I'm open to suggestion.  I don't know much about winrm configuration but I do know if works in my environment with the quickconfig switch.

If I remember correctly, winrm is just a VBScript script actually. I think you should go asking this in a GPO forum/group.

What is your ultimate goal here? Just to enable WinRM 1.0?

My ultimate goal is to use Powershell Remoting across our company.

The more "official" way to do this is with "Enable-PSRemoting -force" that comes with v2.

I'd have to research, but I'm assuming "winrm quickconfig" does the exact same thing. Also, you may want to be aware that the WinRM 2.0 RTM won't use ports 80 and 443 by default.

I totally agree that GPO is the way this ought to be done. It needs researching, afraid I don't know the answer either.

http://www.microsoft.com/downloads/details.aspx?FamilyID=2917a564-dbbc-4da7-82c8-fe08b3ef4e6d&DisplayLang=en

I wonder if Server 2008 R2 has any GPOs relating to PowerShell/WinRM v2...

(let me try again as I don't know what happened to my original post)

At least on Windows Server 2008R2 there is WinRM GPO setting under Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Remote Management.

Minimum OS is Vista and there are settings for the client and service. Not sure of the effect of combining the policy with Enable-PSRemoting.

http://blogs.msdn.com/powershell/archive/2009/04/30/enable-psremoting.aspx?CommentPosted=true#commentmessage

They make mention that there is a way to enable remoting in group policy. I've requested more information and I'll pass it along in this thread if I get a reply.

Jeff - Using the templates you linked I can see a number of settings for WinRM (no version specified) on my 2003 network.  I'll see if I can't replicate what Enable-PSRemoting -force does from there.

This feels like progress. :)

http://msdn.microsoft.com/en-us/library/aa384372(VS.85).aspx "Installation and Configuration for Windows Remote Management"
This includes group policy configuration.

http://technet.microsoft.com/en-us/library/dd819498.aspx

This shows exactly what Enable-PSRemoting does and it lists a great many things that are not included in the previous article.

I've made a GPO that starts the service, makes the firewall exceptions, and creats a listener. I can't do much more this weekend though. Hopefully I'll know more on Monday.

Edit: Useless information.  Solution below.

Well it appears that I have this working and as usual I made it a lot harder than it needed to be and then I found the easy solution. :)

Make a new GPO here (I'm using Win 7 Enterprise with the new RSAT).

Computer Configuration\Windows Settings\Scripts\Startup

There is the usual Scripts tab and a new PowerShell Scripts tab.  I simply made a script which contains "Enable-PSRemoting -force" and told it to run PowerShell scripts first.

I built a new VM to push this on and it complained on the first login but after a reboot there were no more errors and remoting worked.

-Ty

Here's a screenshot.

That is awesome! Thanks for the update, I've already got this article marked for discussion on the podcast.

Also, check out this blog-post:

"Enable and configure Windows PowerShell Remoting using Group Policy"

http://blog.crayon.no/blogs/janegil/archive/2010/03/04/enable_2D00_and_2D00_configure_2D00_windows_2D00_powershell_2D00_remoting_2D00_using_2D00_group_2D00_policy.aspx

Great blog post. Lots of details. Thanks for a shout-out. We plan to cover more "remoting in an enterprise" topics in a next edition.