Built by IT engineers, made for IT teams.
Best PracticesNovember 19, 2026· 5 min read

Remove Local Admin Rights: How to Do It Without Chaos

Admin rights are a security risk, but removing them floods the helpdesk. How SMBs remove local admin rights: preparation, LAPS, Intune, GPO, exceptions.

Nico Haslberger
Nico HaslbergerCEO & Co-Founder · November 19, 2026
Share
Lokale Adminrechte entfernen: So klappt es ohne Chaos

Local admin rights are convenient. For attackers too.

“Can you give me admin rights real quick? I just need to install something.” In many small companies the answer has been the same for years: everyone has them anyway. Convenient – until an email attachment runs with the same rights and switches off the security software.

The opposite movement shows up in our support cases as well: after admin rights are removed, questions like “I can't change the IP address anymore” or “The printer driver won't install” come in. See Change IP address without admin rights. Both show: removing admin rights is the right thing to do – but it takes preparation.

Why local admin rights are a risk

Everything the user starts runs with their rights. With admin rights, that means:

  • Malware can install services, settle in permanently and switch off security software.
  • Users install unvetted software – including browser extensions and AI tools. See Shadow AI in the company.
  • Settings that IT sets centrally can be overridden locally.

Many questionnaires from cyber insurers therefore explicitly ask whether users work without local admin rights.

Remove Local Admin Rights: How to Do It Without Chaos – at a glance
Remove Local Admin Rights: How to Do It Without Chaos – at a glance

Step 1: Take stock

Before you remove rights: who has them, and what are they needed for?

  • Who is a member of the local Administrators group? On a device: net localgroup Administrators (on German-language Windows: Administratoren).
  • What are admin rights used for? Ask the employees – and go through the tickets of the last few months.
  • Which software needs admin rights at launch or update? Often line-of-business software, card readers, older industry-specific programs.

Step 2: Solve the typical cases beforehand

Most admin needs are always the same – and can be solved centrally:

  • Install software – distribute centrally (Intune, RMM, software distribution), Company Portal/self-service
  • Printer drivers – distribute in advance, universal driver – see Printer management in SMBs
  • Updates of line-of-business software – distribute centrally or use the vendor's update service
  • Network settings – centrally via policy or DHCP reservation
  • Program needs admin at launch – ask the vendor, compatibility settings, targeted exception

Step 3: Turn on Windows LAPS

Each device gets its own random password for the local administrator account.

Windows LAPS is built into current Windows versions. It:

  • sets a separate password per device,
  • changes it regularly,
  • stores it in Entra ID or Active Directory, where only authorized administrators can retrieve it.

Set it up in Intune under Endpoint security › Account protection › Local Admin Password Solution (Windows LAPS), in a domain via Group Policy. That leaves an emergency access without the same password sitting on all devices.

Step 4: Remove admin rights centrally

Not device by device, but via policy – otherwise the rights come back.

14 days free

IT support that fixes itself.

SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.

Start free trial
  • Intune: Endpoint security › Account protection › policy Local user group membership. Define who may be in the Administrators group – for example only the LAPS account and a group of IT administrators.
  • Group Policy (domain): Computer Configuration › Preferences › Control Panel Settings › Local Users and Groups – or Restricted Groups.
  • For Entra ID devices: Check whether users automatically become local admins at registration. In Entra ID under Devices › Device settings this can be turned off for new devices.

Proceed in stages: first a pilot group, then department by department.

Step 5: Handle exceptions

There are exceptions – but they should be specific, time-limited and traceable.

  • Approve individual programs instead of blanket rights – for example with Endpoint Privilege Management in Intune or comparable tools for privilege management.
  • A separate admin account for employees who administer regularly (e.g. in engineering) – not for everyday work, only when needed.
  • Document who has which exception and why.

Step 6: Make the support path clear

After the removal, the number of requests rises in the short term. That is normal – what matters is that they are resolved quickly:

  • Employees know where to request software or a setting.
  • Frequent requests are collected and solved permanently (see Helpdesk metrics).
  • IT can carry out elevated tasks in a targeted way without the user getting permanent rights.

How does SuperSupport help without admin rights?

This is exactly where SuperSupport comes in: the user describes in the chat what they need – a setting, a printer, a program. The agent on the Windows or Mac device checks what is going on, takes care of harmless things itself and submits steps that need elevated rights to IT for approval. The user does not get admin rights, and IT sees every step in the log. What that looks like for internal IT teams and MSPs is explained on the respective pages.

Remove Local Admin Rights: How to Do It Without Chaos – frequently asked questions
Remove Local Admin Rights: How to Do It Without Chaos – frequently asked questions

Frequently asked questions

Why shouldn't employees have local admin rights?

Because everything the user runs then runs with full rights – including malware from an email attachment. Without admin rights, malicious code can do much less damage: it can't install services, switch off security software or change system files. Many cyber insurers and security frameworks therefore ask about it.

How do I remove local admin rights centrally?

In Intune under Endpoint security › Account protection with a policy for local user groups, in a domain via Group Policy (Restricted Groups or Preferences › Local Users and Groups). First clarify which accounts should stay in the local Administrators group.

What is Windows LAPS?

The Local Administrator Password Solution built into Windows. It sets a separate, random password for the local administrator account on each device, changes it regularly and stores it in Entra ID or Active Directory. That way not every device has the same admin password.

What if an employee does need admin rights after all?

Don't grant them permanently. Solve the specific task instead: distribute the software centrally, set up an exception for a specific program, or have IT carry out the task. Tools for privilege management (such as Endpoint Privilege Management) allow elevated rights for individual, approved programs.

Which tickets come up after removing admin rights?

Typical ones are software installations, printer drivers, network settings such as a fixed IP address, updates of line-of-business software and devices such as card readers. If you collect these cases beforehand and solve them centrally, you keep the wave of tickets small.

14 days free

IT support that fixes itself.

SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.

Start free trial
Nico Haslberger

Nico Haslberger is Co-Founder & CEO of SuperSupport.ai. With years of experience as an IT technician, he knows the problems in IT support first-hand: from overloaded help desks to recurring tickets that slow teams down. That knowledge is built into every feature of the platform today. He makes sure SuperSupport.ai solves exactly the problems he experienced himself for years.

Share

This article was created with AI assistance and editorially reviewed.

Related Articles