{"id":13044,"date":"2025-07-20T07:52:04","date_gmt":"2025-07-20T14:52:04","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=13044"},"modified":"2025-07-23T05:52:20","modified_gmt":"2025-07-23T12:52:20","slug":"non-admins-control-services-remotely","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/windows-services\/non-admins-control-services-remotely\/","title":{"rendered":"Q&A: Why Can’t Non-Admins Start\/Stop Windows Services Remotely?"},"content":{"rendered":"
\"Why<\/div>\n
\n  I’ve used Service Security Editor<\/a> to give a group of non admins rights to start and stop services on a server. However when trying to do this remotely, access fails (they don’t have any other rights on the server). I assume they need rights to remotely access Service Control Manager?<\/p>\n

Do you have any relevant article that explains how to do this, giving them only the required rights? I don’t want to add them as Power Users or anything like that that might enable them to log in to the server using RDP.<\/p>\n

— Gordon<\/p>\n<\/div>\n

Hi Gordon, thanks for reaching out.<\/p>\n

You’re on the right track here. Even though you’ve used Service Security Editor to grant permissions on the service, there’s still one more obstacle to overcome for normal user accounts. Let’s recap and dig into the solutions available.<\/p>\n

\n

Service Security Editor enables local control…<\/h2>\n

As you’ve seen, Service Security Editor will do the heavy lifting. With a few clicks, you can quickly setup your users to start, stop or restart any service you choose. And after your changes, they can use the NET command<\/a>, the SC command<\/a> or the Services application<\/a> — whatever they like.<\/p>\n

In our experience, most folks stop here because local control is all they need. But you require remote access as well, and that raises security concerns — especially for accounts without admin rights.<\/p>\n

\n

…But Microsoft established additional restrictions on remote access<\/h2>\n

Starting in Windows 10 version 1709 and Windows Server 2016 version 1709, only users who are local administrators on a remote computer can start or stop services on that computer<\/b>. This technical article<\/a> discusses the situation.<\/p>\n

To overcome this restriction and allow your users control a service remotely, you have a couple of options. You can either:<\/p>\n

    \n
  1. \n

    Promote your users to administrators on the remote computer. Since the remote access restriction only applies to non-admins, they will no longer be rejected when they come in as an administrator; or<\/p>\n<\/li>\n

  2. \n

    Add your service to the remote access check exemption list<\/b> — the set of services that bypass the remote access restrictions and can be controlled remotely by normal users.<\/p>\n<\/li>\n<\/ol>\n

    The first option may be the quickest and most familiar because it’s easy to switch a normal user to an administrator. However, going that route may have unintended security implications. Do you really want to empower your users to do anything they want on the remote server?<\/p>\n

    The second approach involves editing the registry, which, of course, brings its own concerns. But at least it doesn’t come with hidden security consequences. We recommend going that way, so let’s take you through it in the next section.<\/p>\n

    \n

    How to add your service to the remote access check exemption list<\/h2>\n

    Fortunately, Microsoft makes it fairly easy to add a service to the remote access check exemption list. And once the service is there, your non-admin folks will be able to control the service as desired.<\/p>\n

    To add your service to the list, step by step:<\/p>\n

      \n
    1. \n

      Start the Windows Registry Editor (“Regedit”) on the remote computer. Since it’s an admin tool, you’ll need to be an administrator to run Regedit:<\/p>\n

    2. \n

      Navigate to this key:<\/p>\n

      Computer\\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\SecurePipeServers\\SCM<\/b><\/p><\/blockquote>\n

      \"Go<\/a><\/div>\n

      If you don’t see a SCM<\/b> key — which is normal on some systems — create it by right-clicking the SecurePipeServers<\/b> key on the left and selecting New > Key<\/b><\/nobr>.<\/p>\n<\/li>\n

    3. \n

      In the left panel, right-click the SCM key and select New > Multi-String Value<\/b><\/nobr>:<\/p>\n

    4. \n

      In the new value that gets created on the right, set the name to RemoteAccessCheckExemptionList<\/b>:<\/p>\n

    5. \n

      Double-click RemoteAccessCheckExemptionList<\/b> to edit its value. In the window that comes up, add the name of your service. But be sure to use your service’s “real” name and not its display name, which may be different.<\/p>\n

      For example, here’s what that looks like when we added Print Spooler, where the service name is Spooler:<\/p>\n

    6. \n

      Back in the main Registry Editor window, you should now see your service(s) in the RemoteAccessCheckExemptionList value:<\/p>\n

    7. \n

      Finally, close Registry Editor.<\/p>\n<\/li>\n<\/ol>\n

      And with your service on the remote access check exemption list, your non-admin users with rights to the service shouldn’t have any trouble manipulating the service. The dreaded “access denied” error will be a relic of the past.<\/p>\n

      \n

      Coming soon: Service Security Editor will update the remote access check exemption list for you<\/h2>\n

      Our team has already started sketching how to enable non-admin remote access with Service Security Editor. And once that new version of our free software is out, you won’t have to read technical articles from Microsoft or mess with the Windows Registry — unless you really, really want to. \ud83d\ude42<\/p>\n

      \n
      \n\n\n\n
      Read more about Windows Services\u2026<\/nobr><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n