In enterprise environments such as Windows Server 2019 Remote Desktop Services (RDS), organizations often require a standardized web browsing experience for all users. One of the most common administrative tasks is configuring browsers to open a specific homepage—such as **https://www.google.co.in**—every time users launch Google Chrome or Microsoft Edge.

While this can be configured manually for each user, doing so becomes impractical when managing dozens or hundreds of user accounts. Microsoft and Google provide Enterprise Policies that allow administrators to centrally manage browser settings through the Windows Registry or Group Policy.

This article explains how to configure Google Chrome and Microsoft Edge so that every user on a Windows Server 2019 system automatically starts with Google as the homepage and startup page using a single PowerShell script.

Why Use Browser Policies?

Browser policies provide several advantages over manually changing browser settings.

They are:

• Centralized
• Enforced automatically
• Applicable to all users
• Compatible with RDS environments
• Persistent even after browser updates
• Easy to deploy through scripts or Group Policy

Unlike user profile settings, policy settings are stored under:

HKEY_LOCAL_MACHINE

which means every existing and future user on the server inherits the same configuration.

Browsers Covered

This guide configures:

• Google Chrome
• Microsoft Edge (Chromium)

What This Script Configures

The script performs the following actions:

✅ Sets Google as Homepage

https://www.google.co.in

✅ Opens Google whenever the browser starts

✅ Applies to all user accounts

✅ Creates missing registry keys automatically

✅ Works on Windows Server 2019

PowerShell Script

Run PowerShell as Administrator.

$HomePage = "https://www.google.co.in"
#######################################################
# GOOGLE CHROME
#######################################################
New-Item -Path "HKLM:\SOFTWARE\Policies\Google\Chrome" -Force | Out-Null
Set-ItemProperty `
-Path "HKLM:\SOFTWARE\Policies\Google\Chrome" `
-Name HomepageLocation `
-Value $HomePage
Set-ItemProperty `
-Path "HKLM:\SOFTWARE\Policies\Google\Chrome" `
-Name HomepageIsNewTabPage `
-Value 0 `
-Type DWord
Set-ItemProperty `
-Path "HKLM:\SOFTWARE\Policies\Google\Chrome" `
-Name RestoreOnStartup `
-Value 4 `
-Type DWord
New-Item `
-Path "HKLM:\SOFTWARE\Policies\Google\Chrome\RestoreOnStartupURLs" `
-Force | Out-Null
Set-ItemProperty `
-Path "HKLM:\SOFTWARE\Policies\Google\Chrome\RestoreOnStartupURLs" `
-Name "1" `
-Value $HomePage
#######################################################
# MICROSOFT EDGE
#######################################################
New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" -Force | Out-Null
Set-ItemProperty `
-Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" `
-Name HomepageLocation `
-Value $HomePage
Set-ItemProperty `
-Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" `
-Name HomepageIsNewTabPage `
-Value 0 `
-Type DWord
Set-ItemProperty `
-Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge" `
-Name RestoreOnStartup `
-Value 4 `
-Type DWord
New-Item `
-Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge\RestoreOnStartupURLs" `
-Force | Out-Null
Set-ItemProperty `
-Path "HKLM:\SOFTWARE\Policies\Microsoft\Edge\RestoreOnStartupURLs" `
-Name "1" `
-Value $HomePage
#######################################################
# APPLY GROUP POLICY
#######################################################
gpupdate /force
Write-Host ""
Write-Host "Google Homepage successfully configured."
Write-Host ""

Understanding the Registry Values

HomepageLocation

Specifies the homepage URL.

HomepageLocation

Example

https://www.google.co.in

HomepageIsNewTabPage

0 = Use Homepage
1 = Use New Tab Page

Since we want Google:

0

RestoreOnStartup

Controls what happens when the browser starts.

For Google:

4

RestoreOnStartupURLs

Stores startup URLs.

Example

1 = https://www.google.co.in

Additional pages can be added:

1 Google
2 Company Portal
3 ERP
4 CRM

Registry Locations

Google Chrome

HKLM
 └ SOFTWARE
    └ Policies
       └ Google
          └ Chrome

Microsoft Edge

HKLM
 └ SOFTWARE
    └ Policies
       └ Microsoft
          └ Edge

Verify Policies

Google Chrome

chrome://policy

Click

Reload Policies

Microsoft Edge

edge://policy

Click

Reload Policies

Deploy Through Group Policy

Large organizations can deploy these registry settings using:

• Group Policy Preferences
• Startup Scripts
• PowerShell
• Microsoft Endpoint Manager (Intune)
• Configuration Manager (SCCM)

No manual configuration is required on individual user profiles.

Benefits for Remote Desktop Servers

Ideal for:

• Windows Server 2019 RDS
• Terminal Servers
• Schools
• Colleges
• Corporate Offices
• Call Centers
• Hospitals
• Government Offices
• Internet Cafés
• Training Institutes

Common Issues

Browser Already Running

Close and reopen Chrome or Edge after applying policies.

Policy Not Visible

Run:

gpupdate /force

Then reload policies.

User Changed Homepage Earlier

Policy settings override personal preferences.

Browser Installed Per User

Policies apply only to machine-wide installations. Ensure Chrome and Edge are installed for all users.

Security Benefits

Enterprise policies:

• Prevent unwanted homepage changes
• Standardize user experience
• Reduce helpdesk requests
• Protect against homepage hijacking
• Ensure compliance with organizational standards

Best Practices

• Use machine-level policies (HKLM) instead of per-user settings.
• Test the script on a staging server before production deployment.
• Keep Chrome and Edge updated with the latest enterprise versions.
• Combine homepage policies with other security settings such as disabling unnecessary AI features, enforcing safe browsing, and configuring startup pages.
• Maintain documentation of deployed browser policies for future audits and troubleshooting.

Conclusion

Using Windows PowerShell and browser enterprise policies is the most efficient way to configure Google Chrome and Microsoft Edge across all users on Windows Server 2019. By storing the configuration under HKLM\SOFTWARE\Policies, administrators can enforce a consistent startup page and homepage without modifying individual user profiles. This approach simplifies browser management in Remote Desktop Services (RDS) environments, reduces administrative effort, and ensures every user starts with the organization's preferred homepage.