1 回答
- 最新
- 投票最多
- 评论最多
1
Hello!
Thank you for taking time to ask a question on re:Post John.
One of the main reasons behind this is because Microsoft has not sunset Internet Explorer for Windows Server until support ends in 2029. This question in re:Post also has a great explanation.
You can also try an alternative approach. You may install Edge (or another browser) with a similar script in the user data at an EC2 launch. This PowerShell snippet is just an example that may be able to get you started.
Set-Location “C:\Windows\system32” #Change TimeZone C:\Windows\System32\tzutil /s “AUS Eastern Standard Time” #Install Chrome $Path = $env:TEMP; $Installer = “chrome_installer.exe”; Invoke-WebRequest “http://dl.google.com/chrome/install/375.126/chrome_installer.exe” -OutFile $Path\$Installer; Start-Process -FilePath $Path\$Installer -ArgumentList “/silent /install” -Verb RunAs -Wait; Remove-Item $Path\$Installer #Set Chrome as default browser $chromePath = "${Env:ProgramFiles(x86)}\Google\Chrome\Application\" $chromeApp = “chrome.exe” $chromeCommandArgs = “--make-default-browser” & “$chromePath$chromeApp” $chromeCommandArgs
Microsoft recently came out with an article that may also help you. There are steps there that show you how to add Edge back into a container image.
Hope all of the different options help!
已回答 1 年前
相关内容
- AWS 官方已更新 2 年前