Hello,

I'm trying to Invoke-Command using the 32 bit powershell client. Is there a way to register the microsoft.powershell32 pssession configuration via GPO ? The reason for this is that I need to invoke this command on all servers in our domain 900+ servers so configuring one by one really isn't an option.

FYI, I've already set up the winrm listener via GPO.

Thanks,

Hi,

We could use group policy to set computers startup or logon script, with the script to register the session for every server in your domain:

Using Group Policy to Deploy a Windows PowerShell Logon Script

http://blogs.technet.com/b/heyscriptingguy/archive/2010/08/14/weekend-scripter-using-group-policy-to-deploy-a-windows-powershell-logon-script.aspx

Hope this helps.

Regards,

Yan Li

Thanks Yan,

This is exactly what I did to make sure any new servers were receiving the proper configuration. As for the servers already deployed I did not want to wait to depend on the server rebooting before having the setting applied so I used psexec.exe from sys internals suite. First I used get-adcomputer to create a textfile with a list of all serves using format \\computername then used the code below:

get-content filename | foreach-object {psexec.exe $_ -u [admin account name] -p [admin account password] -h -n 5 -d powershell.exe "enable-psremoting -force"}

I got the idea to use psexec.exe from this original post and just tweaked a few parameters:

http://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/0800c68c-8cfb-4d6f-9c05-0e1a33412941/

• Edited by guilly08 Wednesday, September 26, 2012 1:27 PM

Thanks Yan,

This is exactly what I did to make sure any new servers were receiving the proper configuration. As for the servers already deployed I did not want to wait to depend on the server rebooting before having the setting applied so I used psexec.exe from sys internals suite. First I used get-adcomputer to create a textfile with a list of all serves using format \\computername then used the code below:

get-content filename | foreach-object {psexec.exe $_ -u [admin account name] -p [admin account password] -h -n 5 -d powershell.exe "enable-psremoting -force"}

I got the idea to use psexec.exe from this original post and just tweaked a few parameters:

http://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/0800c68c-8cfb-4d6f-9c05-0e1a33412941/

• Edited by guilly08 Wednesday, September 26, 2012 1:27 PM

Here is full description as configure Powershell remoting by means of GPO http://blog.powershell.no/2010/03/04/enable-and-configure-windows-powershell-remoting-using-group-policy/ 

Thanks,

Unfortunetly this only explains how to enable winRM service. This isn't enough to allow ps-remoting to work. You still need to issue enable-psremoting locally somehow.

 You still need to issue enable-psremoting locally somehow.

NO! Above article give you all needed steps to configure psremoting by GPO.

@guilly08 is right.  

This article describe the Powershell-Remoting not completeley.