Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enable_winrm_access does not seem to work #41

Open
rreilly-edr opened this issue Feb 28, 2019 · 0 comments
Open

enable_winrm_access does not seem to work #41

rreilly-edr opened this issue Feb 28, 2019 · 0 comments

Comments

@rreilly-edr
Copy link

rreilly-edr commented Feb 28, 2019

Describe the bug
Using packer to create an image, apply hardening cookbook and enable_winrm_acesss and reboot
Expected behavior
Winrm is available after reboot

Actual behavior
after reboot winrm is no longer available

edr-widows-2016-base-20190228-074531: Recipe: windows-hardening::enable_winrm_access
edr-widows-2016-base-20190228-074531:   * powershell_script[Remote Management] action run[2019-02-28T15:53:42+00:00] INFO: Processing powershell_script[Remote Management] action run (windows-hardening::enable_winrm_access line 10)
2019/02/28 07:53:41 [INFO] (telemetry) ending chef-client
2019/02/28 07:53:41 [INFO] (telemetry) Starting provisioner windows-restart
==> edr-widows-2016-base-20190228-074531: Restarting Machine
2019/02/28 07:53:41 [INFO] 0 bytes written for 'stdout'
2019/02/28 07:53:41 [INFO] 0 bytes written for 'stderr'
2019/02/28 07:53:41 packer: 2019/02/28 07:53:41 Retryable error: http response error: 401 - invalid content type

After the 10 minute timeout packer exits as winrm does not become available.
Example code


OS / Environment
aws windows 2016 base
Chef Version

14.10.9

Cookbook Version

0.9.1

I also attempt to connect to the host via telnet ip 5985 and I cannot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant