Internet Explorer first-launch configuration not completed

When running the client from a workstation that has not had it's Internet Explorer first-launch configuration completed, the script fails.

```
Starting Avilability test to 10.0.1.4...

******

Statistics for 10.0.1.4
Calls: Sent = 6, Received = 0 (0.00%), Lost = 6
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Median = 0ms

WARNING: Data upload to remote server failed.
WARNING: Please check to ensure the remote server has all the files required to run this tool.
WARNING: Also ensure the XML files in the 'c:\inetpub\wwwroot' have 'Full Control' file access for the local IIS_IUSRS
account
```

```
PS C:\Windows\system32> Invoke-WebRequest -Uri http://10.0.1.4/WebTest.aspx -TimeoutSec 2
Invoke-WebRequest : The response content cannot be parsed because the Internet Explorer engine is not available, or Internet Explorer's first-launch configuration is not complete. Specify the UseBasicParsing parameter and
try again.
At line:1 char:1
+ Invoke-WebRequest -Uri http://10.0.1.4/WebTest.aspx -TimeoutSec 2
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotImplemented: (:) [Invoke-WebRequest], NotSupportedException
+ FullyQualifiedErrorId : WebCmdletIEDomNotSupportedException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
```

Comienza localizando la llamada a Invoke-WebRequest del script que produce el error de carga informado y compárala con el comando que falla mostrado en el issue. Reproduce la ejecución en una workstation en la que la configuración del primer inicio de Internet Explorer esté incompleta y, después, verifica que el cliente complete la carga de datos sin requerir esa configuración.

Escrito por el modelo de indexación a partir del texto del issue.