We changed our name from IT Central Station: Here's why

Microsoft Endpoint Configuration Manager OverviewUNIXBusinessApplication

Microsoft Endpoint Configuration Manager is #1 ranked solution in top Configuration Management tools, #1 ranked solution in top Patch Management tools, and #2 ranked solution in top Server Monitoring tools. PeerSpot users give Microsoft Endpoint Configuration Manager an average rating of 8 out of 10. Microsoft Endpoint Configuration Manager is most commonly compared to Red Hat Ansible Automation Platform: Microsoft Endpoint Configuration Manager vs Red Hat Ansible Automation Platform. Microsoft Endpoint Configuration Manager is popular among the large enterprise segment, accounting for 74% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 23% of all views.
What is Microsoft Endpoint Configuration Manager?

Microsoft Endpoint Configuration Manager (MECM, formerly SCCM or System Center Configuration Manager) is a software management suite that allows users to manage large numbers of Windows-based computers and servers.

Configuration Manager features software distribution, operating system deployment, remote control, network protection, security management, patch management, and hardware and software inventory, among other services. It allows you to set configuration and security policies, keep your software up-to-date, and monitor your system status while giving your employees access to corporate applications on whatever devices they choose.

Configuration Manager allows you to manage computers using macOS, Windows UNIX, or Linux, and mobile devices running iOS, Windows, or Android operating systems. It can be integrated with Microsoft Intune, allowing you to manage computers connected to a corporate network.

With Configuration Manager, you can manage PCs and servers, keeping software up-to-date, setting configuration and security policies, and monitoring system status while giving your employees access to corporate applications on the devices that they choose.

Benefits and Features

  • Proactively manage all device life cycles, starting from purchase all the way to retirement.
  • Automatically deploy software as well as printers to devices, using a common software library.
  • Deploy upgrades and patches to your operating system.
  • Ensure that all devices are patched, encrypted, and secured in compliance with security best practices.
  • Provide mobile device management functionality, which includes the ability to reboot and/or lock devices remotely.
  • Provide end users with “self-service” so that they can update machines when it is convenient for them.

Reviews from Real Users:

Users of MECM like that it is stable and flexible. Patching is one of its most useful features, although users cite many other features as useful as well. One user stated that "It does what you need it to do, and it's a one-stop-shop for the company and for all your deployments." Overall, “the entire solution, from end to end, is excellent.

Microsoft Endpoint Configuration Manager was previously known as System Center Configuration Manager, SCCM .

Microsoft Endpoint Configuration Manager Buyer's Guide

Download the Microsoft Endpoint Configuration Manager Buyer's Guide including reviews and more. Updated: January 2022

Microsoft Endpoint Configuration Manager Customers

Bank Alfalah Ltd., Wªrth Handelsges.m.b.H, Dimension Data, Japan Business Systems, St. Lucie County Public Schools, MISC Berhad

Microsoft Endpoint Configuration Manager Video

Microsoft Endpoint Configuration Manager Pricing Advice

What users are saying about Microsoft Endpoint Configuration Manager pricing:
  • "Its licensing is quite complicated because we are getting the license not only for SCCM but for the full Microsoft package. We don't need to pay for a separate license. We need to have one license that includes everything we need, such as Windows, Microsoft 365, SCCM, encryption, and so on. So, we don't have a specific price for it. Perhaps, it is good that it includes the full suite of licensing of Microsoft. It is expensive, but we are getting a lot of features."
  • "The price model is different for every client."
  • Microsoft Endpoint Configuration Manager Reviews

    Filter by:
    Filter Reviews
    Industry
    Loading...
    Filter Unavailable
    Company Size
    Loading...
    Filter Unavailable
    Job Level
    Loading...
    Filter Unavailable
    Rating
    Loading...
    Filter Unavailable
    Considered
    Loading...
    Filter Unavailable
    Order by:
    Loading...
    • Date
    • Highest Rating
    • Lowest Rating
    • Review Length
    Search:
    Showingreviews based on the current filters. Reset all filters
    Sumit Dubey
    Technical Lead at HCL Technology
    Real User
    Top 20
    A stable systems management software product with useful package deployment and application deployment features
    Pros and Cons
    • "The major features of this product are the reporting tools. The most valuable features are package deployment and application deployment. Security management is also good because any vulnerability will be identified, and you can fix it. It's the best tool because you never know what kind of client you will have. For example, you may have your offices in low bandwidth remote areas. But it's achievable because it accommodates the bandwidth that you have available. Microsoft Endpoint Configuration Manager is an excellent reporting tool for your environment. If you want to know the details about the hardware configuration, software configuration, what is causing a problem, or when a new feature update comes in for Windows, even that goes on SCCM itself. A lot of deployment stuff."
    • "It would be better if reporting were more user-friendly. I would like to see an upgrade in the reporting structure in the next release. At the moment, you have to use an SQL query or configure it to pull reports through the graphical user interface. Their updates could be more regular. I think Mircosoft updates it every six months. They are also moving many things to Intune, and Microsoft decided to move the deployment solution there. I think SCCM is getting old, and Intune is new."

    What is our primary use case?

    We use Microsoft Endpoint Configuration Manager for application deployment, patch deployment, and many other things. If you have any script that needs to be deployed to all the devices, you can do it with this solution. 

    How has it helped my organization?

    If you have this solution in your environment, it's a win-win situation. You can deliver anything that the customer requires. If the efficacy is somewhere around 80 to 90%, everything isn't well because some devices aren't coming online because of bandwidth issues or they aren't compliant. 

    However, if we have 80% to 90% efficacy, we can achieve compliance. The compliance we reached was around 95%, but that 5% was probably due to a decommissioned device or one that wasn't in the environment. So, for efficacy, delivery, and reporting, this is one of the best tools.

    What is most valuable?

    The major features of this product are the reporting tools. The most valuable features are package deployment and application deployment. Security management is also good because any vulnerability will be identified, and you can fix it. It's the best tool because you never know what kind of client you will have. For example, you may have your offices in low bandwidth remote areas. But it's achievable because it accommodates the bandwidth that you have available.

    Microsoft Endpoint Configuration Manager is an excellent reporting tool for your environment. If you want to know the details about the hardware configuration, software configuration, what is causing a problem, or when a new feature update comes in for Windows, even that goes on SCCM itself. A lot of deployment stuff.

    What needs improvement?

    It would be better if reporting were more user-friendly. I would like to see an upgrade in the reporting structure in the next release. At the moment, you have to use an SQL query or configure it to pull reports through the graphical user interface. 

    Their updates could be more regular. I think Mircosoft updates it every six months. They are also moving many things to Intune, and Microsoft decided to move the deployment solution there. I think SCCM is getting old, and Intune is new. 

    For how long have I used the solution?

    I have been working with Microsoft Endpoint Configuration Manager for about seven years.

    What do I think about the stability of the solution?

    Microsoft Endpoint Configuration Manager is very stable. It's very reliable, and it's a proven product.

    What do I think about the scalability of the solution?

    Scalability is difficult for the inexperienced. But if you know how to use these tools, scalability is also good. When Intune matures, you can also use it together with Microsoft Endpoint Configuration Manager to scale and co-manage the environment.

    How are customer service and support?

    Microsoft support is good, but it does take time. There are two types of support provided by Microsoft, paid and unpaid. The paid option offers a real-time system, and they help because we have to pay in dollars. Sometimes it takes two or three days to get to the submission. I cannot comment much because we only had a few cases and had to connect with them. Usually, these issues are related to some upgrades and some tool-related issues. Although it's good, I think Microsoft support could be better because they still take too much time.

    How was the initial setup?

    The deployment process is very simple. It's not difficult because it gives you a variety of features. You have to create a collection or a group, and you deploy it. It's very slow and dependent on the network. 

    A single person can install and deploy this solution. If you have an application already created and tested, that's fine. If you do not have one, then you have to build the application and test it. If everything goes fine, you can simply deploy it to the list of people you want to target. I wouldn't say that you need many people, but it depends on your operation and how you manage your environment.

    The deployment time depends on the location it's going to, the bandwidth, and more. You can configure a time for the application to replace the policy or when the machine will replace its policies in the configuration settings. Suppose I'm an administrator and deploying something on your device; your machine will not get turned on. I will go ahead and update the application evolution cycle and machine policies so that it happens automatically. Once the 30 minutes clock starts, it'll update, and once it refreshes, it will see something I sent, and it'll start downloading it. 

    Downloading is always completely dependent on how fast your internet is. Once the package is downloaded, you can simply go ahead and install it. Small packages will take about an hour at most to deploy. For bigger packages, it's completely dependent on the internet because this tool does only one job. It's like a postman as it takes one thing from you and gives it to the other person.

    There are periodic updates, and the maintenance is also done. The patch update service is critical and has a significant impact.

    What other advice do I have?

    Microsoft Endpoint Configuration Manager is suitable for small businesses. If you have fewer offices and fewer users, then the efficacy of this product is very high. If the company doesn't have a system for a long time or doesn't have many employees or environmental issues, they can open Intune and have a cloud-based solution and get all the features together there.

    You can stage your content, and you can share where you have no connectivity. You can go ahead and do the whole deployment and a lot of things. Intune is still improving, but SCCM has a feature of all this deployment and all other things.

    So I would say that SCCM has a stronghold and is still relevant. It's an excellent product, but Intune will take it over in a few years. But not entirely because they will coexist. They are working in an environment simultaneously, hand in hand, but I think the market will move more toward Intune (if it's not moving already).

    I would advise potential users to take a structural approach. They should know the customer's requirements, the number of users, and the locations. They need to have the setup, create a cache, and then binary and secondary options for these deployments. But if you're using a cloud-based solution, you don't have too much worry about it because everything will come from the internet. 

    On a scale from one to ten, I would give Microsoft Endpoint Configuration Manager an eight.

    Which deployment model are you using for this solution?

    Public Cloud
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Information Technology Lead at a construction company with 10,001+ employees
    Real User
    Top 20
    Works well with Windows, very stable, and can scale well
    Pros and Cons
    • "The main, clear valuable feature is updating the latest, patches and updates from Windows. This is the main feature we really utilize a lot."
    • "Devices like smartphones and tablets are managed very well on VMware, however, they are absent in SCCM. I could configure iPad from the VMware site and it was done very easily. It should be just as possible on SCCM."

    What is our primary use case?

    Our main use is, first of all, to update the patches and to push the patches from SCCM, to check systems software, and to see which software is installed along with the systems. These are the major three things that we use on SCCM. 

    We are on the endpoint side. We just ensure that the SCCM agent is installed appropriately. 

    I have an on-site server also. There are the primary servers, and then there are site servers of SCCM. I have a site server also. With the site server, I have to make sure it is working and there is no hardware level or any other issue on these machines. This site server is replicating with the main servers in our data center. 

    Due to the fact that we have different sites in different locations including the UAE, Oman, and other sites, there are other site servers, that are replicating with the main servers. They may be taking other information from SCCM as well.

    What is most valuable?

    The main, clear valuable feature is updating the latest patches, Software distribution, remote control and computer inventory. This is the main feature we really utilize a lot.

    What needs improvement?

    The main SCCM lacks some things, which they incorporated into Microsoft Intune. When I evaluated these two products, one from VMware Workspace One and one from Microsoft, I found that there is something missing in SCCM, which is available and works very well in VMware Workspace One. SCCM should work to add these features into their service offering.

    For example, devices like smartphones and tablets are managed very well on VMware Workspace One, however, they are absent in SCCM. I could configure the iPad from the VMware Workspace One cloud and it was done very easily. It should be just as possible on SCCM.

    For how long have I used the solution?

    I've been using the solution for three to four years.

    What do I think about the stability of the solution?

    It's constantly running alongside computers. When they are on, SCCM is on. It's a stable product. There aren't issues with it crashing or getting glitchy. There is no issue, we have not faced any issue with SCCM.

    What do I think about the scalability of the solution?

    Everyone in our organization uses SCCM, as it's on all of the device endpoints. There are two to three people that have access to the SCCM  servers. 

    The scalability is very easy. If a company needs to expand it to more endpoints they can do so easily.

    How are customer service and technical support?

    Initially, when we were installing the agent originally, we did run into a few issues. We found SCCM was not installed on a few computers or servers during installation. We had to get some help to deal with those problems and getting SCCM installed correctly. We figured out the requirements. Now it's working fine. 

    That was just initially. We do not spend a lot of time with SCCM now. Whenever we have a new computer connect with our networks, within two minutes it starts working. There are no more issues. Therefore, since implementation, we haven't really had to call them.

    Which solution did I use previously and why did I switch?

    We were not previously using any other solution. SCCM was our first.

    How was the initial setup?

    I did the configuration of SCCM from scratch, however, I did not configure the VMware Workspace One as it was installed on cloud. I basically just did it for an evaluation to have a taste of VMware Workspace One.

    Therefore, I don't know about the level of complexity or if it's easy or it's difficult in VMware Workspace One. In SCCM, however, there were some issues which I had to search and get assistance with and there were some issues that I resolved. I would describe it as somewhat complex. It was not so simple that anyone can do it.

    For me took me three to four days to configure it and set it up in perfect working condition. That was mostly due to the fact that I took some time to research the issues I came into contact with.

    The main production server is in our data center in Pakistan and production site server in Qatar and UAE, and their configuration is performed by a team in corporate office in Pakistan

    What's my experience with pricing, setup cost, and licensing?

    I'm more interested in features, which is where I spend most of my research time with products. I don't really get into pricing. I'm not sure of the exact price. I can't say if it's cheaper or more expensive than other options.

    Which other solutions did I evaluate?

    I've considered evaluating VMware WorkspaceOne, however, their product is limited when users are just trying them out.

    What other advice do I have?

    We are at an endpoint site. The servers that are in our data center.  I don't know which exact service-side version we are using at our data center.

    I would recommend SCCM to others. I've used it from scratch and with the new features, especially Intune. I do recommend the SCCM, especially in the Microsoft environment.  VMware Workspace One is also good, from what I understand. The issue is they give very limited trial features. If they would give I full fledged trial base version of the VMware Workspace One, it would be easier for someone to completely evaluate the two. Microsoft gives you a six month evaluation period, for example. That's a lot of time to get to know the system. 

    SCCM, therefore, is the best that I can tell, as I've been able to evaluate it fully. Overall, I would rate it eight out of ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Learn what your peers think about Microsoft Endpoint Configuration Manager. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
    564,599 professionals have used our research since 2012.
    Laurent Bert
    IT End User Computing Expert at a manufacturing company with 5,001-10,000 employees
    Real User
    Top 20
    A complete and reliable product that integrates well with the Microsoft ecosystem
    Pros and Cons
    • "It is a very well-rounded product. It is a complete package with all the features using which we are able to manage our PCs very efficiently."
    • "One area of improvement is regarding the patching of Office 365 products. We have some difficulties on this side, and it can be improved."

    What is our primary use case?

    It is used for software deployments, PC operating system deployments, and security patch deployments.

    Currently, we are using it on-premises, but we are slowly moving to the cloud solution that is called Intune or Microsoft Endpoint Management (MEM).

    How has it helped my organization?

    We have high availability for all of our deployments. We can trust this platform for all our deployments. We are quite happy with the fact that we can do what we want to do. It fulfills our goals for all deployments.

    What is most valuable?

    It is a very well-rounded product. It is a complete package with all the features using which we are able to manage our PCs very efficiently. 

    What needs improvement?

    One area of improvement is regarding the patching of Office 365 products. We have some difficulties on this side, and it can be improved.

    Their support should be improved. Mostly, when we are doing patches on Microsoft 365 clients, we need to escalate to Microsoft support. It takes a long time to get to someone in their support team who has good knowledge of the product. Their support at level one is not quite helpful and knowledgeable.

    For how long have I used the solution?

    In my current company, we deployed SCCM two years ago.

    What do I think about the stability of the solution?

    Its stability is quite good, and its performance is quite good. There is nothing to complain about.

    What do I think about the scalability of the solution?

    It is scalable, but we are far from reaching that limit. We don't have any problem with its scalability.

    We have three people working on the SCCM side. In terms of the implementation, we have 6,000 PCs that have this installed. It is being used daily.

    How are customer service and support?

    Mostly, when we are doing patches on Microsoft 365 clients, we need to escalate to Microsoft support. We are not quite happy with the support because it takes a long time to get to someone who is knowledgeable. When we have a tricky issue like this, it is very complicated to get appropriate support. We lose a lot of time with Microsoft support before we find someone who is able to understand and resolve the issue. 

    Which solution did I use previously and why did I switch?

    We were previously working with BigFix. I also worked with HPE's solution. As compared to these two products, SCCM is much more integrated with the Microsoft ecosystem. We are fully on Windows, so it is much easier for us to manage our PCs with SCCM. It is easier to have a Microsoft product on Microsoft operating systems.

    How was the initial setup?

    It is a Microsoft product, and we have an efficient team that is managing the solution. We have a lot of people who have the knowledge of doing its setup. So, deployment is not an issue for us. If you know the product, it is quite easy. You just need the knowledge of the product.

    From the beginning to the end, it took about six months. It was deployed on all PCs.

    What about the implementation team?

    We mainly had two people for its implementation. I managed the deployment, and I had one external resource who helped me in implementing the full product. To implement it, we needed to integrate all of the enterprise applications. This integration of the enterprise applications was outsourced, and there were a few people involved.

    For its maintenance, we have a resource in India who is managing the solution. We need one full-time administrator for managing the solution. We also have one person who is integrating new applications and updates with this platform.

    What's my experience with pricing, setup cost, and licensing?

    Its licensing is quite complicated because we are getting the license not only for SCCM but for the full Microsoft package. We don't need to pay for a separate license. We need to have one license that includes everything we need, such as Windows, Microsoft 365, SCCM, encryption, and so on. So, we don't have a specific price for it. Perhaps, it is good that it includes the full suite of licensing of Microsoft. It is expensive, but we are getting a lot of features.

    What other advice do I have?

    In the next release, we are moving to the cloud, which also fits the strategy of Microsoft. We would like that the features on the cloud side are very similar to what we have on the on-premise side. We are looking to move to the cloud with Intune, but Intune is not like SCCM in terms of the features. We prefer that they develop all the features on the cloud.

    I would recommend others to go for it if they are using any other solution to manage their Windows or Microsoft environment. It will make life easier. I would also recommend others to check the cloud solution before implementing the on-premise solution. They can see what can be done on the cloud. Cloud is not fully ready to replace the on-premise solution, but they can do some of the parts on the cloud and some of the parts on-premises.

    I would rate it a nine out of 10.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    OmidKoushki
    Solution Architect at KIAN company
    Real User
    Top 5Leaderboard
    Flexible, great for patching on virtual machines, and pretty stable
    Pros and Cons
    • "It's helped us solve problems surrounding patching, installing, and reporting different patches, etc., on the virtual machines."
    • "Based on my experience with SCCM 2016, the main, big issue is not having a good user-friendly environment. It needs much better GUI."

    What is our primary use case?

    We are using SCCM to manage the virtual machine configuration. We had around 100 or 200 virtual machines and wireless, and we need to configure different settings on all of the virtual machines. We need to handle patching, updating, and installing security updates. We prefer to use System Center instead of other solutions like GFI LanGuard that are already installed in other environments.

    How has it helped my organization?

    Previous to SCCM, the entire process was completely manual.

    What is most valuable?

    The solution is very flexible and very handy. It has helped us move past the process of manually updating.

    It's helped us solve problems surrounding patching, installing, and reporting different patches, etc., on the virtual machines.

    What needs improvement?

    Based on my experience with SCCM 2016, the main, big issue is not having a good user-friendly environment. It needs much better GUI. 

    We had some problems configuring Linux virtual machines. We needed to install agents. Microsoft should pay more attention to these Linux virtual machines in order to make implementation with them easier.

    For how long have I used the solution?

    I've been working in the System Center on two projects for around two years. 

    What do I think about the stability of the solution?

    The solution is extremely stable. We've only really had to restart the solution twice in the first year. It's very reliable.

    What do I think about the scalability of the solution?

    In terms of scalability, at that time I didn't need to scale the development. However, in the near future, it is possible. I don't have any idea of the timeline for our scaling the solution as I focus on VMware technology at this time.

    Our company has around 60 users. However, we offer this solution to one of the enterprise customers that use it for bank data centers. They have around 3000 staff.

    We are using the System Center to manage around 2000 virtual machines.

    How are customer service and technical support?

    In my country, due to sanctions, we cannot use direct support. We just use third-party partners in different countries. Generally, we support the System Center and all their products directly and don't need outside support.

    Which solution did I use previously and why did I switch?

    If a company migrates to a cloud environment, I prefer to use another solution. For example, in the Azure environment, I definitely use Intune instead of System Center. In other products, I use Jamf, which is a good product that is comparable with System Center in the cloud environment. 

    How was the initial setup?

    In terms of the current initial setup, the new version is a little bit more complex as you need to design a great architecture for the enterprise environment when we use a lot of virtual machines. For example, when you have more than 1,000 virtual machines, there needs to be a high level of consideration for the design of different components of the System Center.

    In terms of deployment, if you have a good design, the process may take about a week. You need, I would guess, one week for installing and preparing the environment. However, you need to relay different instructions in order to install it. In total, the process would take around one, or, at a maximum, two weeks.

    Our team consists of five members; one senior and four support engineers. Their job is to configure and maintain the active directory environment and the SCCM platform.

    What about the implementation team?

    I implemented the solution myself. I took a month to study the solution, and, after that, I was able to handle the process personally. I took only two days in terms of how long it took me to install it.

    What's my experience with pricing, setup cost, and licensing?

    The solution is pretty expensive. A company really needs to consider their environment.

    What other advice do I have?

    We're just a customer. In the past, we used System Center version 2012, and after one year we upgraded to System Center 2016.

    Out of all the products in the market, the best solution is System Center, especially for Microsoft virtual machines and all services that are related to Microsoft Technologies.

    If you are evolving in the Microsoft environment, I prefer to use the System Center due to the fact that it includes different solutions like System Center Configuration Manager, System Center Operation Manager, System Center Virtual Backup. It's a full solution and provides different services. It has great integration with other Microsoft products. 

    I would recommend the solution to an engineer or administrator. And first, a new user will have to study different best practices and have a good overview of the architect of System Center and the functionality of the different components. After that, they would have to go in through the details about the Linux machines. The biggest problems we had at the time of implementation was related to Linux virtual machines, not Microsoft virtual machines. With the licensing and the price, it's a tricky point that the engineers should consider when they need to set up a license

    Overall, I would rate the solution eight out of ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Enterprise Systems Engineer at a mining and metals company with 10,001+ employees
    Real User
    Great patch management, extremely responsive technical support, and very efficient
    Pros and Cons
    • "We have found the scalability to be quite good."
    • "In terms of the monitoring, the timeframe it takes to actually report back on the compliance of a device after it has been patched is a bit too long."

    What is our primary use case?

    We primarily use the solution for patch management, application deployment and operating system deployment.

    How has it helped my organization?

    It has improved our ability to remediate against critical CVE's in a timely manner across the enterprise.

    What is most valuable?

    The patch management is great. The ability to be able to centrally purchase servers is quite useful.

    The ability to monitor only after you have rebooted devices allows you to see if they have compliance or not.

    The efficiency - as opposed to patching once you have the time - of having a central repository to manage everything you need is very helpful.

    The solution is quite stable. 

    It's perfect for enterprises.

    We have found the scalability to be quite good.

    What needs improvement?

    In terms of the monitoring, the timeframe it takes to actually report back on the compliance of a device after it has been patched is a bit too long. That could be better. Sometimes you could be looking at a screen and may take about five to 10 minutes before you get back the actual compliance status and that could be reduced.

    Having a cloud solution is better in a lot of ways. For the deployment of the operating system, with InTune and modern end-point management, you no longer have to image machines and waste a lot of hours. You no longer have your technicians spending four, five hours imaging machine sessions for drivers and things like that. You can make use of an autopilot, which reduces resources and can cut down the timeframe drastically. There's a lot of wins with the cloud technology that's coming forward, that enterprises and organizations can make use of.

    For how long have I used the solution?

    I've used the solution over the three years. It's been in our organization for the past six years.

    What do I think about the stability of the solution?

    It's a very stable product. It is definitely an enterprise-grade patch management solution.

    What do I think about the scalability of the solution?

    The product is very scalable. When we have migrations and we bring on additional devices, such as during an acquisition of companies, it's great. We can bring them right into our environment. It's very scalable in terms of deploying and adding a new division to the solution. 

    Currently, we have it deployed to support over 20,000 PCs.

    Likely, we will increase usage. There are also new tools that are modern tools that we are starting to make use of. As much as you're doing something for patch management, where you need to enter the discussion is you need to start looking at modern endpoints, which is InTune, for example. We will start making use of InTune for the patch of end-points. We could also do scheduling of those patches as well from the cloud to the client. We are using, a hybrid approach. Generally, our goal is to expand usage.

    How are customer service and support?

    In terms of technical support, once you have a Microsoft agreement, the level of support would be the same across all our products. We have an enterprise-grade level of support. Therefore, once I create a critical case, I get support within the hour. We are quite satisfied.

    How was the initial setup?

    We have had a deployment in our enterprise for more than five years. It's a relatively complex deployment due to the fact that we have a large organization.

    I am one of the enterprise engineers. I make deployments happen at a new location and it may just be a matter of training the onsite technician at that new division on how to make use of it. We have an enterprise-grade deployment and we have divisional deployments where divisions can make use of it to still manage their in-house shops.

    What about the implementation team?

    A consultant would've assisted in the initial deployment.

    What's my experience with pricing, setup cost, and licensing?

    We do pay a licensing fee on a yearly basis. 

    There is a license cost and it is licensed per deployment. We do pay licensing costs for all of the deployments that we have on our end, across the enterprise.

    With the way everything is moving to the cloud, you need to have all of these licenses in place.

    What other advice do I have?

    We're partners with Microsoft.

    For people looking into implementing Configuration Manager at this point, I would recommend it. They should also look at InTune, which is more of an endpoint deployment. For the servers, you can still look at what we have, however, just the way, how things are developing, I can see the industry and patch management moving away from on-prem management to more like making use of the cloud and use of our Microsoft for business in terms of managing the updates, ease of updates and things like that. What is happening now is a paradigm shift.

    I'd rate the solution at an eight out of ten. It's great for enterprises.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Flag as inappropriate
    Abul Fazal
    Service Delivery Manager at Almoayyed Computers
    Real User
    Top 20
    Easy to implement with good patching and has lots of new features in the pipeline
    Pros and Cons
    • "Microsoft is being very competitive right now, and they are really investing in a lot of new features to be more competitive in the marketplace."
    • "We'd like the solution to make it easier to manage remote users."

    What is our primary use case?

    We primarily use the solution for client management, especially for day-to-day operational activities, like access management or software deployment.

    What is most valuable?

    The main key feature that we find the most valuable is the patching. The remote desktop is a very useful feature as well. The software deployment aspect is helpful too. These are the three core features from which we see the customers really benefit if they have a System Center Config Manager. This is especially true for enterprise organizations here.

    Microsoft is being very competitive right now, and they are really investing in a lot of new features to be more competitive in the marketplace. 

    What needs improvement?

    We are okay with all the available features.

    In the future, we're looking for tighter integration with cloud solutions like Windows Intune. It is already there, however, it's still in need of some improvements. It's not straightforward in terms of the administration on offer. 

    We'd like the solution to make it easier to manage remote users.

    It offers a very difficult cloud gateway when it comes to cloud management.

    The solution does need a lot of configuration and fine-tuning, so a company will need a dedicated person who's knowledgeable in the product to manage it.

    A few people complained that SCCM is very complex without CPS, depending on the SQL database, and when using SQL as a backend service. Sometimes updating the dashboard and getting the reports, can be slow. They're not getting an instant update on the database. That is where most of the customers tend to complain. 

    For how long have I used the solution?

    I've been using the solution since version 2.0 or something close to that. It may be at least 15 years.

    What do I think about the stability of the solution?

    We don't have very many issues in SCCM. It's not a plug and play software, however. From time to time it does require fine-tuning. You need the right management and administrative people in place to manage the product. This is essential in order to keep it running correctly.  

    What do I think about the scalability of the solution?

    We have clients in both the private and public sectors. 

    The solution requires fine-tuning and configuration tweaks. In order to scale it, you will need a knowledgeable person to manage the process.

    How are customer service and technical support?

    Technical support from Microsoft has been good. We've been satisfied with their level of service.

    How was the initial setup?

    We don't find the initial setup to be complex. We've done many implementations a this point, and we find it to be straightforward. Our team is very much experts at this point. They know all the processes and they go through everything step by step. 

    In terms of how long it takes to deploy the solution, this question is very tricky. It's all dependant on the customers, and their environment as well as the customer's readiness to proceed. If it's a POC, where I don't have any dependencies on the customer side, that everything will be within the private network, isolated environment, I can handle a deployment within two days. We can install, configure, and make everything ready in that short amount of time simply because we don't have customer dependencies.

    You do need to have the correct people in place to manage it once it's up and running. They need to be experienced and dedicated to the product.

    What about the implementation team?

    We're an integrator and service provider here in Bahrain, so we have done more than a couple of installations, so where our team is very confident in our ability to implement the solution on behalf of our clients.

    Which other solutions did I evaluate?

    We're actually looking at ServiceNow as a potential product to use in the future.

    What other advice do I have?

    We are a Microsoft gold partner.

    We're noticing many users in our country moving away from Microsoft and towards AWS.

    We tend to use the latest solution, or something close to that. We always are trying to keep it up to date in all the customer database and systems. Whenever there is the latest update available, we update everything immediately for our customers. The latest version may be 19.06.

    While all the customers we have are currently on-prem, we are looking for cloud-based solutions going forward, due to the fact that our customers tend to gravitate towards the cloud. They are like looking for something they can easily manage. That's all clients, irrespective of whether they are in the office or are our mobile users. 

    I'd rate the solution eight out of ten. I really like the product, however, there's always room for improvement.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company has a business relationship with this vendor other than being a customer: partner
    Systems engineer - IT infrastructure management at a tech services company with 51-200 employees
    Real User
    Top 20
    An easy initial setup and very scalable and stable
    Pros and Cons
    • "The initial setup is straightforward and not too complicated."
    • "With Microsoft Premier Support, you get what you pay for. There's Third Tier Support that you pay for. If you pay for that, you get excellent support, and if you don't pay for that, then you get the less experienced staff."

    What is our primary use case?

    We primarily use the solution for client and server deployments, and software deployments, as well as software metering.

    What is most valuable?

    The entire solution, from end to end is excellent. It's doing essential work for us at our company.

    The initial setup is straightforward and not too complicated.

    What needs improvement?

    I can't think of any features that are lacking in the solution. It's quite complete, and a rather standard setup.

    If you want the best support, you need to pay for it. Otherwise, you may get less technical help.

    For how long have I used the solution?

    We've been using the solution since its inception. It's been maybe ten years or more at this point.

    What do I think about the stability of the solution?

    The solution is very stable. It's reliable. You don't have to work about bugs or glitches. There aren't any crashes. It doesn't freeze.

    What do I think about the scalability of the solution?

    The solution is very scalable. If an organization needs to scale up, the can do so easily using this product.

    Right now, we have about 4,000 users on the solution.

    How are customer service and technical support?

    We have Microsoft Premier Support.

    With Microsoft Premier Support, you get what you pay for. There's Third Tier Support that you pay for. If you pay for that, you get excellent support, and if you don't pay for that, then you get the less experienced staff. There are products where we do have Third Tier Support, and there are products that are not so mission-critical, where we don't pay that much.

    At Microsoft, if we wanted to, we can get the level of that kind of super support, super fast. It's not that they leave a void open that we would like more. If we want more, faster, we can pay for it.

    Which solution did I use previously and why did I switch?

    If the company did use a different solution, that would have been about 15 years ago and before my time. I couldn't say what it might have been. Right now we're System Center 2012, before that it was 2007. Then before that was 2003, and then 2004. Before, the product was called SMS, so it's been around for a while. The previous product might have been a solution called Altaris. Again, that's about at least 15 years ago.

    How was the initial setup?

    The initial setup, for the most part, is not complex. It depends on the company's individual setup, however, it's quite straightforward if you know what you are doing.

    Deployment typically takes about three months.

    You only need about four staff members for deployment and maintenance. They are all systems specialists and engineers.

    What about the implementation team?

    We used to use sellers or consultants. However, we are moving away from that and attempting to implement the solution ourselves internally. We want to have the knowledge completely in-house.

    What's my experience with pricing, setup cost, and licensing?

    We have a basic enterprise agreement with Microsoft which isn't cheap, per se.

    I can't get into the exact cost structure.

    The question of pricing is a bit relative. The enterprise-level that we use is always a negotiation. I don't want to use the word monopoly, however, there's no alternative enterprise vendor that covers all bases, from server storage and backup and everything else in between. Pricing is just a matter of negotiation every time the contract renewal period comes up.

    Which other solutions did I evaluate?

    Right now we are starting a POC for Azure and Office 365. The idea is that it depends on the government and if data privacy and compliance rules allow any change. If we can use Azure's public cloud, and Office 365, then the usage utility of the on-prem requirements would go down. 

    Microsoft Cloud has integration with Intune, which is the cloud version of SCCM in the center. As far as I can see, there is good integration.

    What other advice do I have?

    We're a Microsoft customer.

    It's a very good product. The basic question is the size of the company itself that may want to implement the solution. the point is if you're big enough to afford an enterprise agreement, with Microsoft, then I would highly recommend it. It's a suite of products. If you're a small to medium business, which does not have an enterprise agreement with Microsoft, I would recommend that you look around for third party products. Simply from a cost perspective, you might be better off, but if you have the money and the size and the revenue, then definitely, Microsoft is the way to go, because it includes everything.

    I'd rate the solution ten out of ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    Director of Professional Services at a tech services company with 11-50 employees
    Real User
    Top 20
    Good visibility, and support, but it would be easier to have remote sessions into the box
    Pros and Cons
    • "It lets you know what your infrastructure is like and what state you are in."
    • "It would be nice to have everything in one place. Now they have Intune for the desktops and SCCM to handle their servers."

    What is our primary use case?

    We use it and our clients use it for device patch management, servers, and management processes.

    We deploy it for clients but we don't usually maintain it for them.

    What is most valuable?

    The best thing about SCCM is the patch management. You can make sure that all of your devices are there. You can see all of them and see your levels.

    It lets you know what your infrastructure is like and what state you are in.

    SCCM internally works great. On your internal infrastructure, it is fantastic. It gives you everything you want it to do.

    What needs improvement?

    Because of the way SCCM is, we are moving to the Intune platform similarly to the way that everybody else is. Microsoft is slowly migrating SCCM to the new Intune product for management.

    There are so many issues with SCCM, but they are already working on migrating the desktop to the intune platform. They have already improved the management and the patch management. They are also looking at cloud integration and being able to deploy it in Azure properly and run the Azure infrastructure.

    The main or legacy issue is not being able to do remote management of devices without being on a VPN to get their updates. It didn't work well on non-corporate networks. This has been resolved by the new Intune platform.

    It's Microsoft, they have their issues, but they are getting better. They are integrating it with their office products, and their platforms.

    In the next releases, I would like to see them make it easier to do remote sessions into the boxes.

    It would be nice to have everything in one place. Now they have Intune for the desktops and SCCM to handle their servers.

    For how long have I used the solution?

    I have been using SCCM for ten years.

    We were using some of the older versions.

    What do I think about the stability of the solution?

    The stability is only as good as your infrastructure.

    What do I think about the scalability of the solution?

    The scalability of SCCM is good but now that it is on the intune platform, it's even better.

    The usage and how extensively it is being used depends on the client and the client's roadmap.

    How are customer service and technical support?

    As gold partners, you have a direct line to Microsoft technical staff. It is easy for us to get support.

    Our experience with the support is a positive one.

    Which solution did I use previously and why did I switch?

    I have been using Zabbix for ten years. I have deployed it in my infrastructure.

    I have integrated it with Grafana.

    How was the initial setup?

    The initial setup is pretty straightforward.

    Depending on the customer and their infrastructure, it could be easy. If it is a small infrastructure the installation could be quite quick. You could fire up SCCM, sent the probes, let them detect it, and put it in. 

    For large infrastructures or complex networks, it can be more difficult. It can take as long as a day to get it all set up and running or it could even take a week.

    One of the joys of SCCM is that one person could easily maintain it but we have two people from the service desk.

    What's my experience with pricing, setup cost, and licensing?

    They are always changing their price model, which I don't like. It would be better if they didn't keep adjusting their price model.

    The price model is different for every client. It depends on the corporation, the company's subscription balance, and how many machines they have. For us, it fluctuates. 

    Some clients have a smaller infrastructure, and for those with large infrastructures, it will cost them more. Others will also have multiple versions of it for backup and failovers.

    Which other solutions did I evaluate?

    I was looking for a comparison to see if I want to propose them to some of my clients.

    What other advice do I have?

    If you are implementing from new, go with Intune directly, don't use the on-premises version.

    With the transitioning state to the cloud versions, I would rate SCCM a seven out of ten.

    They have handled desktops very well but they haven't transitioned servers very well.

    Which deployment model are you using for this solution?

    Hybrid Cloud
    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    Flag as inappropriate
    Buyer's Guide
    Download our free Microsoft Endpoint Configuration Manager Report and get advice and tips from experienced pros sharing their opinions.