Pros and Cons of Microsoft Intune 2024 (2024)

Easy to use.

Inventory management.

Policy enforcement

Device Tracking

Imaging

Continuous updates add new functionality

Setup application protection for office 365 apps

protects corporate data

allows a device to be split in to corporate data and personal data

Windows Autopilot

Integrates well with Apple devices

Good tech support

Runs in the cloud there is no need to put up an on-premises server

Mobile device management

Device policies

DLP

Simplify rollout of devices

Inventory thousands of devices and users

Apply patches and applications to multiple devices at once

Able to create Compliance Policies and Configuration Profiles

Configure Windows Update settings

Configure Endpoint security settings and Windows Defender Antivirus

Create App Protection and Configuration Policies

SCCM imaging can't be beat

Intune application deployment and WSUS ensures that devices are getting updates and applications, especially in WFH scenarios

The upgraded interface is much easier to work with than older SCCM iterations (2007 and below)

[Microsoft Endpoint Manager (Microsoft Intune + SCCM)] helps to speed up the deployment of patches/software throughout our environment. I can easily build a package and then deploy across all endpoints.

The ability to supercede software is also quite handy. This automates the removal of old versions and replacing them with newer versions.

The Intune Autopilot option is very useful if you want to deploy software to devices straight out of the box. You can configure them to download software when a user opens a new PC and turns it on for the first time.

Policy Management

Application Deployment

Cloud Management

We can add and assign mobile apps to user groups and devices

Manage access on personal devices by restricting actions users can do or not

Wipe or removing organization data from apps

Device management.

Complete control over the flow of information on the mobile device.

Allows secure data access on BYOD.

Compliance and policy enforcement on the Office apps in mobile.

Windows and Office patching: SCCM does this really well. It is efficient, reliable, and easy to schedule. It's quite simple to keep machines updated once they've been registered.

Application Deployment: SCCM very effectively deploys application and application updates. We use it very effectively to reinstall our security software if it gets uninstalled or needs to be updated.

Software deployment.

Device wipe.

It has nice GUI's built-in for many of the functions throughout the program. This helps to make it easier for the IT Administrator to be able to utilize certain features/functions when using SCCM.

It doesn't use a lot of system resources when running, or even if left open on the server. This is good, as it enables those that work with the program to still be productive with being able to run other programs/software on the server.

It has really good remote assistance options built-in. This is particularly helpful for the IT Admin being able to assist end-users over a remote session or to remotely connect to computers. This is also a benefit for organizations that don't have a commercial remote assistance product in place.

Enrollment process.

Application deployment.

Many security features.

Patching lots of computers (in my case 400+) without leaving your seat!! Less administrative overheads.

Deploying new machines with a standard image that is the same across the organisation and no one has a different set of image and therefore consistancy within the organsation.

Provide a comprehensive inventory of the organisation's computer assets.

Provide security auditors with patching compliance reports within the organisation.

It allows users to install packages from a Self-servicing application via an app called Software Center.

It allows for fast remediation of vulnerabilities across your organization.

Provides reports for high-level visibility of your environment for upper management.

Remote Control works well and does not require a lot of configuration. It must be understood that the Remote Control feature of System Center Configuration Manager is different from RDP, as it does not establish a separate user session and allows a tech to troubleshoot issues in a way visible to a user.

It is easy to add client devices for management, and multiple options are available (push, Active Directory, etc.)

It's modular and extensible. For example, a third-party company, Parallels, makes a System Center Configuration Manager plugin to manage Macs from the same console.

You are able to create queries to identify almost any combination of computers needed.

Its direct tie to active directory.

It fully leverages Windows functionality.

It's easy to group machines into separate categories, such as servers and workstations, or more in-depth categories, such as location X workstations and location Y servers, to easily target them for patches.

Sending software to a workstation through SCCM is simple!

Patching can be handled with bandwidth restrictions in mind, letting only X% of the wire be used for patching and even allowing the patches to go to a specific downstream server at a location to let all local workstations leech from there instead of the web or WAN.

You can run an inventory of your assets, from PCs to laptops, grouping them by location, type, department, all tight to your own Active Directory. That saves a lot of time when you need to report the status of hardware and software. You can even manage alerts to inform you when some hardware change has happened, which could possibly lead to a robbery.

You can centralize software distribution, controlling what kind of software is available for your organization, and here's the most important part: you can give end-users the power to install/remove that software by themselves. That way, you can avoid a ticket to your service desk and potentially save money on those tickets too.

Also, due to the distributed architecture of the product, you can deploy a component of the system in each remote site you have. Thanks to that, you can avoid using the bandwidth of the remote site, which usually is already limited, to download software/updates to each PC locally. You just need to download once for the distribution point it will deliver locally. You can also avoid the risk of having your local WAN to be contested by some unexpected outdated PC that was just connected to your network.

Centrally managing applications, configuration settings and policies makes it easier to deploy. So when someone requests an application or is missing the application, I can jump on the Microsoft System Center Configuration Manager console and add them to the software deployment and generally within the hour, the application is installed on their computer. It can be manually forced to pull the change as well if you don't want to wait up to an hour.

Windows 10 servicing.

Endpoint protection policies and updates.

Reporting.

SCCM allows our administrator to push updates remotely and does not require our staff to do anything to install software/updates etc.

SCCM lets us control licenses to software by allowing our administrator to only push out software to staff members when requested instead of allowing all staff to choose software from a list. Prevents unauthorized usage of licenses to software.

SCCM allows periodic software updates to be scheduled even when our staff are not at their computers, because it does not require staff actions.