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

Support Windows VMs #32

Open
Korving-F opened this issue Mar 28, 2022 · 1 comment
Open

Support Windows VMs #32

Korving-F opened this issue Mar 28, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@Korving-F
Copy link
Owner

The current jinja2 templates, Vagrant triggers and ansible/shell provisioners assume systems are Debian-based Linux systems. This should ideally be expanded so lab environments can be spun up using things like Windows workstations and/or

This would also allow for new artifacts to be collected like EVTX and ETW trace files.

@Korving-F Korving-F added the enhancement New feature or request label Mar 28, 2022
@Korving-F Korving-F self-assigned this Apr 3, 2022
@Korving-F
Copy link
Owner Author

This lack-of-support might be just limited to using Ansible (and therefore Filebeat based data export), TCPdump-based network captures and asciinema. While untested this might get closed after #31 and network capture option is added to the Vagrant templates.

For Windows guest machines that are configured to use WinRM, the shell provisioner executes PowerShell and Batch scripts over WinRM. https://www.vagrantup.com/docs/provisioning/shell

run_remote (hash) - A collection of settings to run a inline or remote script with on the guest. These settings correspond to the shell provisioner. https://www.vagrantup.com/docs/triggers/configuration

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

No branches or pull requests

1 participant