We just raised a $30M Series A: Read our story
SM
System Engineer at a tech services company with 201-500 employees
MSP
Top 5Leaderboard
Full featured and stable but limited support for one operating system

Pros and Cons

  • "SCCM does everything from A to Z for a Windows operating system."
  • "They need to improve the support for the Mac operating system."

What is our primary use case?

SCCM does everything from A to Z for a Windows operating system. It provides a full-featured deployment for Windows-based systems from the setup screen.

How has it helped my organization?

It has reduced a lot of burden from external and internal IT teams, where they have to build systems individually.

What is most valuable?

There are many features that are useful, I will mention a few of the primary ones. You have a tool that enables you to build an operating system image and deploy it to a number of devices, system patching, application deployment, compliance checking, thorough documentation for installation and it has the ability for easy policy assignment management.

What needs improvement?

SCCM supports the Windows operating system well: however, there is minimal support for Mac and none for mobile devices. Organizations that do not just go with a single operating system, having the flexibility to support more operating systems and devices would be an added advantage. This would allow them to stand out from other products on the market.

For how long have I used the solution?

I have been using the product for approximately two years.

What do I think about the stability of the solution?

The solution is stable enough to manage your Windows operating system.

What do I think about the scalability of the solution?

We use the solution for a user base of approximately 500. It is scalable.

How was the initial setup?

I would say it's a bit complex. There are prerequisites which you have to install first before installing SCCM. You need a server in place, a SQL database and some other software installed separately, for example, Management Studio.

What about the implementation team?

We had experienced before allowing us to install the solution ourselves by following the documents provided. It usually takes five to six hours. The time is all depending on the hardware configuration on the server and if there are good hardware installed. It could take much more time if the setup is not good or if you are new to installing these type of solutions.

What was our ROI?

We have had a lot of issues with Mac application deployment support. They need to improve the support for the Mac operating system.

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

There are a few licensing required. When you purchase the SCCM licence the SQL server license is included. When you compare this solution with other tools in the market you might actually find a lot of variation in the pricing and that's why people opt for the other tools rather than Microsoft tools.

What other advice do I have?

Compared to other tools I would recommend SCCM as a good solution for Windows systems only for managing your systems because it provides support for server operating system as well, rather than only for the client's operating systems.

I would rate SCCM a nine out of ten but since their support for other operating systems other than Windows is limited, I rate them overall, a six out of ten.

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
RZ
System Engineer
Real User
Scalable with good management and an excellent set of features

Pros and Cons

  • "The solution has a very good set of features."
  • "The analysis is something that can be integrated. Their report analysis can be improved a little bit due to the fact that most of the time complaints policies are saved by the admins. It's something that we need to look into and search for."

What is our primary use case?

We primarily use the solution for patch management.

What is most valuable?

The solution may be one of the top products from a management standpoint. It's excellent.

The solution has a very good set of features.

Its capabilities are quite robust.

What needs improvement?

Sometimes the time it takes to find the fault is a bit too long. The resolution time needs to be shortened quite a bit. There are just some analysis errors that need to be cleared up quicker in general. Otherwise, data blocks and the firewall can be affected unnecessarily.

The analysis is something that can be integrated. Their report analysis can be improved a little bit due to the fact that most of the time complaints policies are saved by the admins. It's something that we need to look into and search for. It would be nice if there was just a cohesive report of what was saved, etc. 

For how long have I used the solution?

I've been working with the solution for about two and a half years at this point.

What do I think about the stability of the solution?

The stability is very good. We don't have any issues with it. It's very reliable. I'd give it five stars.

What do I think about the scalability of the solution?

The solution is scalable. We do have options to integrate other products as well. You want to combine your MDM solution with SCCM, for example. Scalability is something I would give them five stars for.

As admins, we do have rules for distributing. Basically, to manage inventory on all those steps. In our current organization, we are connected to approximately 300 million servers.

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

We didn't previously use a different solution. Previous to initiating the use of SCCM, everything was pretty much a manual process.

How was the initial setup?

The initial setup is not complex. I believe it is very straightforward. You can choose to do it manually or you can do it via an automation feature that is available to push everything for you. 

Depending upon how big your organization is, how the sites are spread across mainly on physical entities, on logical entities, the installation and the detection will not take much time. In most cases you can have it configured in five to ten minutes in order to detect once the reporting gets updated. That said, if there are different geographical locations, the entire process can take a day or so. 

What was our ROI?

I've had to reach out to technical support in the past and I'm satisfied with their level of service. They are very knowledgeable and responsive.

What other advice do I have?

We're just a customer and an end-user. We don't have a business relationship with SCCM.

Overall, I would rate the solution at a seven out of ten. We've been mostly satisfied with it as a product.

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.
542,721 professionals have used our research since 2012.
Serge Gagnon
Développeur at a tech services company with 11-50 employees
Real User
Top 20
Does the job, meets our needs, and makes deployment easier

Pros and Cons

  • "It does the job and meets our needs. With everybody working remotely these days, we are using this solution to deploy everything. The deployment of PCs is easy."
  • "It should provide the ability to remotely connect to mobile devices. There are some solutions that are doing that, but with Microsoft Intune, the only way to remotely connect to devices outside the organization and mobile devices is by using TeamViewer. It is pretty strange for a big company like Microsoft to not have something for that."

What is our primary use case?

We are using Microsoft SCCM as the deployment platform for our environment to deploy laptops and PCs for the help desk technicians. We also use it to deploy applications and servers and provide some reports to the organization about what is currently deployed. We are using its latest version.

How has it helped my organization?

We do not have a big IT department, so it solves a major part of our problems and makes it easier to deploy applications, servers, PCs, etc.

What is most valuable?

It does the job and meets our needs. With everybody working remotely these days, we are using this solution to deploy everything. The deployment of PCs is easy.

What needs improvement?

It should provide the ability to remotely connect to mobile devices. There are some solutions that are doing that, but with Microsoft Intune, the only way to remotely connect to devices outside the organization and mobile devices is by using TeamViewer. It is pretty strange for a big company like Microsoft to not have something for that.

What do I think about the stability of the solution?

It is stable. When the applications are set up correctly, we didn't face any major problems. Most of the problems are related to DNS and other things that are outside of SCCM. They are not related to SCCM.

What do I think about the scalability of the solution?

Currently, our business is really stable, and there is no need to increase the devices in our organization. We have six technicians who are using it currently.

How are customer service and technical support?

We are not using any tech support outside our organization. We are handling it internally.

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

I have used some solutions in the past, but in our organization, there was no centralized management application before SCCM.

How was the initial setup?

It is not hard to deploy and manage, but you need some knowledge of what you want to do. SCCM is strictly based on the specific configuration of the network. Therefore, you need to know the network configuration and how to use Microsoft Active Directory. If you have made a bad choice at the beginning, it will be hard to roll back and redeploy it. It works well when the environment is well configured. It doesn't really work well when the corporate network is not as good as it should be.

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

Its price is okay because it is part of our licensing.

What other advice do I have?

I would recommend having someone to help with the deployment because the success of its deployment depends on the experience of the people who are deploying it. If you don't have enough experienced people in the internal IT department, it would be helpful to have a consultant from outside the organization to assist you.

I would rate SCCM 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.
Flag as inappropriate
SR
Associate Director at a consumer goods company with 10,001+ employees
Real User
Stable with good administration and excellent scalability

Pros and Cons

  • "Technical support is very helpful and very responsive."
  • "It is a bit of an old and outdated product."

What is most valuable?

The administration of the solution is very helpful.

It offers many of the same features other solutions would offer. It's very similar in scope.

The solution has been very stable over the years.

The product is capable of scaling.

Technical support is very helpful and very responsive.

What needs improvement?

It is a bit of an old and outdated product.

The cloud would have been the best improvement and already Microsoft is looking into it. They are moving into the cloud and all it will make the product better. There's a roadmap in place, from what I understand. We'll move ahead toward whatever Microsoft decided to deploy.

The solution is mainly used for client management and software deployment. However, there maybe should be a more self-service experience. Microsoft may be addressing it in their cloud-native solutions, as currently a lot of administrative tasks are still needed. Automation would be helpful in those cases. If they could add more automation, that would be ideal.

For how long have I used the solution?

I've used the solution for the last eight to ten years or so. It's been almost a decade. I've worked with it for a long time. 

What do I think about the stability of the solution?

The solution offers good stability. there are no bugs or glitches. It's reliable. It doesn't crash or freeze. The performance overall has been very good.

What do I think about the scalability of the solution?

A company can easily scale this product if they need to.

How are customer service and technical support?

Technical support has been amazing. It's Microsoft and their bread and butter is understanding their product. They built this technology and therefore can offer amazing support. At any level, for any questions, they can support you. We've very satisfied with the level of assistance they've provided.

Which other solutions did I evaluate?

I've also evaluated VMware, which would be a good option for companies that are not dealing with a lot of Microsoft applications.

What other advice do I have?

We're just a customer and end-user.

We use the latest version of the solution. I can't speak to the exact version number.

I'd rate the solution at a ten out of ten. It's an incredible product.

I would recommend other companies to go ahead with whatever the latest cloud option is on offer. That is due to the fact that there is no SCCM as a product now. They have already transformed it into Microsoft Endpoint Manager

If a company is heavy on Microsoft products, like Office 365, this is the right tool, however, if not, if they are not a Microsoft centric organization, then maybe they can explore VMware as well. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
SN
Specialist (US IT Recruiter) at a tech services company with 1,001-5,000 employees
Real User
Top 10Leaderboard
A systems management software good detailed descriptions, but dependency relationships could be better

Pros and Cons

  • "It uses detailed descriptions of the workstations, and that is good for me."
  • "I want the system to provide some dependency relations. I would also like to see the relationship between different machines."

What is our primary use case?

We use SCCM to access user data.

How has it helped my organization?

Basically, my requirement was to get the data from wherever it was available within the organization. SCCM helped identify how many computers we had, what software was loaded on it, what different types of data were available, and so on. It helped us a lot when it came to extracting the data.

What is most valuable?

It uses detailed descriptions of the workstations, and that is good for me.

What needs improvement?

I think SCCM can improve whatever details they shared with the integration partner. There was a lot of junk software and data. There should be flexibility to allow us to extract the data we require. In other words, the flexibility of accepting the specific data that we are looking for.

I want the system to provide some dependency relations. For example, you have a laptop, and you start working on it. If I can be informed that you're using the laptop at work, other machines that are dependent on this laptop will be able to provide that dependency relationship. I would like to see the relationship between different machines.

For a small-scale industry, the storage capacity is good. However, the performance and storage capacity could be better.

For how long have I used the solution?

I have been using SCCM for a while as part of an integration project.

What do I think about the scalability of the solution?

We are running almost 5,000 machines, and it was working fine from a performance perspective. 

How are customer service and technical support?

Technical support is good.

How was the initial setup?

The initial setup was straightforward and took us about a week to deploy this solution. The strategy was simple. We just had to do it in the same plugin, and we actually did learn on the job each day.

What about the implementation team?

We used an integrator, and we still use them regularly or even daily. We might use them for other integrations as well.

What other advice do I have?

I would tell potential users that SCCM is a good solution if their focus is on the number of computers and laptops they have in the company.

I used it for the first time, and it was good. But users should know what kind of databases they are using and if the integration has sufficient rights to access that data.

On a scale from one to ten, I would give SCCM a seven.

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
Juned Bedrekar
Consultant at ATOS
MSP
Offers excellent patching and troubleshooting features

Pros and Cons

  • "Offers good patching."
  • "Cloud-based improvements need to be better managed."

What is our primary use case?

Microsoft Endpoint Configuration Manager, formerly known as SCCM, is used for patching machine servers and application deployments. It also stores an inventory of machine hardware. We are customers and I'm a consultant. 

What is most valuable?

Patching is an important feature in the solution. Because it's console-based we can create one application or patch in the console. It will download and from the console base we can deploy to all machines. If your company has around 1,000-2,000 machines we're able to patch and deploy to all concurrently. We're also able to check, report and troubleshoot if there are any issues or errors that occur during deployment. We currently have 500 plus servers which are managed automatically on cloud.

What needs improvement?

Cloud-based improvements need to be better managed than is currently the case. 

For how long have I used the solution?

I've been using this solution for nine years.

What do I think about the stability of the solution?

The solution is quite stable because it's a Microsoft product. Even though it's cloud-based it's quite stable. We have two engineers that deal with maintenance. 

What do I think about the scalability of the solution?

The solution is quite scalable, although there is a lot of competition from products such as AWS and IBM BigFix.

How are customer service and support?

We've had good experience with Microsoft technical support. 

How was the initial setup?

The initial setup was straightforward. It's a matter of downloading from Microsoft, updating on the console and deploying. The amount of staff required for deployment depends on the level of infrastructure. Before the deployment, you need to test the machines to check whether a particular patch is installed and updated properly on that machine and whether there are any bugs. Installation is a step-by-step process. We can do about 20,000 per week, so within five weeks the job can be done. If there are only 10,000 machines, deployment can be completed within a week. 

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

Licensing is better than with other solutions because it's Microsoft-based. Microsoft offers multiple options which works for us. 

What other advice do I have?

The solution is good for us because most of our users are using Microsoft-based products and the solution is compatible for anyone using Linux-based or AWS.

I rate the solution nine out of 10. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
EM
System Administrator at a tech services company with 10,001+ employees
Real User
Helps to file claims from servers and has good patching

Pros and Cons

  • "Patching is the main feature because SCCM is made to control the entire environment without manually interpreting. So it is good to use for patching."
  • "The main room for improvement is the on-screen display. I think it would be good if some improvements were made."

What is our primary use case?

Our primary use case for this product is for patching and sending back packages to the client.

How has it helped my organization?

SCCM helps to file the claims from servers.

What is most valuable?

Patching is the main feature because SCCM is made to control the entire environment without manually interpreting. So it is good to use for patching.

What needs improvement?

The main room for improvement is the on-screen display. I think it would be good if some improvements were made.

Overall, as of now, it's sufficient for us. I don't have any scope of what new features would be needed for our company. I'm not sure if we require anything more. We are good with this product. If our companies move to the cloud or something, maybe we'll need additional features.

For how long have I used the solution?

I have been using SCCM for 10 years.

What do I think about the stability of the solution?

The stability is also quite good.

What do I think about the scalability of the solution?

The scalability is quite good.

We don't have a separate team using it. It's an operations team, where everyone works in every technology.

There are about 5 - 10 people using it - Windows server persons, applications teams, and other teams.

How are customer service and technical support?

We very rarely have contact with the technical service. I think about once a year. That's it. We don't require it because most of the time we fix any issues ourselves.

How was the initial setup?

The initial setup was straightforward. It was quick and it took a day. We didn't have any issues.

What other advice do I have?

My advice for this product is that it's a team tool that can be helpful. At the same time, it can be harmful if you are not using it properly - it can ruin your company. That's because if someone messes up, they can send a package to one client instead of sending it to another. Once you start the initial installation, it is difficult to stop it. So you should be careful.

On a scale of one to ten, I would rate SCCM an eight.

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
MT
IT Technical Support Manager at a financial services firm with 10,001+ employees
Real User
Helpful reporting tool, scalable, and offers valuable organization viability

Pros and Cons

  • "I have found the solution to be scalable. We have around 50,000 users using the solution."
  • "I currently need to increase my compliance level in the patching processes which this solution could improve on."

What is our primary use case?

This solution helps to manage different areas. For example, asset inventory and software inventory. You are able to patch products, do software deployment, and software packaging. 

What is most valuable?

I have found some valuable features to be the built-in reporting tool, the ability to get visibility on your organization, compliance reports, software remitting for all your products in your organization, and the management of all machines in your environment including a new domain and workgroups.

What needs improvement?

I currently need to increase my compliance level in the patching processes which this solution could improve on. For this purpose, I am looking for another solution to perform more efficiently and to work faster to cover this part specifically.

There should be more visibility to integrate more products other than Microsoft products. For example, Adobe and Google Chrome. You need to do a lot of manual intervention to cover all non-Microsoft products for patching at the moment. There are third parties working on these gaps in this solution. 

For how long have I used the solution?

I have been using the solution for 12 years.

What do I think about the stability of the solution?

The solution is stable most of the time.

What do I think about the scalability of the solution?

I have found the solution to be scalable. We have around 50,000 users using the solution.

How are customer service and technical support?

We were satisfied with the support sometimes. There were occasions when we have had an engineer that was not experienced in the particular problem we encountered to be able to help efficiently. This could be improved by having better-trained engineers.

How was the initial setup?

The specifications for the SCCM and the organizational capacity can make the installation complex otherwise it can be easy.

What about the implementation team?

The deployment took a long time. We required a team system engineer from Microsoft to be allocated with my team to complete any configuration.

What other advice do I have?

We are currently looking for another solution to work in parallel to cover some of the gaps in functionality.

I rate SCCM 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.
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.