Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Enabling winrm using powershell

DZone's Guide to

Enabling winrm using powershell

· Performance Zone ·
Free Resource

xMatters delivers integration-driven collaboration that relays data between systems, while engaging the right people to proactively resolve issues. Read the Monitoring in a Connected Enterprise whitepaper and learn about 3 tools for resolving incidents quickly.

So, you’re doing stuff with these new “virtual” machines eh? Well if you’re using windows, there’s a damn good chance you’ll need to enable and configure winrm, otherwise you won’t be able to log in to your swanky new “virtual machine”! Even Chef needs this service running on the target in order to work with windows. Anyway, here’s what to do: open a powershell prompt and type the following:

    winrm quickconfig -q

    winrm set winrm/config/winrs ‘@{MaxMemoryPerShellMB=”512″}’

    winrm set winrm/config ‘@{MaxTimeoutms=”1800000″}’

    winrm set winrm/config/service ‘@{AllowUnencrypted=”true”}’

    winrm set winrm/config/service/auth ‘@{Basic=”true”}’

    Start-Service WinRM

    set-service WinRM -StartupType Automatic

Alternatively you could create a ps1 script containing the stuff above, open powershell, do the thingy that allows you to run unsigned scripts, namely:

Set-ExecutionPolicy Unrestricted

Then run the ps1 script.

There, I’ve blogged it, now I’ll never have to google this again!

Discovering, responding to, and resolving incidents is a complex endeavor. Read this narrative to learn how you can do it quickly and effectively by connecting AppDynamics, Moogsoft and xMatters to create a monitoring toolchain.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}