TrustRadius Insights for Microsoft Intune are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Simplified Device Rollout: Users have praised Microsoft Endpoint Manager for simplifying the rollout of devices, enabling inventory management and simultaneous patching and application deployment to multiple devices efficiently. They find this feature especially valuable in large-scale deployments where managing numerous devices is crucial.
Effective Patch Management: Reviewers appreciate the ability of Microsoft Endpoint Manager to speed up patch and software deployment across all endpoints, allowing for easy package creation and distribution throughout the environment. This streamlined process has helped users keep their systems updated promptly and consistently.
Streamlined Policy Management: Customers find the policy management, application deployment, and cloud management features of Microsoft Endpoint Manager beneficial for effective device management and security purposes. The centralized approach to managing policies has improved operational efficiency for many users.
We use Microsoft Intune to manage our Windows, Android, iOS, and macOS devices. It provides a single admin console for all device types, ensuring they stay compliant with our configurations and app requirements. Additionally, Microsoft Intune gives us a streamlined way to deploy apps and configure device settings. We've also intgrated Windows Autopilot, Apple Business Manger, and Android enterprise to make onboarding new devices easy.
Pros
Deploy device settings and policies
Deploy apps and app settings
Checks device compliance
Streamlines onboarding of devices
Deploy device update policies
Cons
It should integrate with BeyondTrust and other remote access tools, not just TeamViewer.
App deployments should have a pre-install script option, not just requirement script options.
Sync now doesn't always update everything, should be an easy way to push and app, script, or settings instantly so you don't have to wait 24 hours
Likelihood to Recommend
It's the best tool to have for managing many devices with multiple os types, especially if you're already using MS Office products. I recommend bypassing hybrid join and opting for Entra ID joined instead. Once devices are enrolled, you'll be able to manage them remotely, ensuring seamless off-site management.
VU
Verified User
General Manager in Information Technology (51-200 employees)
We use it for mobile device management, mobile application management, Mac OS management, and Windows 10 management. I have also converted GPO to Intune Policies for Windows 10 devices. The Bitlocker key is also being managed by Intune. I set up the company portal for self-services application installs.
Pros
Software deployment.
Device wipe.
Cons
Reporting.
User notification for patching/rebooting.
Likelihood to Recommend
It is well suited if you are an Office 365 shop. The ecosystem and security cannot be matched. Securing data and DLP is built-in or works together. It is a really cost-effective solution for MDM, MAM, and endpoint management.
VU
Verified User
Director in Information Technology (51-200 employees)
Currently, we're using Microsoft System Center Configuration Manager to manage all our Windows assets, from PCs to laptops. Considering we use it across all organization, and we have a dozen of remote sites, some of them with distribution points, I can safely say that we solve basically 2 big business problem: We can manage all of those assets from a single pane of glass, delivering software with software-central feature, managing and keeping a eye on the status of those updates and also saving bandwidth at the same time, because we can deploy those software and updates from that distribution point, avoiding to have every single PC/laptop to download from the Internet itself.
Pros
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.
Cons
The licenses can be expensive if you are a small organization. Make sure you have a good deal with your Microsoft partner.
Deal with collections can be a little hard sometimes. Collections are the say the product classify or organize the groups. As the concept is a little different from what we're used to, like Active Directory Organizational Units or Security Groups, etc., it's best if you spend some time studying this before you deploy the product in your organization, especially if your organization has severy business or business units and remote sites.
You don't have as much product specialists as you have for other Microsoft products like MS Exchange, for example. So, make sure you hire a partner that have the skills needed to help you during the deploy of the product. Indeed, it is a complex product and it demands attention to details to avoid frustration in the future. People tend to save money on the implementation phase and that leads to frustration and, in some cases, projects cancellation due to underestimation of the requirements of the product.
Likelihood to Recommend
Seems obvious, but if your organization's assets are all based on Microsoft Windows, this is the right product for you. If you have mixed environments, with most of the computers running Linux or Mac, I don't think you'll have the same results. Unfortunately, I can't say much about that, because my experience is only based on a full Windows environment, and honestly, I didn't waste to much time paying attention to other operating systems.
We use Microsoft System Center Configuration Manager (SCCM) globally across over 40 countries and over 15000 clients on Windows Operating Systems. It is our enterprise software deployment solution as well as software management for enterprise wide desktops and servers. We have previously used WSUS and Altaris but SCCM allowed us to combine them into a single seamless platform providing us with much greater scalability as well as better reporting of software deployment and management status.
Pros
Consistent deployment of software across the enterprise with coherent reporting tools for better management of software and patching delivery.
Highly scale-able for large enterprises and/or geographically dispersed organizations.
Great value added for large Microsoft-centric organizations that heavily leverage Microsoft systems and software.
Minimal administration required to maintain the system over the years once deployed despite the complexity of initial setup.
Cons
Complexity of initial deployment requires 6 to 8 months of planning and preparation. This is one of those projects that will take a year to implement.
Managing user roles in the system can be made easier with use of templates and a more robust role management tool.
System and agent upgrades as well as patching the SCCM back-end systems should be easier.
Offer a hybrid cloud-based solution with pre-built models and templates for faster deployment and appeal to mid-size enterprises.
Likelihood to Recommend
SCCM is great for large global organizations with over 10,000 devices to manage or more. It is an excellent choice for a Microsoft-centric environment and pretty much the gold standard to for software deployment and patch management for Microsoft operating system devices. If you have a more mixed environment with Linux and Mac OS X, you may want to look at Altiris or WSUS, but keep in mind those products are less scalable.
VU
Verified User
Administrator in Information Technology (10,001+ employees)
We are currently using SCCM across our entire company for software distribution, update/patching of workstations & servers, compliance settings for various items as well as reporting. It allows us to ensure our software and operating systems are up to date as well as ensures we are meeting certain requirements for baseline configurations.
Pros
Operating system deployments via SCCM are fantastic. They allow for robust settings in various formats and allows us to easily deploy new computers.
OS patching made easy. The patching process for our environment is a breeze when using SCCM. We're able to easily roll out patches to test environments and subsequently apply them to production
Software Deployments. There are so many options for deploying software that it's hard to find a replacement for SCCM. The ability to deploy to a user or computer is a wonderful feature. Not to mention having the ability to create a catalog where users can request/get software as needed.
Cons
Currently, we have no complaints with regards to SCCM.
Likelihood to Recommend
The features and benefits of using SCCM are too hard to describe in detail but at a high-level overview the reporting, inventory, patching, management, and software/OSD options make this a wonderful investment. With regards to reporting, specifically finding out all hardware information for a group of computers, is vital to operations when planning for hardware refresh cycles. And having the ability to PXE boot a computer, give it a name, start the imaging process, and have it complete all the steps on its own saves hours of time.
VU
Verified User
Administrator in Information Technology (201-500 employees)
Across all of IT, SCCM is used for deployment of software as well as Windows patching. It is used for both server patches as well as workstation patches—both laptop and desktop—on a monthly basis. It handles the patch process much more efficiently than its predecessor here—WSUS.
Pros
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.
Cons
It takes time to implement SCCM. Take advantage of an integration company whenever possible.
Its capabilities are broad and can go so deep that it takes a while to understand just a portion of it. Get training whenever possible.
Reporting is useful but could be expanded to more of a Power BI capability.
Likelihood to Recommend
Microsoft System Center Configuration Manager is great for companies of all sizes, national or international. Its scalability and pinpoint accuracy can be used in all scenarios. However, use downstream servers as distribution points to save on bandwidth and ensure timely updates and easier deployment of individual software packages.
VU
Verified User
Engineer in Information Technology (1001-5000 employees)
We are a relatively small/medium company. I was fortunate enough to have enough influence to convince them to allow me to buy the Data Center version of both SCCM and SCOM. Having said that, we utilize SCCM within our IT Department to manage our IT inventory as well as push out critical updates and patches to our Microsoft Windows devices. Additionally, we utilize SCCM to track software licensing and usage across our organization. It has been a powerful tool for us as a company to enable not only the resource management functions, but leveraging the System Center Endpoint Protection (SCEP) product enables us to manage and take advantage Microsoft built in security products. The reporting is an extremely flexible and powerful tool that enables us to quickly visualize our inventory and assist with technology refreshes and forecasting our upgrades.
Pros
System Center Endpoint Protection (SCEP) product enables you to manage and take advantage Microsoft built in security products. Very simple to configure and maintain.
Track software licensing and usage across your organization.
Managing the ageing of our equipment and plan technical refreshes. Through reporting you can easily visualize your inventory and see basically any information needed to make informed decisions.
Cons
Configuration and setup of SCCM can be quite challenging if you have never performed this. Microsoft has very good documentation on this function and can guide a seasoned IT professional through the process.
Keeping SCCM up to date can be challenging and I believe that this is a major opportunity for an area of improvement.
There is a right-click tool kit that is separate that Microsoft should include in the console. Once you use them, you will understand why.
Likelihood to Recommend
While there are other products that can perform functions that SCCM provides, I would still recommend SCCM due to the vast array of features that it provides IT professionals. Most great products that I have used require some configuration to ensure they are a useful tool that we as administrators and managers can utilize to extract data relating to our environment. SCCM can do just that.
SCCM allows us to manage and deploy machines on our network. This is a nice tool to have in order to centralize things for updates and deployment. We also use this for imagining new computers as they come in from Dell. We use it across the whole organization to manage the systems on the network.
Pros
Image computers from a standpoint of having everything in a centralized location for deployment
Deployment control of updates managed by IT system admins
Overall Management of computers in the network
Cons
Deploying Software seems to be a challenge and has a low rate of success when pushing through SCCM
Imaging can be cumbersome and depend on updates and current status of the machine there can be many roadblocks in the imaging process adding several hours to the process. It also takes a decent amount of time to keep the image up to date with current standards.
Having the machine join as a client does not work consistently. Have to manually check each machine after the image to ensure that this task has been completed successfully.
Likelihood to Recommend
The whole idea of SCCM is great. Just wish that the features that it has actually work seamlessly. It seems we are always having systems fall off from being a client and/or they are not able to be updated. I am yet to have any success in deploying software and having it actually make it to the host machine.
