clong / DetectionLab

Automate the creation of a lab environment complete with security tooling and logging best practices
MIT License
4.64k stars 987 forks source link

ISO Download issue #165

Closed dnice77 closed 6 years ago

dnice77 commented 6 years ago

Description of the issue:

vmware-iso: Error downloading: checksums didn't match expected: 70721288bbcdfe3239d8f8c0fae55f1f ==> vmware-iso: ISO download failed. Build 'vmware-iso' errored: ISO download failed.

==> Some builds didn't complete successfully and had errors: --> vmware-iso: ISO download failed.

==> Builds finished but no artifacts were created. packer_build_box : Something went wrong while attempting to build the windows_2016 box. At C:\tools\DetectionLab-master\build.ps1:450 char:3

dnice77 commented 6 years ago

Additionally when using -VagrantOnly

Attempting to reload and reprovision the host... Attempting to bring up the win10 host using Vagrant vagrant.exe : The provider 'vmware_desktop' could not be found, but was requested to At C:\tools\DetectionLab-master\build.ps1:336 char:3

back the machine 'win10'. Please use a provider that exists. Vagrant knows about the following providers: docker, hyperv, virtualbox WARNING: Something went wrong while attempting to build the win10 box. Attempting to reload and reprovision the host... WARNING: Caldera failed post-build tests and may not be functioning correctly. WARNING: Splunk failed post-build tests and may not be functioning correctly. WARNING: Fleet failed post-build tests and may not be functioning correctly. WARNING: MS ATA failed post-build tests and may not be functioning correctly.

clong commented 6 years ago

Hi @dnice77 - you seem to have an old version of the code which has outdated hash values for the ISOs. Updating the git repo to match the contents of master should get you back on track.

As for the vmware_desktop message, do you have the Vagrant VMware plugin installed? It's required for this project: https://www.vagrantup.com/vmware/index.html#buy-now

clong commented 6 years ago

I'm going to close this issue out as I'm confident updating your repo should fix your issue. Feel free to re-open if that ends up not being the case!