Local Group Policy Editor basics for a standalone server
Use gpedit.msc on a Windows VPS or Admin RDP that is not in a domain, understand computer and user settings, apply changes with gpupdate and check them with gpresult.
- Intermediate
- Windows VPS · Admin RDP
- 5 min read
The Local Group Policy Editor (gpedit.msc) controls hundreds of Windows settings from one place. On a standalone server, one that is not part of an Active Directory domain, it is the main way to set rules such as Remote Desktop session limits or update behaviour. This guide explains how the editor is laid out, how to apply and check a change, and a few policies that are useful on a remote server.
Before you start
- Administrator access over Remote Desktop to
203.0.113.10:12230. - The browser console in your Dashboard as a fallback, in case a policy affects your own sign-in.
- Windows Server, or Windows 10/11 Pro or higher. Home editions do not include
gpedit.msc.
Open the editor
Press Win + R, type gpedit.msc and press Enter.
The left pane has two top-level sections:
- Computer Configuration: settings that apply to the whole machine, whoever signs in. Most server settings live here.
- User Configuration: settings that apply to users when they sign in. In the local editor they apply to all users on the machine.
Each section has three folders:
- Software Settings: rarely used on a standalone server.
- Windows Settings: includes Security Settings, which is the same content you see in
secpol.msc, and logon or startup Scripts. - Administrative Templates: the large tree of settings for Windows components, such as Remote Desktop Services and Windows Update.
Read and change a setting
- Browse to a setting in the tree and double-click it.
- Choose Not Configured, Enabled or Disabled.
- If enabled, fill in any options in the lower-left box.
- Read the Help box on the right. It explains exactly what each state does.
- Click OK.
Not Configured means "let Windows use its default". Setting a policy back to Not Configured is the clean way to undo a change.
To find a setting by name, select Administrative Templates, then use Action → Filter Options and enable keyword filters. Turn the filter off again afterwards, or the tree will look empty.
Apply changes with gpupdate
Windows refreshes policy in the background every so often, but you can apply changes immediately. Open PowerShell or Command Prompt as Administrator:
gpupdate /forceExpected output:
Updating policy...
Computer Policy update has completed successfully.
User Policy update has completed successfully.Some settings only take effect after a sign-out or a restart. If so, gpupdate tells you.
Check what is applied with gpresult
gpresult shows which policies are in effect:
gpresult /r /scope computerOn a standalone server the list mostly says Local Group Policy. That is expected. For a detailed, readable report of every applied setting, create an HTML file and open it in a browser:
gpresult /h C:\PolicyBackup\gp-report.htmlCreate the C:\PolicyBackup folder first if it does not exist. Run gpresult from an elevated prompt to include computer settings.
Useful policies for remote servers
These all live under Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host:
- Session Time Limits → Set time limit for disconnected sessions: signs out sessions left disconnected for too long. Leave this off if you run apps, such as trading terminals, in a disconnected session. See RDP session time limits.
- Connections → Restrict Remote Desktop Services users to a single Remote Desktop Services session: each user gets one session, and reconnecting resumes it.
- Security → Require user authentication for remote connections by using Network Level Authentication: makes users authenticate before a session starts, which reduces load from attackers.
- Device and Resource Redirection → Do not allow Clipboard redirection or Do not allow drive redirection: stops copy-paste or drive sharing for tighter security.
Under Computer Configuration → Administrative Templates → Windows Components → Windows Update, you can control when updates install and whether the server may restart automatically. Sub-folder names differ between Windows versions, so use the keyword filter to find Configure Automatic Updates and the restart-related settings.
Do not disable Remote Desktop connections or change the Remote Desktop port through policy. The setting Allow users to connect remotely by using Remote Desktop Services, if set to Disabled, will cut off your RDP access on port 12230.
Back up and reset local policy
Local policy for Administrative Templates is stored in C:\Windows\System32\GroupPolicy. To back it up, copy that folder (it is hidden) while signed in as an administrator:
Copy-Item -Path "$env:windir\System32\GroupPolicy" -Destination "C:\PolicyBackup\GroupPolicy" -RecurseIf policies cause a problem and you cannot find the bad setting, set it back to Not Configured. As a last resort, renaming the GroupPolicy folder and running gpupdate /force resets Administrative Template settings to defaults. Security settings are separate and are not reset this way.
Check it works
After changing an RDP policy, run gpupdate /force, then open a second Remote Desktop session to 203.0.113.10:12230 while the first stays open. Confirm the new behaviour and that you can still sign in.
Troubleshooting
- "Windows cannot find gpedit.msc": you are on a Home edition, which does not include the editor.
- A policy seems to have no effect: run
gpresult /hand check the setting is listed. Some need a restart or a new sign-in. - Locked out after a policy change: sign in through the browser console in the Dashboard, set the policy back to Not Configured and run
gpupdate /force. - The tree looks empty: a filter is on. Use Action → Filter Options and clear it.
Next steps
- Security-specific settings: Local Security Policy basics on Windows Server.
- Keep sessions alive for always-on apps: Keep apps running 24/7 on RDP.
- Compare Windows Admin RDP plans.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Windows VPS & RDP
RunRacks RDP port 12230: how to connect to your Windows VPS and Admin RDP
RunRacks Windows VPS and Admin RDP servers accept Remote Desktop on port 12230, not 3389. Here is how to connect from every device and keep the port open.
- Beginner
- Windows VPS · Admin RDP
- 5 min read
Windows VPS & RDP
Allow or block multiple RDP sessions for one user
Understand why a new Remote Desktop login takes over your old session, how the single-session policy works on Windows Server, and which setting suits a team.
- Advanced
- Windows VPS
- 5 min read
Windows VPS & RDP
Create Windows users with Remote Desktop access
Give each person their own Windows login, add them to Remote Desktop Users, test the account and remove access cleanly later.
- Beginner
- Windows VPS · Admin RDP
- 2 min read