Putting in Chrome/Firefox on a New Home windows Server, the Simple Manner – CloudSavvy IT

Posted on


Windows Server logo

Home windows Server comes with default “Enhanced Safety Configuration” protections for Web Explorer that block web sites that aren’t trusted. The issue? This blocks you from putting in a correct browser like Chrome and getting on with the remainder of your job.

Disabling IE Protections

The best way to correctly disable IE Enhanced Safety Configuration is to open up the Server Supervisor app, after which click on “Configure this native server.”

Click "Configure this local server" in the Server Manager app

Subsequent, below “Properties,” discover IE Enhanced Safety Configuration and switch it off.

Under "Properties," find IE Enhanced Security Configuration and turn it off

From there, you may open up IE, obtain the Chrome/Firefox installer, and get on along with your day.

If that doesn’t work, you may strive manually enabling file downloads below Web Choices > Safety > Customized Degree > Downloads.

The Simple Manner (with PowerShell)

After all, there’s a faster approach to do that utilizing a PowerShell script.

The next script will obtain the Chrome installer and run it, and Chrome shall be auto-installed. You possibly can then launch it from the desktop icon or the beginning menu.

$Path = $env:TEMP; $Installer = "chrome_installer.exe"; Invoke-WebRequest "http://dl.google.com/chrome/chrome_installer.exe" -OutFile $Path$Installer; Begin-Course of -FilePath $Path$Installer -Args "/silent /set up" -Verb RunAs -Wait; Take away-Merchandise $Path$Installer

Should you’re utilizing Home windows Server 2012, you should use this script as an alternative:

$LocalTempDir = $env:TEMP; $ChromeInstaller = "ChromeInstaller.exe"; (new-object System.Web.WebClient).DownloadFile('http://dl.google.com/chrome/set up/375.126/chrome_installer.exe', "$LocalTempDir$ChromeInstaller"); & "$LocalTempDir$ChromeInstaller" /silent /set up; $Process2Monitor =  "ChromeInstaller"; Do { $ProcessesFound = Get-Course of | ?{$Process2Monitor -contains $_.Identify} | Choose-Object -ExpandProperty Identify; If ($ProcessesFound)  Write-Host; Begin-Sleep -Seconds 2  else { rm "$LocalTempDir$ChromeInstaller" -ErrorAction SilentlyContinue -Verbose } } Till (!$ProcessesFound)

Auto-Putting in on AWS

Should you’re on AWS, you then’re in luck, as a result of you may robotically run instructions on server creation utilizing EC2 Consumer Knowledge.

If you create the server, you may add a textual content file or simply paste within the command. It’s also possible to automate this course of if you happen to’re launching from the CLI.

When you create the server, you can upload a text file or just paste in the command

Then, all it is advisable to do is paste the Powershell script inside a <powershell> block, like so:

<powershell>
$Path = $env:TEMP; $Installer = "chrome_installer.exe"; Invoke-WebRequest "http://dl.google.com/chrome/chrome_installer.exe" -OutFile $Path$Installer; Begin-Course of -FilePath $Path$Installer -Args "/silent /set up" -Verb RunAs -Wait; Take away-Merchandise $Path$Installer
</powershell>



Source link

Gravatar Image
I love to share everything with you

Leave a Reply

Your email address will not be published. Required fields are marked *