{"id":11702,"date":"2023-10-23T03:40:32","date_gmt":"2023-10-23T10:40:32","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=11702"},"modified":"2025-12-15T06:21:22","modified_gmt":"2025-12-15T14:21:22","slug":"secure-windows-service","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/secure-windows-service\/","title":{"rendered":"Q&A: How do I Protect my AlwaysUp Services from Unauthorized Changes?"},"content":{"rendered":"
\"Q&A:<\/div>\n
\n  Dear support,<\/p>\n

It is possible to protect AlwaysUp by password to prevent unauthorized change of settings or unauthorized intervention?<\/p>\n

— Tom\u00e1\u0161<\/p>\n<\/div>\n

Hi Tom\u00e1\u0161, thanks for getting in touch.<\/p>\n

I can tell you that safety and security<\/a> are front and center as we develop AlwaysUp. Indeed, here are a couple of ways that AlwaysUp helps to protect your applications from unauthorized changes.<\/p>\n

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

Only Administrators can run AlwaysUp<\/h2>\n

First, only users who have admin rights can start AlwaysUp. That’s because AlwaysUp is installed as a User Account Control (UAC)<\/a> administrative utility that requires elevated rights to run.<\/p>\n

No doubt you’ve already noticed the UAC restrictions in play. For example, they greet you with a protective prompt whenever you start AlwaysUp on Windows 11:<\/p>\n

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

If you click “No”, AlwaysUp will not start.<\/p>\n

Note that non-administrators see a different prompt. Instead of simply having to acknowledge elevation, those users must enter the user name and password of an administrator to continue:<\/p>\n

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

So that’s the general security in place. Next, we’ll review how you can protect individual applications you’ve deployed with AlwaysUp.<\/p>\n

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

Restrict access to the Windows Services that AlwaysUp creates<\/h2>\n

For each application you add, AlwaysUp installs a Windows Service to manage it. Indeed, you can see those AlwaysUp-created services in the Services<\/a> application.<\/p>\n

For example, here is the service that AlwaysUp created to run Microsoft OneDrive 24\/7<\/a>:<\/p>\n

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

And because they are “true” Windows Services, Microsoft’s robust permissions system extends to the entities created by AlwaysUp. You can manage them like any other service, setting exactly who can start, stop or edit them.<\/p>\n

So, to set the permissions for your AlwaysUp application\/service:<\/p>\n

    \n
  1. \n

    If your application is running in AlwaysUp, stop it now. You can update permissions only when the service is idle.<\/p>\n<\/li>\n

  2. \n

    Highlight your application and select Application > Advanced > Service Security Settings<\/b>:<\/p>\n

  3. \n

    The Service Security Settings<\/b> window shows all the users and groups with rights over the service that AlwaysUp created. For example, you’ll likely find that anyone in the built-in Administrators group<\/a> has full control:<\/p>\n

  4. \n

    Adjust the service’s permissions as you see fit.<\/p>\n

    For example, to prevent someone from updating or deleting the service:<\/p>\n

      \n
    1. \n

      Click the Add<\/b> button and add that person to the top panel. We’ve selected “Hazel Smith” on our computer; she currently has full rights to the service (inherited from the Administrators group):<\/p>\n

    2. \n

      In the lower panel, check the Modify<\/b> and Delete<\/b> boxes in the Deny<\/b> column:<\/p>\n

    3. \n

      Click OK<\/b> to record your changes.<\/p>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

      With your updated restrictions in place, the users who you have denied access to the service won’t be able to change your application in AlwaysUp.<\/p>\n

      For example, if Hazel tries to update our OneDrive entry in AlwaysUp, the attempt to save fails with an “Access denied” error:<\/p>\n

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

      Hopefully, you will be good to go after adjusting permissions. But a note of caution…<\/p>\n

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

      Please be careful when updating service permissions!<\/h2>\n

      You don’t want to lock yourself out.<\/p>\n

      Pay particular attention when adjusting the rights of groups. Because “Deny” rights take precedence over “Allow” rights, you will strip away your own rights if you block a group that you’re a member of. And once you block your own account, you won’t be able to restore your rights without help.<\/p>\n

      If you do make a mistake, look to our Service Security Editor<\/a> program to help you fix the problem. And this article<\/a> offers a few troubleshooting tips.<\/p>\n

      \n
      \n\n\n\n
      More articles about AlwaysUp…<\/nobr><\/span><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n