{"id":3797,"date":"2022-01-25T03:23:00","date_gmt":"2022-01-25T03:23:00","guid":{"rendered":"https:\/\/www.adminbyrequest.com\/?p=3797"},"modified":"2026-01-25T07:55:18","modified_gmt":"2026-01-25T07:55:18","slug":"new-feature-spotlight-clean-up-local-admins","status":"publish","type":"post","link":"https:\/\/www.adminbyrequest.com\/en\/blogs\/new-feature-spotlight-clean-up-local-admins","title":{"rendered":"New Feature Spotlight: Clean Up Local Admins"},"content":{"rendered":"\n

Staying on top of your admin accounts is no easy feat.<\/strong><\/p>\n\n\n\n

This is particularly true for older, larger companies that have created admin accounts when onboarding new employees and have been unable to keep track of them over time.<\/p>\n\n\n\n

The problem that results is an untracked number of rogue accounts that have elevated access, but may not be being used, monitored, or protected adequately.<\/p>\n\n\n\n

Every one of these rogue admin accounts doubles as a point of access for cyber criminals searching for elevated privileges to launch an attack, and the more these you have, the greater your attack surface, and the higher the risk of a security breach.<\/p>\n\n\n\n

Leaving them be is a dangerous option, but even more so is eliminating them all and unintentionally rendering your endpoints unusable.<\/p>\n\n\n\n

With Admin By Request version 7.3, we\u2019ve added a feature that makes the job of tidying up your loose ends (i.e., loose admin accounts) easy:<\/p>\n\n\n\n

Clean Up Local Admins.<\/strong><\/p>\n\n\n\n

Feature Overview<\/h2>\n\n\n\n

The Clean Up Local Admins feature allows you to get rid of unwanted administrator accounts with the click of a button.<\/p>\n\n\n\n

Admin By Request already provides a \u2018birds-eye\u2019 view of all your administrator accounts in a single place; that single place now includes a Revoke Rights button for each Admin account.<\/p>\n\n\n\n

The idea is to eliminate the cumbersome task of locating these unused accounts and having to disable each of them from the endpoint they belong to. Instead, you can get the job done on multiple endpoints from a single place \u2013 your Admin By Request User Portal.<\/p>\n\n\n\n

Using the Feature<\/h2>\n\n\n\n
    \n
  • Navigate to the Inventory page, select an endpoint, and click the Local Admins item from the left-hand menu to get to the \u2018birds-eye\u2019 view of all of your administrator accounts on that endpoint (now illustrated as cards for each account):<\/li>\n<\/ul>\n\n\n\n
    \"\"\/<\/figure>\n\n\n\n
      \n
    • Each account card indicates what type of admin account it is by it\u2019s name and icon:<\/li>\n\n\n\n
    • AzureAD account – cloud icon<\/li>\n\n\n\n
    • Domain account – computer network icon<\/li>\n\n\n\n
    • Built-in Windows Administrator account – computer icon<\/li>\n\n\n\n
    • Local admin account – person with shield icon<\/li>\n\n\n\n
    • Etc.<\/li>\n\n\n\n
    • For every endpoint that has Admin By Request 7.3 installed (and is able to be removed \u2013 more on this further down), the Clean Up Local Admins feature is available, indicated by an orange Revoke Rights button in the top-right corner of the account card.<\/li>\n\n\n\n
    • Identify the accounts you want to \u2018clean up\u2019 based on their name and type (dead accounts may be indicated by long numbers in the place of a distinguishable name). Simply click the button for every admin account you want to remove.<\/li>\n\n\n\n
    • When selected, the button changes from Revoke Rights<\/em> to Cancel Revoke<\/em>, and orange fill, to orange outline. If you make a mistake in revoking, you can easily undo the action by selecting the button:<\/li>\n<\/ul>\n\n\n\n
      \"\"\/<\/figure>\n\n\n\n
        \n
      • Once an admin account is revoked, it is moved to a new section on the same page called Restore Revoked Local Administrators<\/em>. It remains here for two weeks after revocation, during which time you can select the Restore Rights<\/em> button in the top-right corner:<\/li>\n<\/ul>\n\n\n\n
        \"\"\/<\/figure>\n\n\n\n
          \n
        • As account-removals are issued, the details are listed in the Events<\/em> section of the Local Admins page, including the time of the event, the action undertaken (i.e., \u2018X account removed\u2019), the account that the action was taken on, and the name of the user who instigated the action:<\/li>\n<\/ul>\n\n\n\n
          \"\"\/<\/figure>\n\n\n\n
            \n
          • After selecting Revoke Rights, the action is completed within four hours on the endpoint \u2013 an event which is also displayed in the Events table when it completes.<\/li>\n\n\n\n
          • There are safeguards built in to the feature to ensure you cannot remove certain accounts that would prevent you from logging in to your endpoints. These accounts include Active Directory\\Domain Administrators, AzureAD\\Device Administrators, AzureAD\\Company Administrators, and the built-in Windows Administrator account.<\/li>\n<\/ul>\n\n\n\n

            Access via Reports Page<\/h2>\n\n\n\n

            You can also use the Clean Up Local Admins feature via the Reports page, which includes functionality to reverse accidental removal of multiple accounts at a time.<\/p>\n\n\n\n

            Removing Accounts from Reports:<\/strong><\/p>\n\n\n\n

              \n
            • Navigate to Reports > Endpoint Reports > Local Admins<\/em>, and make sure you are in the Local Admins tab. Here, you get your administrator view in a list form, however, this list groups all admin accounts of the same type together, with the number of accounts listed in the Occurrences<\/em> column:<\/li>\n<\/ul>\n\n\n\n
              \"\"\/<\/figure>\n\n\n\n
                \n
              • As with the admin account cards shown in Inventory, these accounts are also classed by name and icon, and only those with version 7.3 installed have the Remove button available (in the right-hand column of the table).<\/li>\n\n\n\n
              • Locate rogue accounts and remove them by selecting the Remove button. Again, dead \/ rogue accounts are often indicated by a long number instead of a name (and there will often only be one of them \u2013 listed in the Occurrences column).<\/li>\n<\/ul>\n\n\n\n

                Undoing Remove:<\/strong><\/p>\n\n\n\n

                Using the Remove feature from the Reports page provides the ability to remove large numbers of accounts in one go. For example, if you remove an account group which has 60 occurrences, all 60 will be removed at the single click of a button.<\/p>\n\n\n\n

                While very useful when used intentionally, it is possible to do this by mistake. Follow the steps below to reverse unintentional removal of local admin rights.<\/p>\n\n\n\n

                  \n
                • On the Local Admins page (Reports > User Reports > Local Admins<\/em>), locate and click the Restore Rights tab at the top of the page:<\/li>\n<\/ul>\n\n\n\n
                  \"\"\/<\/figure>\n\n\n\n
                    \n
                  • Use the drop-down menu next to Show revokes since<\/em> to view the appropriate groups:<\/li>\n<\/ul>\n\n\n\n
                    \"\"\/<\/figure>\n\n\n\n
                      \n
                    • The list on the page displays removed groups of local admins. Locate the group that you want to reverse the Remove action on, and click the Undo button in the right-hand Action column.<\/li>\n\n\n\n
                    • The group will have their local admin rights returned, and appear in the list under the Local Admins tab.<\/li>\n<\/ul>\n\n\n\n

                      Summary<\/h2>\n\n\n\n

                      The Clean Up Local Admins feature new to version 7.3 is designed to make your environment tidier and more secure, and gives you the power to achieve this in a much more manageable way than what was previously possible.<\/p>\n\n\n\n

                      Minimize your attack surface and get on top of your local admin accounts with the latest version of Admin By Request.<\/p>\n","protected":false},"excerpt":{"rendered":"

                      This feature makes the job of tidying up your rogue – and potentially dangerous – local admin accounts easy.<\/p>\n","protected":false},"author":2,"featured_media":567,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[146,144,106,145,117,76],"ppma_author":[9],"class_list":["post-3797","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","tag-admin-clean-up","tag-clean-up-local-admins","tag-features","tag-local-admins","tag-new-feature","tag-update","entry","has-media"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t