A Go command-line tool to execute remote commands on Windows machines via WinRM/WinRS protocol.
winrm-cli is a command-line tool that allows users to remotely execute commands on Windows machines using the WinRM/WinRS protocol. It solves the problem of managing Windows servers without direct console access, particularly useful for cloud environments where traditional RDP might be impractical for automation. The tool provides a simple interface to run administrative commands from any system that can connect to the Windows host.
System administrators and DevOps engineers who need to automate tasks on Windows servers, particularly those managing EC2 Windows instances or other cloud-based Windows infrastructure.
Developers choose winrm-cli because it's a lightweight, focused alternative to heavier Windows management tools, with specific optimization for cloud scenarios and straightforward command-line usage. Its Docker availability makes it easy to integrate into CI/CD pipelines and automation workflows.
Command-line tool to remotely execute commands on Windows machines through WinRM
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Specifically optimized for Amazon EC2 Windows instances, making it a go-to tool for cloud infrastructure automation without SSH.
Available as a Docker container, enabling easy deployment in CI/CD pipelines and isolated environments without local Go installations.
Allows remote Windows command execution from Linux, macOS, or any system with Docker, bridging OS management gaps for DevOps teams.
Provides a straightforward CLI for executing any Windows command or script, prioritizing simplicity over feature bloat.
Does not support domain users or Kerberos, relying only on basic authentication for local accounts, which restricts use in corporate Active Directory setups.
Requires enabling AllowUnencrypted='true' on remote machines for basic auth, posing a security risk if not properly isolated or secured in networks.
Each target Windows machine needs manual PowerShell configuration to enable WinRM and adjust settings, adding complexity and potential for errors.
On some Windows 2008R2 systems, memory limits may not work without a hotfix, as noted in the README, reducing reliability for memory-intensive commands.