warn users to lock down winrm after provisioning

This commit is contained in:
Megan Marsh 2019-04-19 17:03:20 -07:00
parent a360516a64
commit 11037968a8
6 changed files with 18 additions and 0 deletions

View File

@ -166,6 +166,9 @@ setting a valid `account_file` and `project_id`:
}
```
-> **Warning:** Please note that if you're setting up WinRM for provisioning, you'll probably want to turn it off or restrict its permissions as part of a shutdown script at the end of Packer's provisioning process. For more details on the why/how, check out this useful blog post and the associated code:
https://cloudywindows.io/post/winrm-for-provisioning---close-the-door-on-the-way-out-eh/
This build can take up to 15 min.
### Nested Hypervisor Example

View File

@ -876,6 +876,9 @@ Finish proxy after sysprep -->
</unattend>
```
-> **Warning:** Please note that if you're setting up WinRM for provisioning, you'll probably want to turn it off or restrict its permissions as part of a shutdown script at the end of Packer's provisioning process. For more details on the why/how, check out this useful blog post and the associated code:
https://cloudywindows.io/post/winrm-for-provisioning---close-the-door-on-the-way-out-eh/
## Example For Ubuntu Vivid Generation 2
If you are running Windows under virtualization, you may need to create a

View File

@ -893,6 +893,9 @@ Finish proxy after sysprep -->
</unattend>
```
-> **Warning:** Please note that if you're setting up WinRM for provisioning, you'll probably want to turn it off or restrict its permissions as part of a shutdown script at the end of Packer's provisioning process. For more details on the why/how, check out this useful blog post and the associated code:
https://cloudywindows.io/post/winrm-for-provisioning---close-the-door-on-the-way-out-eh/
## Example For Ubuntu Vivid Generation 2
If you are running Windows under virtualization, you may need to create a

View File

@ -90,6 +90,9 @@ Here is a basic example for windows server.
]
}
-> **Warning:** Please note that if you're setting up WinRM for provisioning, you'll probably want to turn it off or restrict its permissions as part of a shutdown script at the end of Packer's provisioning process. For more details on the why/how, check out this useful blog post and the associated code:
https://cloudywindows.io/post/winrm-for-provisioning---close-the-door-on-the-way-out-eh/
Here is a basic example for linux server.
{

View File

@ -322,6 +322,9 @@ Platform:
}
```
-> **Warning:** Please note that if you're setting up WinRM for provisioning, you'll probably want to turn it off or restrict its permissions as part of a shutdown script at the end of Packer's provisioning process. For more details on the why/how, check out this useful blog post and the associated code:
https://cloudywindows.io/post/winrm-for-provisioning---close-the-door-on-the-way-out-eh/
### Post i/o timeout errors
If you see

View File

@ -404,6 +404,9 @@ Start-Service -Name WinRM
</powershell>
```
-> **Warning:** Please note that if you're setting up WinRM for provisioning, you'll probably want to turn it off or restrict its permissions as part of a shutdown script at the end of Packer's provisioning process. For more details on the why/how, check out this useful blog post and the associated code:
https://cloudywindows.io/post/winrm-for-provisioning---close-the-door-on-the-way-out-eh/
Save the above code in a file named `bootstrap_win.txt`.
-> **A quick aside/warning:**<br />