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
Sharing one Administrator login between several people is risky: you cannot tell who did what, and one leaked password exposes everything. Give each person their own Windows account instead and grant Remote Desktop access only to the people who need it.
Standard user or administrator?
- Remote Desktop Users can log in over RDP and use installed programs, but cannot install software for everyone or change system settings. This is the right choice for most staff.
- Administrators can change anything, including other people's passwords. Keep this group small.
Create a user in PowerShell
Open PowerShell as Administrator. The first command asks for the new password without showing it on screen.
$pw = Read-Host -AsSecureString "Password for alex"
New-LocalUser -Name "alex" -Password $pw -FullName "Alex Smith" -PasswordNeverExpires
Add-LocalGroupMember -Group "Remote Desktop Users" -Member "alex"To make the user an administrator as well (only if they really need it):
Add-LocalGroupMember -Group "Administrators" -Member "alex"Create a user with the graphical tools
- Press Windows + R, type
lusrmgr.mscand press Enter. (On Windows 10/11 Home this console is not available; use the PowerShell steps above.) - Right-click Users → New User, fill in the name and password, untick User must change password at next logon if you will hand the password over yourself, and click Create.
- Open Groups → Remote Desktop Users, click Add and enter the new user name.
Test the new account
Keep your own session open and start a second Remote Desktop connection as the new user. If Windows asks for a domain, enter the user name as .\alex so it uses the local account.
Windows Server allows two simultaneous administrative Remote Desktop sessions without extra licensing. Windows 10/11 Pro allows one interactive session at a time, so a second login disconnects the first. Plan shared use around this.
Remove access later
Remove-LocalGroupMember -Group "Remote Desktop Users" -Member "alex"
Disable-LocalUser -Name "alex"Disabling keeps the user's files in C:\Users\alex in case you need them. Delete the account with Remove-LocalUser only once you have copied anything important.
Troubleshooting
- "The connection was denied because the user account is not authorized for remote login": the user is not in Remote Desktop Users or Administrators.
- "Your credentials did not work": see Fix "Your credentials did not work".
Next steps
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
RDP over UDP vs TCP: check and choose the transport
Remote Desktop can carry your session over TCP, UDP or both. Learn how each is used, how to see which one your session runs on, and how to force TCP when UDP misbehaves.
- Advanced
- Windows VPS · Admin RDP
- 5 min read