WinRM Configuration on Windows 2008R2

We have recently been given the green light to use Powershell.
Most of our servers are running 2008 r2 and we want to use powershell cmdlets when possible vs wmi calls from powershell.
But we need to configure WinRM on the target servers which many are production.
Is there an impact, issue, pitfall to setting this up.
I will have to make a very detailed request for this and need to have all my ducks in a row to field any questions or push back that may come.

Any advise is greatly welcomed
Thanking everyone in advance
Jose TorresCertified Database AdministratorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
you might as well get the latest windows management framework.  Will require a reboot.  on each machine run from an elevated command prompt 'winrm -quickconfig'
Jose TorresCertified Database AdministratorAuthor Commented:
We are starting to rollout .net 4.5 on our production servers so seems as a well worth add on.
There are a few servers that we cant because we have an old version of biztalk.

But regardless, i still need to prepare a well defined argument to get upper mgmt to approve this change and the server reboots are a hard sell specially in health care.
You can make the argument that any avenue for access is a vulnerability, but beyond that I see no issue with allowing this.  If you're concerned about securing the traffic between machines you can set it up to use HTTPS (TCP 5986).  Do you already allow remote WMI queries or PsExec?

There's potential for great gains when using PowerShell Remoting, particularly with fan-out processes.  It could reduce the run-time of a script drastically when querying many remote machines.  Particularly for remote registry work, using PS Remoting is a great approach as your code doesn't have to differ from how you would access it locally.

I'll share some links which I think are good reading.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jose TorresCertified Database AdministratorAuthor Commented:
Thank you for your comments
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.