Microsoft ATA is not reachable

[raghucybersec]

• Operating System Version: Windows
• Deploying via (VirtualBox/VMWare/AWS/Azure/ESXi): VMWare
• Vagrant Version (if applicable):

Please verify that you are building from an updated Master branch before filing an issue.

Description of the issue:

Microsoft ATA is not reachable and getting below error while running post script.

[*] Verifying that Microsoft ATA is reachable... Error occured on webrequest: Exception calling "DownloadString" with "1" argument(s): "Unable to connect to the remote server" [!] Microsoft ATA was unreachable and may not have installed correctly.

Remaining packages like fleet, splunk and velociraptor is running sucessfully, expect Microsoft ATA. Kindly help to resolve the issue.

[bamoburry]

I have been having the same problem too and when I try to install it directly on the WEF Server I got another error which seems worse

[ProtoDroidBot]

Investigating the overall issue on my side. To @bamoburry : Assuming Vagrant placed the Microsoft ATA ISO file in the root C:\ directory, it might need to be mounted from an administrator PowerShell prompt from within the WEF machine. I am checking to see if this is actually the case.

@raghucybersec - Checking now, were there any errors during provisioning of the wef VM? I suspect if ATA is not installed it might've had a download issue, but I need to verify this for sure on my end.

Could you try the below command and see if it works? If not then at least it will output a vagrant.log file to the current directory and it might be easier to triage what is going on with the log file.

vagrant reload wef --provision --debug 2>&1 | Tee-Object -FilePath ".\vagrant-wef-reload.log"

[ProtoDroidBot]

Apparently while attempting to triage the above issue with the wef machine, I got stuck on "mounting shared folders" for some reason, I realized that vmware tools was trying to install but somehow got stuck or was waiting.

[bamoburry]

Investigating the overall issue on my side. To @bamoburry : Assuming Vagrant placed the Microsoft ATA ISO file in the root C:\ directory, it might need to be mounted from an administrator PowerShell prompt from within the WEF machine. I am checking to see if this is actually the case.

@raghucybersec - Checking now, were there any errors during provisioning of the wef VM? I suspect if ATA is not installed it might've had a download issue, but I need to verify this for sure on my end.

Could you try the below command and see if it works? If not then at least it will output a vagrant.log file to the current directory and it might be easier to triage what is going on with the log file.

vagrant reload wef --provision --debug 2>&1 | Tee-Object -FilePath ".\vagrant-wef-reload.log"

@ProtoDroidBot Thank you for the tip, but unfortunately when I mount the ISO image as advised I got a different error during installation here is the screenshot.

[gingerhax]

Seems like this is due to a change from Microsoft. The URL in install-microsoft-ata.ps1 to download is "http://download.microsoft.com/download/4/9/1/491394D1-3F28-4261-ABC6-C836A301290E/ATA1.9.iso". That URL has a 404 page.

[clong]

Hey folks, thanks for the report. Microsoft ATA is kind of deprecated and so I'm going to be removing it from the project entirely.