Press Windows + R, type gpedit.msc and press Enter. That opens the Local Group Policy Editor, which changes policy on the computer you are signed in to. It is built into Windows Server and the business editions of Windows, such as Pro. If you need to manage policy for a whole Active Directory domain, you want the Group Policy Management Console (gpmc.msc) instead, which you install as a feature: Install-WindowsFeature -Name GPMC on Windows Server, or the “RSAT: Group Policy Management Tools” optional feature on Windows 10 and 11. After any change, gpupdate /force applies it and gpresult /r shows what actually applied.

We could not run Windows in our test environment, so the steps below follow Microsoft’s documentation, linked in each section.
gpedit.msc vs GPMC: which tool do you need?
| Local Group Policy Editor | Group Policy Management Console | |
|---|---|---|
| Command | gpedit.msc | gpmc.msc (or search for Group Policy Management) |
| What it edits | The local Group Policy Object of one computer | Group Policy Objects stored in Active Directory |
| Needs a domain? | No | Yes, to be useful |
| Installed by default? | Yes, on Windows Server and business editions such as Pro | No: add the Group Policy Management feature or RSAT |
| Typical use | A stand-alone Windows VPS or dedicated server | Linking policies to sites, domains and OUs, backups, reports |
A stand-alone Windows VPS that is not joined to a domain only has local policy, so gpedit.msc is the tool you will use.
How to open the Local Group Policy Editor
- Sign in with an administrator account. On a remote server, connect with Remote Desktop first; see how to connect to a Windows VPS using Remote Desktop.
- Press Windows + R, or open the Start menu search.
- Type
gpedit.mscand press Enter. It also works from Command Prompt or PowerShell.
To edit policy for only some local users, Microsoft’s Local Group Policy Editor page describes opening it as a snap-in instead: run mmc, choose File, Add/Remove Snap-in, add Local Group Policy Editor, click Browse and pick the Users tab. There you can choose Administrators, Non-Administrators or a single user.
Finding your way around
The editor has two top-level sections, according to Microsoft:
- Computer Configuration: settings applied to the computer, at start-up and during background refresh.
- User Configuration: settings applied to users, at sign-in and during background refresh.
Each is split into Software Settings, Windows Settings (security settings, scripts) and Administrative Templates (most registry-based options). Select a setting under Administrative Templates and the pane on the right explains what it does and which Windows versions support it. Double-click it to set it to Enabled, Disabled or Not Configured.
Two useful settings for a Windows server
End idle and disconnected Remote Desktop sessions
Closing the Remote Desktop window disconnects you but leaves your session, and its programs, running. Over weeks this uses memory. Microsoft lists these settings under Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Session Time Limits:
- Set time limit for disconnected sessions
- Set time limit for active but idle Remote Desktop Services sessions
- Set time limit for active Remote Desktop Services sessions
- Terminate session when time limits are reached
The same settings exist under User Configuration; if both are set, the Computer Configuration value wins. Users get a warning two minutes before an idle session is disconnected or ended. Be careful with the active-session limit if you run long tasks interactively; running them as a scheduled task or service is safer.
Lock accounts after repeated failed sign-ins
Remote Desktop on the internet attracts password-guessing. The Account lockout threshold setting lives in Computer Configuration, Windows Settings, Security Settings, Account Policies, Account Lockout Policy. On a stand-alone server it defaults to 0, meaning accounts never lock, and Microsoft’s security baselines suggest 10 as a starting point. It takes effect without a restart.
Two cautions from the same page: an attacker who knows a user name can deliberately lock that account, and the built-in Administrator account is excluded from the policy. So a long, unique Administrator password still matters, and so does limiting who can reach port 3389 in the first place.
Apply and check your changes
Windows refreshes policy by itself: according to Microsoft’s Group Policy processing page, every 90 minutes plus a random offset of up to 30 minutes, and every five minutes on domain controllers. To apply a change now, open Command Prompt as administrator:
gpupdate /force
gpupdate normally applies only settings that changed; /force reapplies all of them. Some settings, such as software installation, only apply at start-up or sign-in, and /boot or /logoff handle those. Then check the result:
gpresult /r
gpresult /scope computer /r
gpresult /h C:\gp-report.html
gpresult shows the Resultant Set of Policy: what actually applied after all policies were combined. It needs an output option such as /r for a summary or /h for an HTML report you can open in a browser.
How to install the Group Policy Management Console
On Windows Server
In Server Manager, choose Add roles and features, continue to the Features page, tick Group Policy Management and install. Or in PowerShell as administrator:
Install-WindowsFeature -Name GPMC
On Windows 10 or 11
Microsoft’s RSAT article says the tools are part of Windows from version 1809 and are added under Settings, System (or Apps), Optional features, Add a feature; type “Remote” in the search box, as Microsoft suggests, and pick RSAT: Group Policy Management Tools. In PowerShell, the capability name comes from Microsoft’s Features on Demand list:
Add-WindowsCapability -Online -Name Rsat.GroupPolicy.Management.Tools~~~~0.0.1.0
RSAT cannot be installed on Home editions. On Arm64 devices running Windows 11 version 25H2, Microsoft says RSAT is added through Turn Windows features on or off instead.
Why your local setting might not stick
Policies apply in a fixed order: the local GPO first, then GPOs linked to the site, the domain and finally organisational units. Later ones win, so on a domain-joined server a domain policy quietly overrides whatever you set in gpedit.msc. If a setting keeps reverting, run gpresult /h and look at which GPO won. The fix is then in the domain policy, not on the server.
gpedit.msc not found?
- Check the Windows edition. Run
winver. Microsoft lists Group Policy as a Windows 11 Pro feature, so a Home edition is the usual reason the editor is missing. - Check for Server Core. A Windows Server installed without the Desktop Experience does not normally include the Microsoft Management Console (
mmc.exe) that snap-ins likegpedit.mscrun in; Microsoft’s App Compatibility Feature on Demand adds it. Otherwise, manage the server from another machine with GPMC or RSAT. - Run it as administrator. Standard users cannot change local policy.
Our Windows VPS plans include the Windows Server licence, so Group Policy is available from the first sign-in. If you would like someone to harden Remote Desktop or set up policies for you, our engineers are available by the hour.