Contact Us
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
drivera@cyberfox.com
Article
Last Month
AutoElevate is comprised of 4 basic components: Agents - and Agent service, which runs on each workstation that you want to manage AutoElevate Notification Server - Server which talks to the Agents Web Admin Portal - Console where MSPs can log in to control the system Notification Apps - Android, iOS, and Windows applications that technicians use
AutoElevate's Blocker feature gives you the ability to block 200+ native Windows applications, binaries, and .dll files that are typically used as Living off the Land (LOTL) attack vectors. Fileless malware, malware-free, or Living Off The Land refer to cyberattack techniques where the cybercriminal uses native, legitimate tools within the victim’s
Companies can get out of sync if they are deployed differently and fail to specify identical information. We recommend adopting a single deployment method (we offer various pre-made scripts for different RMMs here) and adhering to it consistently. In the meantime, you have the option to consolidate duplicate companies by following these steps: Selec
We no longer support Windows 7 but have previously identified a known issue that affects these machines running older versions of PowerShell. The latest AutoElevate agent relies on a function available only in PowerShell 5.0 and above. To determine the PowerShell version on your problematic machines, please follow these steps: Open PowerShell. Run t
No, deploying AutoElevate is incredibly straightforward and can be done across your MSP practice quickly. We're dedicated to supporting you at every step of the process. AutoElevate is deployed by simply installing the AEAgent on workstations. The AEAgent is a small, lightweight MSI file that can be deployed silently using various methods such as RM
We are currently assessing the necessity of macOS compatibility for our customers. If you are interested in this feature, please refer to our Roadmap Map located at https://github.com/AutoElevate/roadmap. Our aim is to allocate our development resources to areas that are most important to you.
Many of our partners have set up AE user accounts for their clients, allowing their administrators to approve their own requests. Typically, these users are assigned the "Technician (Level 1)" or "Technician (Level 2)" role to prevent them from modifying their permissions or accessing other user accounts. We've created a comprehensive document that
When the end user has made a request and the timer expires an additional dialog box with appear that states that the technician is evaluating the request, a ticket has been opened, and that they will be notified as soon as a technician responds. When a technician does respond a new notification appears for the user telling them their request has
The Agent’s Windows Event Logs are provided to give you visibility into what the AutoElevate Agent observes and how it operates on the system. They can be ingested by a SIEM or syslog service to better automate events happening within AutoElevate. This feature can be enabled or disabled in the Admin Portal settings. Some of the events do contain
The Process Once the API token has been set up and AutoElevate is successfully communicating with your Halo PSA account, you will be able to complete the configuration and integration via the admin portal. How to Setup the Halo API Application In your Halo web portal, create an API application for your AutoElevate integration by doing the following
Rules that have been defined are securely encrypted and stored in a protected section of the registry during each check-in. These rules continue to function seamlessly, whether you have internet connectivity or access to our services. For situations where no specific rule exists, we default to a position of enhanced security, allowing the User Accou
Sometimes, a password synchronization problem may arise between Azure Active Directory (AzureAD) and the local machine, particularly when users primarily log in using a PIN rather than their password. In such cases, if the password is changed on the AzureAD side, it may not always sync correctly with the local device until specific actions are taken
Universal User Prompts: No Admin Distinctions AutoElevate will prompt any user regardless of whether they are local/domain admin or not. There are 2 main ways to modify the default behavior and prevent AE from auto intercepting UAC prompts. The first is on a Computer by Computer basis. If you set the Computer in "Audit" or "Policy" mode (read mo
This can be done by modifying the "AGENT_MODE" argument that can be passed to the MSI installer at time of deployment. You can see how to do this in the following article: System Agent Installation .
Uninstalling AutoElevate is straightforward and can be done either from our Admin Portal or via a command line. Here's how: Method 1: Using the Admin Portal Access our Admin Portal. In the Computers section, locate the specific computer you wish to uninstall. Click the "Trash Can" icon next to the computer's entry. For bulk uninstallation: Fil
By default, third-party Windows services are not permitted to start in Safe Mode. To ensure that our agent does not interfere with your ability to access Safe Mode, we do not automatically configure it to start in Safe Mode. This allows you to enter Safe Mode without any hindrance from the agent if it is not functioning properly. Enabling AE Agent i
No, AutoElevate is a cloud-based service and software platform. All you need to get started is a license key and instructions. We handle server maintenance, mobile apps, security, updates, and web portals.
We are aware of a limitation in QuickBooks design, where it does not prompt for User Account Control (UAC) for standard users. When standard users need to update QuickBooks, they must right-click on it and select "Run As Admin." This action triggers the UAC and subsequently activates AutoElevate. To simplify this process for end-users, some clients
Right now, all technicians that have the Mobile Notification app installed will receive notifications from your clients . They can quiet the notifications by adjusting notifications on their phones. We currently have plans to build a scheduling system for the notifications which will allow your AutoElevate administrator to adjust which technicians r
While the timer is active, the Agent operates in "fast-talk" mode, ensuring immediate responses to your approval or denial of requests from the user. However, there are some nuances to be aware of: Real-Time Response: During the timer's operation, user requests trigger immediate responses. Out-of-Timer Approvals/Denials: Approvals, denials, or rule
This message serves as additional guidance to assist you. It advises you to right-click on the installer and select "Run As Admin." In some cases, installers may extract another executable file into the "AppData/Local/Temp" folder and execute it from there. These files often lack metadata, making them challenging to identify. Furthermore, the "App
In cases where User elevation fails due to an incorrect password, the dialogue box should typically include a field for entering a new password. However, if you do not see this option, you can manually update the password stored by AutoElevate for the user by following these steps: Open the "C:\Program Files (x86)\AutoElevate\AECredentialInput.exe"
We suspect this to be related to a recent Windows bug that causes conflicting registry keys within the UAC. Please follow these steps as a solution that should fix the issue: Go to the Computers screen of the AE admin portal. Select one of the machines that are experiencing the issue by checking the checkbox. From the Actions menu, set the UAC
When users attempt to delete specific desktop shortcuts, UAC prompts may appear. This occurs because these shortcuts are located in the C:\Users\Public\Public Desktop folder. By default, this folder grants the "Interactive" user Read & Execute/List/Read NTFS permissions but lacks 'Modify' or 'Write' permissions. This limitation prevents standard
The issue may be that the standard UAC is not being prompted but instead, the UAC prompts with the username already set. This usually means the user itself or a group the user is associated with is a member of one of the following Windows groups: Backup Operators Cryptographic Operators Network Configuration Operators Power Users If you
Blocker has been designed to counteract potential threats from malicious actors or activities that exploit native programs within your network. With the capability to block over 200 native Windows applications, binaries, and .dll files commonly leveraged as Living off the Land (LOTL) attack vectors, Blocker serves as a defense mechanism against thes
Please ensure that the Agent for that specific computer is set to "Live" mode, and the User Account Control (UAC) is configured to prompt. Additionally, it's worth noting that not all installers trigger the UAC prompt, especially those that install into the local user area rather than Program Files. AE is designed to respond to the UAC appropriately
No, you can have as many technicians using the system as you desire. The monthly charge is based on the number of agents that are registered and active on machines.
No, when the user request is granted, their session for that action is elevated from a standard user to an admin user. This has the advantage of not requiring the storage or maintenance of a database of user credentials, making security tighter, faster, and easier to manage.
This issue can occur when the Remove Admin Privileges feature is activated, resulting in users being removed from the Administrators Group, which previously had permission to Allow Remote Access. To resolve this, follow these steps: Check Group Membership: Ensure that affected users are now only members of the Users Group. Verify Remote Login Permi