Microsoft Configuration Manager Reviews

We use this solution because we need to manage patching and system provisioning.

This solution helps us by automating the patching of our system. We are able to standardize our Windows configuration, and models are supported through imaging.

The most valuable features of this solution are:

• Imaging - standardized Windows builds
• Software deployment - deploying updates and automating the installation of software
• Patch deployment - increased security
• Reporting - better view of our environment for decision making

This solution should be simpler, and more consistent across modules/sections.

Reporting and collection queries should be made easier to do.

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.

We use this solution for image and software deployment.

It wasn't very user-friendly.

The reporting is not very good.

It was hard to effectively manage with one person.

I have been using SCCM for ten years.

We have version 2012.

It's a stable product. In terms of our experience with any bugs, glitches, or crashes there were not more than what is normal for Microsoft.

SCCM does not scale well, which is one of the reasons we are not going to continue to use it.

We have six people in our organization who are using it.

I have not had any contact with technical support.

Previously, I did not use another solution. SCCM was the only one that we used while I was there.

The initial setup is complex.

You need more than one person to manage the environment.

We are currently evaluating some EDR alternatives.

I would not recommend using this solution. I didn't really like anything about it. In general, I am not a fan of Microsoft.

I would rate SCCM a four out of ten.

We use it for deployment purposes, for all managing all the devices and patching. It has performed very well.

The benefits of SCCM is that in the deployment, we can deploy one like machine with it without an alias, it also gets the management capability of all devices that are dispatched or not.

It deploys all the bare metals using PXE and it gathers all of the information of the device using a discovery, whatever it is in the domain and we can schedule the deployment according to our need. It's a flexible tool. 

It has many features. It generates our reports as well, provides compliance reports, monitors the dashboard and now it has the Cloud Management Gateway. It's awesome! 

In addition, there are improvements. There are new features like App-V and Core Management. The Core Management allows us to move to the cloud as well as with our own premises infrastructure. It can manage the Internet Appliance without exposing the infrastructure to the cloud.

Sometimes it does not update the log files. It gives an error code, rather than giving the actual problem.

The stability is good. 

The scalability is good.

We only use SCCM and MDT. I really do not have experience with anything else.

The setup was complex and I faced a lot of problems initially because I was new to the solution.

If you need only deployment purposes, and no management capability, then use MDT also. And if you want to deploy many devices and manage those devices, then go for SCCM.

The primary uses are PC imaging, application deployment and updates, Windows patching, and baselining.

Using SCCM has sped up PC deployment, made it much more consistent through automation, and provided a self-service application portal that users can go to and install software themselves without admin rights.

The most valuable features are application deployment and task-sequenced imaging.

The operations could be faster and you need some patience with this tool. I  wish that sending media to remote distribution points was faster.

I have been using SCCM for 15 years.

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.

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

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.

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.

I have been using the product for approximately two years.

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

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

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.

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.

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

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.

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.

My primary use case is for the product is mainly for helping with competitive analysis. It is not my main solution but it is one of the components.  

The most valuable part of the solution in my case is patch management.  

I would like to see Microsoft extend the coverage of the product to integrate better with other platforms beyond Windows.  

I have been using SCCM (System Center Configuration Manager) for about eight years now.  

The stability of the product is good.  

We do not have any issues with scalability.  

I have not had the need to contact technical support for any reason so I have no real experience with them.  

I also use BigFix by HCL Technologies (Hindustan Computers Limited). I use these products to check between SCCM and BigFix to see if they agree.  

On a scale from one to ten where one is the worst and ten is the best, I would rate System Center as an eight-out-of-ten.  

Primary use case is for Windows Desktop Operating System configuration management, primarily for fully automated operating system deployment. We use it for additional Microsoft operating system and application update delivery and malware reporting for 300 laptops/desktops distributed across eight international locations. We also use it for configuration management and update management for Windows Server operating systems.

Configuration Manager has standardised updating and application delivery across the organisation.

• Automation of operating system, application, and update deployments - Massively reduces IT operations effort.
• Desired configuration management – Enables identifying undesirable changes to corporate computer equipment and desktop applications.
• Configuration reporting - Reduces the effort involved in annual software inventory and meets any ad-hoc computer reporting needs.

It would be of benefit if Configuration Manager could be connected/integrated with multiple Microsoft Intune subscriptions rather than just one (the current limit).

I cannot think of any other improvements, as the product has been full-featured for any use we need to put it to, especially since the Current Branch releases.