Closed ghost closed 6 years ago
This issue looks to be related to #33 - DNS resolution is failing, which probably means:
Can you confirm if any of these are the case?
It should have been up, I started by bringing that one online first. I just tried again by running "vagrant reload win10 --provision" and got the same error
Can you start the build from scratch and see if this is reproducible? This will wipeout your current VMs and start the rebuild process all over again.
From inside the DetectionLab/Vagrant
folder:
vagrant destroy -f
vagrant up
Hey @iwebsguy - just wanted to follow up here and see if you were ever able to get this working or if you were still having this specific issue.
Sorry for reopening but just wanted to say that I gave up on getting it working. However I did end up using some of what you put together to implement WEF, PowerShell logging, and some the auditing GPOs in our production environment so thanks for that.
Sorry for another one, I kicked off just the win10 machine and got a few errors. Looks like atom stuff and splunk.
Another error