Filter Ratings and Reviews
Filter 175 vetted Microsoft Endpoint Manager (Microsoft Intune + SCCM) reviews and ratings
Reviews (1-25 of 39)
Companies can't remove reviews or game the system. Here's why.
We are in the process of transitioning from Group Policy over to Microsoft Endpoint Manager. We are using it for controlling our policies and setting up our standard operating environment. as well as application deployment. It allows us to standardize what we are doing and automate IT functions, freeing up valuable resources to be better spent elsewhere.
- Policy Management
- Application Deployment
- Cloud Management
- Pricing
- Steep Learning Curve
January 22, 2021
We use MS Intune and SCCM with our Azure cloud solution for all of our offices.
It is great tools to control and monitoring our security, servers and applications.
Manage mobile devices is highly important now days, so now we can manage our phones and tablets in modern way with modern approach.
It is great tools to control and monitoring our security, servers and applications.
Manage mobile devices is highly important now days, so now we can manage our phones and tablets in modern way with modern approach.
- 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
- Reporting should be improved
- Better integration with AV software
- AI integration with alert notification about unusual user behavior
September 24, 2020
Microsoft Intune is used to provide corporate data access via email app and other mobile apps on the mobile device of an employee. Intune enables the use of a personal mobile device to access emails and other official data in a secure environment where the IT team has full control over the flow of information. It is used throughout the organization where employees are eligible for email access via mobile. The business does not have to worry about data leakage and it provide 24/7 access to emails to employees.
- 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.
- Dashboard customization can be improved.
- Privacy between personal and office data as i don't want that my company control my phone.
- Location service could be improved.
- Enhanced security and integration with other apps.
February 18, 2020
We use it for monthly Windows updates, image deployment to workstations, server and application deployment. It's being used in all departments to:
- Quickly patch/deploy applications all laptops, desktops.
- Push down new, updated Windows 10 OS versions.
- OS imaging and deployment via BOOTP across various locations through North America
- Patch management across various locations through North America
- Easier to find where something is inside the application.
- Faster results after patching has been completed, and it takes hours some time to see if a server was patched or something failed to install.
January 25, 2020
We use SCCM for application and Windows desktop, laptop, and server patching. We accompany it with the PatchMyPC addons, so we can update the majority of applications we use for end-users.
We also use it to deploy security software.
We also use it to deploy security software.
- 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.
- Reporting: The SQL Reporting Services oriented user-interface is really not particularly user-friendly.
- Inventory: The inventory function is overly basic and difficult to search. If this were improved to be a legitimate asset management tool, it would tremendously increase the value of SCCM to organizations.
October 18, 2019
It is used by two departments, enterprise services (e.g Infrastructure Administration, Email, Sharepoint, etc) and Help Desk.
- 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.
- Driver portals for different PC/Laptop manufactures.
- There is no dashboard for the executive summary of the organisation's patch levels.
- Being able to see the downloaded patches (labeled with KB numbers) according to their names on the SCCM server.
August 31, 2019
SCCM is used across our entire organization. We use it for zero-day remediations, as well as large scale package deployments. It saves the company an immense amount of hours wasted for on-site support team members having to manually install packages. We can also pull reports of software versions across our environment and deploy patches accordingly for any PC that's out of compliance.
- 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.
- Building a collection and deployment takes some time to learn. It isn't very user intuitive.
- Getting up to date reports on a deployment isn't a one-click process. It requires triggering multiple events and waiting about 10-15 minutes
- I wish there was a dashboard feature built into SCCM. I manage the JAMF platform in my environment as well, and this is one of the key features I rely on every day. When I need to pull a report in System Center Configuration Manager it is just clunky.
July 29, 2019
We use SCCM for a number of different use cases including imaging, OS and software deployments, inventory and desktop management. Its primary function is to push new software to the fleet. The benefit is being able to time when and what gets deployed and make it done in an automated fashion. We also use it to manage to patch existing software packages (in conjunction with a product called Ninite).
- 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.
- Its mac integrations, though improving, are really not much more than inventory.
- It could benefit from an enterprise remote control solution more similar to Bomgar or LogMeIn.
- Its web interface for reporting is very dated.
November 23, 2019
It is being used both across the whole organization and at the department levels. It is centrally managed by the main IT group in the organization, and then individual departments have their own instance of SCCM to be able to use to manage resources/deploy software, etc. It addresses the business problem of having a central Systems Management solution that can pretty much do most everything, including managing all hardware endpoints, managing software, monitoring, asset management, managing antimalware and firewall policies, etc. in an organization.
- 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.
- The program itself can be challenging to use, especially if there hasn't been any formal training on the use of the product. Either training/reviewing documentation is recommended prior to using SCCM.
- At times, it can be difficult to try and find out why a certain machine that's listed in SCCM says that the endpoint has the SCCM client and shows as Active, but in fact, it's not. It's also difficult at times to try and figure out why the client can't be pushed down to the endpoint.
- Even though the remote assistance features in SCCM are really good, it can be challenging at times when the remote options don't work for a particular endpoint, even though the machine is active, online, etc.
August 02, 2019
System Center Configuration Manager was used as a solution for OS deployment, remote troubleshooting, and patch management for Windows PCs in our organization. The plan was to use it to manage close to a thousand PCs in total. As the product required an excessive number of man-hours to implement and support, its use was dropped after a year, and an alternative selected. The main goal was to improve OS deployment and replace WDS.
- 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.
- Installation is very laborious and complicated. The number of things to manually configure during the installation is incredible.
- OS deployment is hard to configure and troubleshoot. The Microsoft article on deploying Windows 10 via System Center Configuration Manager in a test environment takes 44 minutes to read (Microsoft's estimate, not mine -- check here: https://docs.microsoft.com/en-us/windows/deployment/windows-10-poc-sc-config-mgr). If something goes wrong, there are multiple log locations to check on both the server and client, making troubleshooting difficult.
- The management console looks old, and its performance isn't great. It is often hard to find settings in the console, and it refreshes slowly. The old name for System Center Configuration Manager, SMS, comes to mind often. "Slowly Moving Software."
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.
- Software deployment.
- Device wipe.
- Reporting.
- User notification for patching/rebooting.
November 21, 2019
We needed to deploy a point of sale on mobile devices and we wanted to have a clear control over what the device could do, so we looked for an MDM.
- Enrollment process.
- Application deployment.
- Many security features.
- VPN deployment.
- Device searches.
- In the tagging of devices by project.
July 23, 2019
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.
- 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.
- 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.
March 14, 2019
At my current and previous companies, I have used System Center Configuration Manager as one of the main tools to manage my IT infrastructure. From simple management of active directory users and computers to detailed inventorying of windows equipment (computers and server), software inventorying, software deployments and patch management. Also, it is used as a main endpoint protection solution that includes centrally managed Windows Defender and ATP. We use System Center Configuration Manager as one of the main monitoring tools to get reports of the Windows patching state, device availability and activity, to get information about what PCs users are using at a current time. Using as the only solution to capture and image new and existing workstations and servers. And, also SCCM is the main remote control/assistance tool for our help desk department.
- We have mostly Windows environments, so SCCM provides us tons of monitoring options for computers and servers.
- SCCM saves a lot of time and money for our Help Desk team to provide remote assistance to end users.
- In a Windows 10 environment, SCCM provides pretty decent endpoint protection.
- Patch management: tons of options of management, deployment, and monitoring.
- Systems Imaging: deploying images to new PCs or servers, reimaging existed environment.
- And of course, systems inventorying (hardware and software).
- Initial configuration is pretty much complex and requires some additional time for preparation and deployment.
- It would be awesome to have Patch management and endpoint security be moved to separate tabs in the SCCM management console.
- Imaging functionality is great but over-complicated, and sometimes simple processes take way longer compared to regular WDS services.
- Better reporting and monitoring services with customized charts.
- Better integration of SCCM patching services with Windows Updates services on Windows 10. Sometimes it is almost impossible to say if patches were installed on Windows 10 via SCCM deployment until you get that information within SCCM management console.
- Requires a lot of learning about the product for IT personnel.
March 07, 2019
My former company used System Center Configuration Manager for software deployment, Imaging, and Microsoft updates. It was used across the entire enterprise, but my department only used it for imaging and application deployment. Before SCCM we were using Landesk, which I preferred greatly. That being said, SCCM does work well, as long as it is configured correctly. I would recommend it, but it would not be my first choice for deployment or imaging software.
- Imaging from PXE boot, and it can be configured for remote imaging. Any IT department that has ever imaged 100 or more workstations with a CD and external drive knows that this is a strength.
- Application deployment. Sccm can be configured with a software store where end users can install the software they need.
- Update deployment, updates can be deployed on a set schedule with SCCM.
- Imaging. I know that I gave this as a plus, but this is also a drawback too. Images take much longer to deploy via SCCM than they do with FOG or Landesk.
- The system itself is a huge learning curve and takes a great deal of configuration to make it work correctly.
- Remote Desktop Tool -- Microsoft already has a remote desktop tool, so why include almost the exact same one in your VERY expensive management suite?
March 20, 2019
System Center Configuration Manager (SCCM)is being used across the whole organization on all of our Windows computers and our dual booted Mac computers. SCCM addresses the problem of having to have more employees to be available for hands on installing and updating any software that SCCM allows the user to do without another employee finding time to do it for them.
- 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.
- SCCM takes a long time to install once a computer has been reimaged and sometimes it fails.
- When the SCCM server goes down, no one is able to install anything and causes staff to be frustrated.
- There isn't a communication tool that tells users that new software has finished installing. Staff have to keep checking for software they requested to be installed to verify it was installed.
February 01, 2019
I use this tool to connect with my team remotely, and it has allowed us to have all the necessary information in an organized way and to have the documents ready to share quickly and safely. This harnessing has allowed me to build a real and very useful database, and allows me to establish service level objectives, review them, and generate associated reports.
In general, it has allowed me to automate some processes associated with personnel management.
In general, it has allowed me to automate some processes associated with personnel management.
- It allows me to increase the response capacity to the requirements of the users to keep the information organized and accessible.
- It allows me to build a really reliable database.
- It allows me to automate processes and establish a single point of contact per user.
- It is a very good tool to generate follow-up reports.
- It is not an easy tool to use, it has many functions and tends to confuse the naked eye.
- The implementation is a bit slow.
July 25, 2019
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.
- 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.
- 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.
March 18, 2019
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.
- 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.
- 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.
February 28, 2019
Microsoft System Center Configuration Manager is used by our IT Operations department to create, deploy software packages for homegrown applications, commonly used software and windows update on desktop, laptops, and servers. It provides IT Asset Management capabilities as well as software inventory and auditing. The remote control feature is used by PC support for remote access and support solution.
- Managing Windows Environments for patching, software deployment, and Inventory.
- Automation of software deployment.
- Imaging of devices.
- Asset reporting.
- The SCCM console is a bit outdated. Needs an improvement.
- Better reporting, we have to rely on other monitoring tools for software and hardware inventory.
- Configuration and setup of SCCM can be quite challenging if you have never performed this.
June 19, 2019
Microsoft System Center Configuration Manager is used for imaging our computers, but it is also used to deploy policies and software packages to specific users or groups.
By utilizing Microsoft System Center Configuration Manager, the IT admins spend less time manually installing applications for our end users. It allows us to centrally manage what is being deployed to the computers in our environment and run reports on the computers and what is installed on them.
By utilizing Microsoft System Center Configuration Manager, the IT admins spend less time manually installing applications for our end users. It allows us to centrally manage what is being deployed to the computers in our environment and run reports on the computers and what is installed on them.
- 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.
- Microsoft System Center Configuration Manager does take a lot of time to learn and manage. There are a lot of bits and pieces to keep up to date (software packages, drivers, OS builds, computer model packages). It is not something that you can easily pickup and start configuring. And with automation, making a mistake can cause the scripts to take days instead of hours.
- There are frequently update failures. I understand many of these are configuration problems on our end or that the state of the computer is such that the updates cannot be pushed to it. But I feel like it happens a bit much.
February 01, 2019
Our organization is basically using SCCM to deploy some applications remotely, keep a record of each machine we have deployed to users, which is a must have to any organization and also for patching endpoint computers. This last feature would be perfect if it worked consistently, but there are a few complaints.
- Software deployment - SCCM allow you to silently deploy software to your users without leaving your desk.
- You can keep track of each machine you deployed.
- Even though is not perfect, the patching feature is still very helpful.
- Patching with SCCM is now 100% guaranteed. Sometimes it gets stuck with some patches, other times the patches simply won't show up, but this is just for approximately 10-20% of the devices.
- For some other features, they could make the path more straight forward, sometimes you need to spend some time in order to find what you want.
- Sometimes it takes longer for the software you deploy to show up to the user's machine, but that is not an issue, it's kind of 1 in 50 deployments and it just takes a little more time but works.
May 01, 2019
It is very effective for simple tasks such as pushing out Windows updates, Defender updates, and a large array of other software. We have also started using it for servicing Windows 10 computers. With the modern life cycle of Windows 10 being more aggressive then past versions, it has been extremely handy to use Windows 10 servicing to keep our computers running the latest builds of Windows 10.
- Windows 10 servicing.
- Endpoint protection policies and updates.
- Reporting.
- Surface Driver updates seem flaky.
- Sometimes needs some TLC to keep Microsoft SCCM and WSUS happy.
- Menu structure sometimes gets a little confusing.
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.
- 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.
- Currently, we have no complaints with regards to SCCM.
February 22, 2019
Excellent tool for centralized and standardized configurations and software distribution. This tool is based on AD authentication like the rest of the Microsoft products and makes sending enterprise-wide updates automatically or manually a breeze. Metered usage for software, as well as built-in reporting, is excellent as well. Due to the popularity of the tool, there are enough resources online to get help on most issues.
- We are using it for software distribution.
- AD based user access.
- Web-based.
- Allow custom icons.
- Reboot notifications.
- Better reporting.
Microsoft Endpoint Manager (Microsoft Intune + SCCM) Scorecard Summary
What is Microsoft Endpoint Manager (Microsoft Intune + SCCM)?
Microsoft Endpoint Manager, combining the capabilities of the former Microsoft System Center Configuration Manager, SCCM or ConfigMgr with the mobile device management application Microsoft Intune, is presented as a unified endpoint management option.
The former Microsoft Intune is an endpoint management solution for mobile devices, an MDM solution that allows the user to securely manage iOS, Android, Windows, and macOS devices with a single endpoint management solution.
The component Endpoint Configuration Manager (the former SCCM) is a system monitoring and management platform that can be deployed as an agent, via the cloud, or on-premises. It can manage systems across OS types (Windows, Mac, Linux), as well as multiple environments, including servers, virtual environments, and mobile devices from a single management console, and supports scaling capabilities, such as future application delivery.
The former Microsoft Intune is an endpoint management solution for mobile devices, an MDM solution that allows the user to securely manage iOS, Android, Windows, and macOS devices with a single endpoint management solution.
The component Endpoint Configuration Manager (the former SCCM) is a system monitoring and management platform that can be deployed as an agent, via the cloud, or on-premises. It can manage systems across OS types (Windows, Mac, Linux), as well as multiple environments, including servers, virtual environments, and mobile devices from a single management console, and supports scaling capabilities, such as future application delivery.
The platform includes a customizable reporting tool to inform future business software decisions. It also enables endpoint protection from malware and vulnerability identification within the monitored systems and infrastructure.
Microsoft Endpoint Manager (Microsoft Intune + SCCM) Integrations
Microsoft Endpoint Manager (Microsoft Intune + SCCM) Pricing
- Does not have featureFree Trial Available?No
- Does not have featureFree or Freemium Version Available?No
- Does not have featurePremium Consulting/Integration Services Available?No
- Entry-level set up fee?No
| Edition | Pricing Details | Terms |
|---|---|---|
| Microsoft 365 For Families | 9.99 | per month |
| Microsoft 365 For Individuals | 6.99 | per month |
| Microsoft 365 Business Basic | $5 | per user/per month |
| Microsoft 365 Business Standard | 12.50 | per user/per month |
| Microsoft 365 Business Premium | $15 | per user/per month |
| Microsoft 365 Apps | 8.25 | per user/per month |
Microsoft Endpoint Manager (Microsoft Intune + SCCM) Technical Details
| Deployment Types: | On-premise |
|---|---|
| Operating Systems: | Windows |
| Mobile Application: | No |