Microsoft Configuration Manager Reviews

We use the solution to monitor our servers and clouds. We also use it for software and hardware inventories.

Hardware and software inventories help us discover the resources and assets in our organization. The dashboards have information about our assets. We use the reports for decision-making. The tool gives good information about our resources in the organization.

The solution is crowded with information. It is complicated to search for things.

I have been using the solution for almost six months.

The stability is excellent. I have had no problems. I rate the product’s stability an eight out of ten.

We have around ten users in the organization. The product serves only the environment where we install the agent for each client. We have almost 2000 clients. I rate the product’s scalability a nine out of ten.

The implementation is easy. It took three to four hours.

Since we are a government organization, money is not an issue. There's an agreement between the Ministry of Communications and Information Technology and Microsoft.

I will recommend the tool to others. It is helpful for organizations. Overall, I rate the tool a nine out of ten.

Microsoft Configuration Manager gives different tools in one solution. 

The tool's deployment is complex and depends on the architecture you want to implement. 

The solution is stable.

The tool is scalable. 

I rate Microsoft Configuration Manager a ten out of ten. 

SCCM is used in the insurance and public administration sector. We have various sized customers using it.

We are using the solutions for PC application inventories, patch management for new PC installation, PC reinstallation, and zero-day patching. We're using it to its full capabilities. It's a complete solution in the Microsoft environment.

SCCM has made it easy for our organization to personalize all the distribution schedules and how we want to distribute. It is very easy to manage, and there is a lot of option.

The most valuable feature of SCCM is the application distribution.

SCCM can improve on third-party application support.

The next features are coming through their newer solution Microsoft Intune or Microsoft Endpoint Configuration Manager (MECM).

I have been using Microsoft System Center Configuration Manager (SCCM) for approximately 15 years. 

SCCM is stable.

The scalability of SCCM is good, it can scale a lot. You can manage a very small environment and go up to a couple hundred thousand PCs.

The support we have received from Microsoft was excellent.

I did not use another similar solution to SCCM.

The SCCM deployment difficulty level and time frame are dependent on how large the deployment is. If it is a large company then it can be complex. It can range in time from a couple of hours to a couple of days to a couple of weeks.

SCCM is an old on-premise solution. We're moving through to MECM and that is a cloud-based solution to do similar functionality, such as Intune. SCCM is used at its most. We will not increase the use of SCCM.

We are consultants and we do all of the implementations of SCCM for our customers.

The number of staff we need for maintaining the solution depends don't the size of the company, but usually, we have two to three people.

The ROI has been very good from SCCM.

The price of SCCM depends on the size of the organization. The price is competitive.

I rate the price of SCCM a three out of five.

We did not choose SCCM. It's a solution that evolved, and at one point it changed its name.

My advice to others is to plan ahead and make sure to take into account everything that the solution can do because if you do not understand what the product can do, you will probably buy a lot of software to do what the solution is already doing. Understand all the features and how you will be able to use them.

The next features are coming through Microsoft Intune.

I rate Microsoft System Center Configuration Manager nine out of ten.

The most valuable feature of Microsoft Endpoint Configuration Manager is patch management.

Microsoft Endpoint Configuration Manager can improve by allowing us to schedule the scripts, we don't have a script scheduling option and have to do it manually. 

I have been using Microsoft Endpoint Configuration Manager for a couple of years.

Microsoft Endpoint Configuration Manager is a stable solution.

The scalability of Microsoft Endpoint Configuration Manager is good.

The support can be responsive but other times can be a little slow.

The rate support from Microsoft Endpoint Configuration Manager an eight out of ten.

I have not used another solution other than Microsoft Endpoint Configuration Manager.

The initial setup of Microsoft Endpoint Configuration Manager was simple.

We did the deployment of Microsoft Endpoint Configuration Manager in-house. We have our maintenance of the solution automated.

Microsoft Endpoint Configuration Manager is a complete solution for what we need it for, and I would recommend it to others.

I rate Microsoft Endpoint Configuration Manager an eight out of ten.

Microsoft Endpoint Configuration Manager is used for ingenuity and automation.

The configuration of Microsoft Endpoint Configuration Manager could be improved, it is a bit complicated.

I have been using Microsoft Endpoint Configuration Manager for a few years.

The stability is very good.

Microsoft Endpoint Configuration Manager is very scalable.

The support from Microsoft Endpoint Configuration Manager is good, they are friendly.

The initial setup of Microsoft Endpoint Configuration Manager is straightforward. The time it takes for the process depends on the environment, typically it can take one day.

There is not a license needed to use the solution. 

I rate Microsoft Endpoint Configuration Manager an eight out of ten.

We are using Microsoft Endpoint Configuration Manager in our organization for patch deployment. Additionally, we deploy and manage Microsoft antivirus solutions to most of the desktops and the servers which we have.

I have been using Microsoft Endpoint Configuration Manager for approximately 

The solution is stable.

Microsoft Endpoint Configuration Manager is scalable.

I have used this solution in a couple of banks I have worked in.

The technical support is good.

The installation was not too difficult.

We use consultants to do the implementation and they were trained by Microsoft.

For enterprises, there is an annual license required to use this solution. The price of the solution could be cheaper. However, this is mostly because of the exchange rate from the dollar to the Nigerian currency.

I would recommend this solution to others.

I rate Microsoft Endpoint Configuration Manager a nine out of ten.

SCCM is used to manage both users, and your devices. It's an administration tool used for endpoint protection.

I would like to see more automation.

I have been using SCCM for three years.

We are using the 2019 version.

SCCM is a stable solution.

I have not scaled with this solution. I use it for a specific reason.

I have never contacted Microsoft technical support. I use our internal support.

I was not involved in the installation of this solution.

I would recommend this solution to others who are interested in using it.

I would rate SCCM a seven out of ten.

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.

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.

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.

I have been using SCCM for ten years.

We were using some of the older versions.

The stability is only as good as your infrastructure.

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.

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.

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

I have integrated it with Grafana.

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.

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.

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

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.