Microsoft Configuration Manager Reviews

Microsoft is working on migrating the function of Microsoft Endpoint Configuration Manager to the cloud. Every week and every month there is something new that's happening to move to the cloud.

Microsoft Endpoint Configuration Manager is used for installing new workstations without the interaction of people, it does the deploying of workstations automatically. Autopilot is used for automatic deployment installations of workstations without IT support. We only have packages at home and we do not need a VPN to configure workstations from home.

The patching of inventory to patching of Windows and applications, such as Office, inventory of wiping security, deploying new software, reinstalling software, uninstalling software, and wiping the device. This is insecurity from Active Directory services, some functionality we are moving to a group policy.  By having less IT support you can handle more workstations.

The solution could improve the functionality for automating, license management. Additionally, more and better-looking reports are needed.

I have used Microsoft Endpoint Configuration Manager within the last 12 months.

Microsoft Endpoint Configuration Manager is a stable solution. We do not have a lack of production in my orgaization.

The solution is highly scalable.

We have two IT engineers using the solution.

Microsoft has high-level support, I only have good words to say about them.

I have used Zabbix previously. I was using Zabbix, its free tool. It's not for somebody who does not have knowledge of Linux. Zabbix is not for a regular Microsoft user to use.

The installation requires a lot of knowledge and experience. The whole process took us three months.

The license price could be reduced for Microsoft Endpoint Configuration Manager  They should make the price more affordable for smaller companies, most companies would be able to use the solution if it was priced better.  There are more people on this cloud because you don't have to have either a server room or an on-premise server. You can have one IT person handle this without any local infrastructure. 

You receive a license for Microsoft Endpoint Configuration Manager when you buy an EMS E3 license. 

I would recommend this solution to others.

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

Our primary use case of this product is for infrastructure, capturing all the configuration items within our infrastructure. I'm the configuration manager and we are customers of SCCM. 

I like that this solution captures all the devices in our infrastructure, quickly identifying those items based upon everything we've identified within the SCCM, as far as the proper nomenclature goes. Other things along those lines like serial numbers, and the location of things, it's all good stuff. The solution does exactly what it needs to do and in terms of being on the ITSM side of the house it just feeds into it. 

I'd like to see some cosmetic improvements on the user interface. 

I've been using this solution for two years. 

This solution definitely does what it's supposed to do. 

Microsoft does a good job as far as putting information out there for anyone to train themselves, especially if it's within their Microsoft Virtual Academy. I don't deal with the administrative side of the house, but we have Microsoft system engineers we can contact if we need. The support is sufficient, very responsive and easy to work with.

The initial setup was straightforward and took around five hours. It was carried out by the two administrators in the company. We also have people on the team who are familiar with SCCM.

I don't know much about the licensing structure but I believe everything is probably included within the package.

It's important to be aware of the capabilities of the software and all that it says it's designed to do, and to make sure that you educate yourself on the use of the software. 

I would rate this solution an eight out of 10. 

Our primary uses for this solution are packaging, imaging, and patching.

This solution has made life easy with respect to patching, compliance, and OSD.

With SCCM 2012 and SCCM 2016, it allowed users to install non-licensed products when required.

The most valuable features of this solution are Package deployment, Software Center, OSD Creation with Task sequence, and Patching.

This solution needs to be supported on all Operating systems.

This solution is used for vulnerability management. Our primary use case is for software updates, including ad-hoc and monthly updates, as well as security patches.

The whole purpose of vulnerability management is to help with mitigating any security threats that could be within the network. So this solution has helped because it is very valuable to have an overview of which devices and networks are not up to date, or have failed to update with a specific software update deployment.

A specific example is related to malware by the name of Coinminer. It is used by intruders to remotely mine cryptocurrency, using your computer resources. It consumes your computer's CPU and memory. By putting this solution in place and ensuring that the latest security patches are installed, you are no longer vulnerable to this virus. Your computer operates at an optimal speed.

In summary, you maintain security and the best performance of your systems.

The most valuable feature is the graphical-based status reports of software updates; showing successful and failed deployments. This gives you a quick overview of vulnerable computers that expose your network to risks of a security breach.

I would like to see an agentless version of the solution. An agent-based system is one where every computer on the network has to have a client installed in order to be able to report on it or deploy to it. In the case of this solution, you need to have the SCCM agent installed on every computer. To me, that is a weakness because if you don't have the agents installed in some computers, then you cannot reach them for the deployment of software updates.

An agentless system means that you don't need to have an agent installed on computers. You would simply sweep the network, see all live computers and deploy the updates be able to deploy updates. It is worth noting is that the installed agents open and run on specific ports in the computer. These may be used as launch pads for attacks; making your network more vulnerable to security breaches.

This is a stable solution. They release regular updates and upgrades, and they keep enhancing the features. I have not had any bugs that I would say were a challenge.

This solution is very scalable. As your network becomes bigger, you're able to accommodate more computers in terms of deploying the updates that you need to.

Microsoft technical support is fairly good, and I would rate them eight out of ten. They try to act promptly, but there are two issues that cause delays. The first is related to the difference in time zones, and the second comes about from the different levels of support licensing.

We did not use another solution prior to this one.

The initial setup for this solution is straightforward. It is a Microsoft-based product, and they usually have startup wizards. It is graphical, and the process of installation is self-explanatory. It is easy, even for a new user.

The initial setup, depending on whether it is a server and what tests have to be done, might take about two hours.

Once running, the time required for the deployment of updates varies depending on how many computers you are deploying to. If you have, say two thousand computers, then it will take approximately a week for all of them to be fully updated. This also depends on how regularly the computers are online. In cases where systems are frequently offline, it will take even longer. Once they come online, they get the deployment and update.

The first priority after installing the software is to gather all of the end-user devices. Make sure that they are all covered and up to date all of the time.

One IT administrator is enough to deploy and maintain this solution.

We handled the implementation and deployment ourselves.

The licensing is good because they have various options, depending on what you are looking for. There are one-year up-to three-year license contracts.

We did not evaluate options other than this one, from Microsoft. It is our company policy to run on Microsoft SCCM.

Since this solution is agent-based, computers without the agent cannot be reached on the network. In addition, non-Microsoft products are not supported. So if you have a mix of platforms like Linux and Mac OS, you'd be better off looking for an agentless solution and not SCCM.

Security is one of the big problems with Microsoft products, but usability is equally good. 

I would rate this product 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.

The best features that I really appreciated are software and application pushing, Microsoft patching with Wsus integration, O.S. deployment with PXE (with driver installation, latest patches and customization), mobile management with Intune Connector, file inventory on pcs, users statistic usage about applications, hardware and software inventory.

We had the opportunity to easily manage Microsoft patching deployment with Wsus role installed or maintaining Wsus infrastructure separated from SCCM.

In this latter case we created properly GPO and script to push patch centrally and with appropriate scheduling. At the same time mobile management with MDM ability and encrypting as well, software and application pushing and updating overriding security concerns and O.S. deployment was some of the top features that we really appreciated.
I appreciated Distribution points on the cloud and ability to publish on demandapplications for users groups.

In this case users could choose from software list to automatically install some missing application without asking directly to IT team.

I think that some improvements would be appreciated on application package deployment for whom that has not a deep scripting ability like me.

SCCM is an high CPU/memory conuming application and so it would be fine that Microsoft could improve performances.

I started utilizing SMS 2003 since 9 years ago, since 4 years ago I managed and directed differentsmigration projects and zero installations on corporate companies with CAS, Primary and Secondary Sites.

At the same time I utilized this product during daily operations like reporting, software pushing, Microsoft patching, mobile managemen with satisfaction

You should consider that this product is particularly complex and delicate at the same time and so, the most difficult thing, was related to find causes of any installation delay or misconfiguration

About stability I did not find any particular problem.

When I got some problems on internet is quite easy to find consistent answers.

The only thing that I did not appreciated it was the case that, if you do not have CAS, you can install only one primary sites and all other sites could be only secondary sites.

This problem could be solved installing CAS later but about secondary site upgrade I am not aware that they can be automatically updated to primary site without uninstallation and re-installation.

Customer service is very good.

Technical support is very good and there are a lot of documentation on internet to help you on deployment/usage too.

I utilized for a while PDQ, spiceworks and psexec too but they are not caomparable with wide SCCM options/features.

The first setup was quite complex but primarily due to wide capabilities of the product itself that need time to be customized.

It was implemented by an in-house team coordinated and managed from me.

In my opinion SCCM SP1 is great.

Setup and licensing was quite expensive as well at start up stage. When all procedures have been implemented like collections, application and packages, wsus automatically deployment, O.S preparation, mobile management policies, reporting day by day, time to be spent to manage it would be more limited but, considering the importance and quantity of activity done from SCCM it would be normal to have a lot of hours daily spent from a team to utilize this product (obviously it would depends on company too)

PDQ, Spiceworks, psexec, GPO, scripting…

SCCM is really great but you must consider that you will take a lot of time to manage it entirely.

You should consider that this product would be, in the future, more and more strategic for companies about security concerns, task automation and for your CV too.

I have a lot of guide and screenshot as well:

http://www.alessandromazzanti.com/search/label/SCCM%202012

Here is my blog link:

http://www.alessandromazzanti.com/

https://www.linkedin.com/in/mazzanti

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 this solution to deploy all of the packages to the workstations.

The scalability to deploy the package.

The App to upgrades to the server needs to be improved.

We have used SCCM for a couple of years.

We are using the latest version.

It's a stable solution.

It's a scalable product. We have 1,000 users in our organization.

We have plans to continue using this solution.

Technical support is fine. We have no issues with support.

The initial setup is straightforward. It's easy for us.

We have a team of four to deploy and maintain this solution.

We completed the installation ourselves.

It took one week to deploy and customize it.

We have to pay for a license.

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

I would rate this solution a nine out of ten.