What is your primary use case for Ivanti Neurons for UEM?

Our main use case for Ivanti Autonomous Endpoint Management is to perform Windows patching and third-party application patching to set up an automated schedule so that all the endpoints are updated on time and as per the user's convenience. A specific example of how we use Ivanti Autonomous Endpoint Management for patching is that a customized update prompt or a reboot prompt is very important for us because we do not want to reboot our users during or after hours since we do not know when the users are working. We customize the reboot prompt and provide options to the users, allowing them to extend the timing, do it immediately, or whenever they are ready, which helps us manage our end-user experience in a better way. Regarding our main use case, we do a lot of things using Ivanti Neurons where we run scripts to get files, delete files, and make automated adjustments remotely.

Ivanti Autonomous Endpoint Management is our main solution to manage all of our endpoints. Our help desk uses it to remote control devices. We use it to install and uninstall software and to look at the status of machines, such as whether they are running out of disk space. There are numerous uses that we give to it. A specific example of how my team used Ivanti Autonomous Endpoint Management recently involves an issue where we found that a number of endpoints had malicious software installed on them. We used it to first find which machines had it and then remove that software from those endpoints. It was incredibly useful and saved us a tremendous amount of time. Our help desk uses it to remote control devices, which helps for remote users who do not connect to our corporate network very often. However, they can still contact remote workers to ensure that everything is okay, and when they have issues, they can remote control in. This saves a lot of time and trouble for everyone involved.

The main use case for using Ivanti Autonomous Endpoint Management is to track the incidents which we get from our project which is in support. Generally, the client raises the instance such as service requests or change requests. We get those as tickets via Ivanti Autonomous Endpoint Management, and we handle them and try to close them using the tool from its new status to the closure part.

My main use case for Ivanti Autonomous Endpoint Management is patching endpoints, desktops, and servers. I use Ivanti Autonomous Endpoint Management to meet the 14-day compliance window for critical patches to be applied. Patching is the primary focus, but I also use Ivanti Autonomous Endpoint Management as an RMM solution and as a CMDB for endpoints.

My main use case for Ivanti Autonomous Endpoint Management is support. I use Ivanti Autonomous Endpoint Management in my daily work to review tickets and look at issues and access requests. I have been examining the task flows and access to the dialogues globally regarding my main use case for Ivanti Autonomous Endpoint Management.

My main use case for Ivanti Autonomous Endpoint Management revolves around endpoint health, patching, vulnerability remediations, and proactive issue resolutions on a day-to-day basis. I use it to identify endpoints with security configuration issues, prioritize devices based on risk, and automate remediation wherever possible. If the platform detects a known application issue on an endpoint, an automated bot can perform predefined remediation and verify the result, thus saving the endpoint team from manually connecting to the device, troubleshooting it, and potentially opening and updating a service ticket. I believe the biggest value lies in the closed-loop approach that detects, diagnoses, remediates, and verifies the endpoint is healthy again, shifting support from reactive troubleshooting to proactive self-healing.

My main use case for Ivanti Autonomous Endpoint Management is to have streamlined management of all the endpoints within our infrastructure, whether related to VDI or our Citrix infrastructure. We used to have all policies and specific configurations related to registries, files, and startup scripts that could be done without group policy, which we managed via Ivanti application. To cater to all policies related to what we have set within group policy, including computer policies or user policies, since Ivanti takes precedence over group policies within the infrastructure, we apply similar computer policies or user policies along with any additional policies required, such as disabling drives, hiding drives, getting permissions, catering permissions, and how permissions act on those devices. We manage these in our infrastructure along with creating registries for user-specific items, such as HKCU-specific items that we can publish to remediate application-related issues or to enforce computer-level or user-level policies. We are mostly using Ivanti Autonomous Endpoint Management for endpoint management and not for other applications or patch management. Our use is specifically focused on endpoint management.

My main use case for Ivanti Autonomous Endpoint Management involves the deployment of Ivanti Autonomous Endpoint Management on 25,000 assets. This deployment on 25,000 seats benefits my organization because we are able to support and update the entire infrastructure through Ivanti Autonomous Endpoint Management.

Ivanti Neurons for UEM serves as our main solution for utilizing EPM for Endpoint Manager to manage endpoints, obtain inventory data, push software, and conduct patch analysis. We also use UE and EPM, Endpoint Manager Mobile, for managing mobile devices to ensure secure applications such as email and Email+.

My main use case for Ivanti Neurons for UEM is device management, patch management, risk and vulnerability management, Edge Intelligence, and the bots. I use Ivanti Neurons for UEM every day to patch devices and monitor them automatically so that staff only need to check it, which improves the user experience. I cannot give exact figures, but we now have a patch level of 95% of devices patched on average, which we did not have before. Ivanti Neurons for UEM's end-to-end remediation process has had a significant impact on risk reduction in my IT environment, as everything is always up to date, everything is monitored automatically, and as a result, the risk has dropped massively.

My main use case for Ivanti Neurons for UEM includes several use cases that depend on the team level where I am leading and the period. One example is device provisioning, where we're trying to implement a sort of touchless deployment using Autopilot and Apple Business Manager. Another use case is patch management for deploying Windows updates, OS updates, and rollouts. Additionally, I focus on software inventory to track installed applications and license usage, compliance management to enforce encryption, password, firewall, and security configuration, as well as asset management for maintaining real-time inventory. We have more than 20 different use cases for this tool. One typical example of how I use Ivanti Neurons for UEM in my daily work is during the onboarding of a new employee. For instance, when an engineer in a country is hired, we receive a Windows laptop directly from the manufacturer, and when they turn it on and connect to the internet, Windows Autopilot enrolls the device into Ivanti Neurons for UEM automatically. Ivanti Neurons for UEM applies various security policies, such as defender and password rules, installs all required applications such as MS 365, Teams, and Slack, and configures the Wi-Fi and VPN profiler while verifying compliance before granting access to corporate resources. This onboarding example is just one scenario; as I mentioned before, we have more than 20 different use cases. On a scale of one to ten, I would rate Ivanti Neurons for UEM an eight.

My main use case for Ivanti Neurons for UEM is processing incidents and implementing changes for documentation and fixing IT problems that occur during the day. A recent incident I handled involved a server file that was completely full with no remaining storage. I had to free up storage space to resolve the issue. Daily operational issues include managing file storage size and restarting services when they go down. I receive tickets automatically, process them, and close them. We use Ivanti Neurons for UEM across our entire IT company and department. We also have a dashboard that shows all organizational units of the IT department, displaying how many tickets, incidents, changes, and requests each has, how many are closed, and how many are pending.

As a threat hunter, I have integrated Ivanti Neurons for UEM for our clients, and I have been working with it for around one year and eight months. I rely on Ivanti Neurons for UEM primarily for centralized device management and policy enforcement. We can also handle asset inventory, automation, security, and compliance. A common part of my daily routine is using Ivanti Neurons for UEM to verify that managed endpoints are compliant with our organization policies. If a Windows laptop is missing or requires a security configuration such as BitLocker not being enabled or an outdated antivirus version, the device is automatically flagged as non-compliant. I can review the device status from the console, trigger the necessary remediation actions, and confirm once the endpoint returns to a compliant state. The centralized visibility helps us reduce manual effort and ensures the device consistently meets our security baseline. Beyond routine day-to-day tasks, I primarily use Ivanti Neurons for UEM to monitor endpoint compliance, verify device health, check software and patch status, and help troubleshoot managed endpoints. Having everything centralized saves time and makes it easier to maintain a consistent security posture across the environment.

My primary use case for Ivanti Neurons for UEM is centralized endpoint management in our environment. I use it to monitor and manage laptops, desktops, and mobile devices from a single console, handling tasks such as software deployment. My day-to-day responsibility is centralized endpoint management. I use Ivanti Neurons for UEM to handle critical patch updates for multiple endpoints by identifying devices with missing security patches from the dashboard, creating a deployment job, and pushing updates to affected systems. Ivanti Neurons for UEM helps me track compliance and quickly troubleshoot any failed installations from the console.

I use Ivanti Neurons for UEM for mobile device management, and I can describe the use case. The remote device management feature has helped our remote work strategy because manual intervention is not needed, allowing us to have real-time insights, policy enforcement, and strong security with patch management.