Internet Explorer first-launch configuration not completed
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- networking
Research direction
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.
Description
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
- Dominant language
- PowerShell
- Stars
- 114
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/NetworkMonitoring
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Te Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
Azure/NetworkMonitoring#30 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Azure/NetworkMonitoring#17 ·
-
How Network Topolgy can be used to see network topology diagram for more then one resource group? Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/NetworkMonitoring#14 ·
All issues in Azure/NetworkMonitoring
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
home-assistant/supervisor#7248 ·
-
bug cert blocker needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
project-chip/connectedhomeip#74373 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-mgmt#28113 ·
-
kind/bug kind/community-report needs/triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100