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
```

Start by locating the script's Invoke-WebRequest call that produces the reported upload failure and compare it with the failing command shown in the issue. Reproduce the run on a workstation where Internet Explorer first-launch configuration is incomplete, then verify that the client completes its data upload without requiring that configuration.

Written by the indexing model from the issue text.