We changed our name from IT Central Station: Here's why
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.
User at a computer software company with 1,001-5,000 employees
MSP
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
Learn what your peers think about Microsoft Endpoint Configuration Manager. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
565,689 professionals have used our research since 2012.
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
System Engineer at a tech services company with 201-500 employees
MSP
Top 5
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
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.
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.
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
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.
Buyer's Guide
Download our free Microsoft Endpoint Configuration Manager Report and get advice and tips from experienced pros sharing their opinions.