Watchmaker support for Windows Server 2025
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 42
- Forks
- 31
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 19
Description
While attempting to use Watchmaker userdata with a Windows Server 2025 AMI, received an error output in the watchmaker.log stating 'wmic' is not recognized as an internal or external command.
Salt_call.debug.log entry:
'wmic' is not recognized as an internal or external command, operable program or batch file.
This is a deprecated command and the recommendation is to use PowerShell cmdlets such as Get-CimInstance for the same functionality.
Also, noticed that Windows Server 2025 (and 2022) is not on the supported list at https://watchmaker.readthedocs.io/en/stable/scap.html
Watchmaker and salt_call.debug log files are attached.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached watchmaker.log and salt_call.debug.log to locate the failing WMIC use, then inspect the supported-platform list at the linked scap.html documentation. Done means Watchmaker works with Windows Server 2025 without this error and the supported list reflects the relevant Windows Server versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, python
- Domain
- documentation, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100