GoogleCloudPlatform / GoogleCloudPlatform/compute-image-tools
WinRM not enabled for Windows Pro (Professional) edition or any non-Enterprise edition
- Dominant language
- Go
- Stars
- 220
- Forks
- 168
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 6
Description
https://github.com/GoogleCloudPlatform/compute-image-tools/blob/33c970f077033a73e715b95550673d5700b99442/daisy_workflows/image_build/windows/post_install.ps1#L693C9-L693C116
https://github.com/GoogleCloudPlatform/compute-image-tools/blob/33c970f077033a73e715b95550673d5700b99442/daisy_workflows/image_build/windows/post_install.ps1#L661-L666
For example, on Windows 10 Professional, `$pn` will be `Windows 10 Pro`, so `winrm quickconfig` won't run.
This leads to `Error - Could not start WinRM Service` when the imported image is booted (preceded by a 2m wait) https://github.com/GoogleCloudPlatform/compute-image-windows/blob/6759c61b20e3dc26ad2004e05d10000ccc519c02/sysprep/instance_setup.ps1#L234-L243
Contributor guide
Research direction
Start with daisy_workflows/image_build/windows/post_install.ps1 at lines 661-666 and 693, then compare the WinRM setup with sysprep/instance_setup.ps1 lines 234-243 in compute-image-windows. Verify the edition check covers Windows Pro and other non-Enterprise editions, and confirm that an imported image boots without the WinRM service error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100