We just raised a $30M Series A: Read our story

Microsoft Endpoint Configuration Manager OverviewUNIXBusinessApplication

Microsoft Endpoint Configuration Manager is the #1 ranked solution in our list of top Configuration Management tools. It is most often compared to Ansible: Microsoft Endpoint Configuration Manager vs Ansible

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 is also 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: October 2021

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

Pricing Advice

What users are saying about Microsoft Endpoint Configuration Manager pricing:
  • "The price model is different for every client."
  • "Pricing is negotiable with Microsoft, depending upon which of their packages you choose."

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
US
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.
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.
Learn what your peers think about Microsoft Endpoint Configuration Manager. Get advice and tips from experienced pros sharing their opinions. Updated: October 2021.
541,708 professionals have used our research since 2012.
Abul Fazal
Service Delivery Manager at Almoayyed Computers
Real User
Top 10
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
JP
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.
SB
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
BP
Infrastructure, Technical Computing Applications at EQF Solutions
Real User
Top 20
Stable and works well for large environments

Pros and Cons

  • "We're a Microsoft-centric organization, so we are happy with the integration between products."
  • "There is no asset management package included."

What is our primary use case?

The primary use case for SCCM is for managing workstations.

All of the software that runs on our workstations is packaged and distributed and managed. Along with that, some of our security software is managed a little bit differently, but is accounted for in that way.

We also use it for keeping track of our patches.

What is most valuable?

We're a Microsoft-centric organization, so we are happy with the integration between products.

The interface, customization, and security are all pretty good.

What needs improvement?

There is no asset management package included. You have to buy that separately so we need  to use another system to manage that. This is one of the biggest things that makes SCCM not as competitive as some other systems. If they had this functionality then their help desk software would be much better and much more useful.

It is a little bit fat on the client-side, in terms of the stuff it leaves in place after the management is complete. It would be nice if they could pay attention to that, although we have a separate way of dealing with it.

For how long have I used the solution?

I have been involved with using SCCM in four or five different places for a total of close to 15 years.

What do I think about the stability of the solution?

SCCM has no issue with stability.

What do I think about the scalability of the solution?

This is a scalable product. The biggest group that I have been involved with was maybe 15,000 people. Typically, the sizes are in the 1,000-person area and it's not the type of product that you put together and configure for an office.

How are customer service and technical support?

Their SCCM support is slightly better than their general support. Their general support, Microsoft is tiered so you have to fight your way through the tiers to get to the real people. There's no way around that, but that's just the way they are. I understand that because they're such a big company

How was the initial setup?

I have not done the initial setup alone, and I wouldn't recommend doing it for anybody who didn't know what they were doing, or that hadn't done it before, because you have to go through a certain learning process.

I have seen that a base installation complete can be done in three days, and I have also seen an environment with 1,000 workstations deployed in two weeks.

What about the implementation team?

I have always worked with somebody who is well-versed in the solution to assist with deployment. I rely on a Microsoft MVP-level person to get the install done properly for me.

One person is enough for maintenance.

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

Pricing is negotiable with Microsoft, depending upon which of their packages you choose. They're changing their packages, and I don't know how they're changing them yet. It's been a few years since I have worked in that capacity.

Which other solutions did I evaluate?

We continually look at and evaluate everything.

Microsoft has Intune, as well. However, Intune is a choice if you're in a smaller-scale situation. Typically, I don't get called into things unless it is large, where I interact with clients on technical computing and solving network problems that are related to workstation issues. For these types of larger things, SCCM is a logical choice.

I haven't been in a Unix environment beyond having to do database-engine-related work.

What other advice do I have?

My advice for anybody looking into implementing SCCM is that it has to be on a larger scale, and you have to be committed to Microsoft.

I would rate this solution an 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.
SS
User at a computer software company with 1,001-5,000 employees
MSP
Top 20
Stable with an easy initial setup and good batch management

Pros and Cons

  • "The initial setup is fairly straightforward."
  • "The solution is a bit heavy on the sources such as RAM or CPU and the software needs to be a bit lighter."

What is most valuable?

The new CMD features are excellent. It is like a cloud environment gateway. 

The batch management is very helpful. The software deployment happens in there. 

There are many features relevant to many of our clients.

The initial setup is fairly straightforward.

What needs improvement?

The interface needs to be a little bit simpler. Right now, it's a bit hard to navigate with ease.

The integration capabilities could be better. They need to expand this aspect of their product.

The solution is a bit heavy on the sources such as RAM or CPU and the software needs to be a bit lighter.

SCCM does not support Linux and Unix. That has been deprecated and is no longer there. 

It would be ideal if the solution came with more features supporting Mac, then it would be a better product.

What do I think about the stability of the solution?

The solution is quite stable. We haven't really dealt with bugs or glitches. It doesn't crash or freeze. It's reliable.

What do I think about the scalability of the solution?

You can scale it up if you need to. You can add the client servers, for example. I've had multiple primary sites that I get as I go. A company that needs to scale can do so with relative ease.

We deal with companies that are often medium-sized or enterprise-level.

How are customer service and technical support?

The technical support is good. It's provided by Microsoft and we have lots of cases with Microsoft. They have been able to support us effectively so far. We're satisfied with the support so far.

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

SCCM has been the only product that we have worked on. We haven't used anything else. We haven't worked with BigFix or anything like that.

How was the initial setup?

The initial setup is easy. It's not overly complex. That said, anyone who's doing it needs to be a bit clever. It's not for people with little technological background. There is a bit of research required. You need to learn a bit about the product for effective deployment.

What about the implementation team?

We handle the deployments for clients.

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

I don't deal with the pricing. I'm not aware of the costs in general. I can't say if it's reasonable or expensive. It's not my area of expertise.

Which other solutions did I evaluate?

I haven't really evaluated other solutions. However, I just received a proposal from one of our sales associates, and the company had BigFix. They were trying to move on to SCCM. They had some questions regarding whether the same features would be available in SCCM or not. That's the reason I went to do some comparisons.

What other advice do I have?

We are Microsoft partners. I'm a consultant. This solution is being used by my client's companies.

We are using the latest version of the solution, which is 2010.

I would recommend SCCM based on the requirement of the customers. However, if they are looking for Unix and Linux support, which is no longer in SCCM, I'd recommend BigFix. That solution is better for Unix and Linux.

Anybody who wants to implement SCCM should do some research online, depending upon what features they want. Once they see that SCCM will be able to manage, will be able to resolve their issues, they should choose it. However, they need to look for a partner, a Microsoft partner, that can take help from them for deployment purposes.

I would rate the solution eight out of ten. If the product used less resources, I would rate it higher

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
Flag as inappropriate
CD
Global Tech Delivery Lead Win & EUC at a manufacturing company with 10,001+ employees
Real User
Stable with good on-premises usability and has potential to scale

Pros and Cons

  • "The solution is stable."
  • "The solution is on-premises. The cloud version of the product, if a person needs to be on the cloud, would be InTune, which already exists as an option. SCCM doesn't need to offer cloud features for this reason."

What is most valuable?

The on-premises useability is very good.

The solution is stable. 

For the most part, for our needs, the scaling is fine.

What needs improvement?

Microsoft is already pushing users towards Intune, as opposed to SCCM. It's on the roadmap for them. It's inevitable. SCCM will be on Endpoint Manager in the future. I would say nothing needs to be changed.

The solution is on-premises. The cloud version of the product, if a person needs to be on the cloud, would be InTune, which already exists as an option. SCCM doesn't need to offer cloud features for this reason.

For how long have I used the solution?

We have used the solution for the past decade. It's been around ten years at this point.

What do I think about the stability of the solution?

The solution is stable. There are no bugs or glitches. It doesn't crash or freeze.

What do I think about the scalability of the solution?

SCCM is built for corporate networks. There is some advantage from Microsoft in terms of the content management gateway that we already have so that we can utilize the internet, however, scaling is fairly it's straightforward.

In our company, we have 44,000 devices. We do not need more. Scalability-wise we are good. We are not a company of hundred thousand devices. I'm not looking to scale it more. Therefore, I can't speak to what scalability would be like for those with 100,000 or more devices.

How are customer service and technical support?

We have a support team that does technical support for us. I don't work directly with Microsoft. I go into priority calls, however, our technical teams manage that. Therefore, I can't speak to how helpful or responsive they are.

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

We are trying to transition from SCCM to Bigfix.

How was the initial setup?

My understanding is that the installation is a two-day setup, however, I did not personally set it up, and therefore can't speak of the implementation or how easy or difficult it might have been.

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

I cannot speak on pricing. I let the procurement team deal with it. Therefore, I don't have any information on licensing fees, et cetera.

Which other solutions did I evaluate?

I have looked at comparisons between Bigfix, SCCM, and Intune. I personally prefer INTune as a solution, however, the company is moving towards Bigfix and away from SCCM.

What other advice do I have?

We are just customers and end-users of SCCM.

We have been using SCCM for the past decade, however, now, the company is supposed to go with Intune for model management. However, we have a new CPO or CSO double hatting with security as well. He's more inclined in Bigfix features, which offer more robust patch management as well as vulnerability scan. SWe dropped the plan to go with Intune and will go with Bigfix, moving us away from SCCM.

Our CPO, CSO is mainly the driver for the change, not because it is on our roadmap or our partnership with the vendor or anybody else.

In general, I would recommend the solution to other organizations and companies. We've been happy with it over the years. I'd rate it at a nine 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.
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.