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

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How do you secure your Windows domain environment while still enabling the Powershell 2.0 remoting capabilities (WinRM invoke-item) ?

Because at the moment my company datacenter would like to implement tight security policy according to this guideline: ?

Normally I use the Powershell for managing and monitoring the Exchange Server, Active Directory and VMware vSphere environment. With Windows Server 2008, 2003 and XP as the client.

Any kind of help and suggestion would be greatly appreciated.


share|improve this question
up vote 2 down vote accepted

We are in a similar situation. We also haven't enabled PS Remoting due to security precautions, but here's what I do know:

  • Lock down the trusted hosts that are allowed to connect to a remote computer:

Set-Item WSMan:\localhost\Client\TrustedHosts ControllerComputerDNSnamesOrIPs

I'm no security expert, but I do appreciate the security risks involved. I would like to hear from others who have identified potential security issues, and what can be done to mitigate them.

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.