Microsoft Configuration Manager Reviews

I use the solution to manage security and policies. 

The solution effectively handles inventory management, deployment, and reporting. 

The solution does not support remote devices so CMG is still required. 

I have been using the solution for six years. 

The solution is very stable. 

The solution is for ICCM so does not scale like a cloud application. It is intended for security, management, or device teams and not end users. 

Scaling is always available with a monetary investment. 

Technical support is pretty good. 

The complexity of setup depends many factors such as the number of sites or distribution points and whether they will be centrally administered. Proper planning and execution are important. 

Deployments of an ICCM server can take up to four weeks. 

The solution operates on a licensing model that can be expensive. 

Pricing is reasonable for small companies but large companies or enterprise environments require multiple licenses. 

The solution is very stable and robust with a longstanding reputation. It works well with Windows devices and offers good management for ICCM.

The cloud-based platform is a good option for managing only Android or iOS devices. 

I rate the solution an eight out of ten. 

Our primary use case for this solution is deploying endpoints, applications and updates for large companies. The solution is deployed on-premises and on cloud.

It has the ability to perform mass distribution which is valuable.

It needs to be able to load faster during deployment and the new release could include this ability. This will allow us to deploy critical collections with over 50,000 to 60,000 users simultaneously.

We have been using this solution for approximately ten years and are currently using version 2203.

The solution is stable.

The solution is scalable.

The initial setup was straightforward.

I rate this solution an eight out of ten. The solution is the best there is in the market today. A feature that could be included in the next release is its ability to load faster during deployment.

Microsoft has done a good job with authentication solutions, such as single sign-on, or open authentication.

The downside of Microsoft Endpoint Configuration Manager is it's an on-premise-based solution. With the pandemic coming on board the need to support users across the globe has increased. For a while, we would use the in-built Microsoft Teams screen sharing feature but the disadvantage of that is you cannot perform privileged access. Microsoft does not give you access to that. That's where you need cloud-based tools, such as BeyondTrust or Freshservice.

There are many aspects of this solution that can be improved, such as security.

The integration could be better with other software packages.

I have been using Microsoft Endpoint Configuration Manager for approximately three years.

Microsoft Endpoint Configuration Manager is a stable solution.

Having Microsoft Endpoint Configuration Manager available only on on-premise creates limitations. If you want the best scalability options then you will have to move to the cloud to a solution such as Microsoft Intune.

We have approximately 1,000 active endpoints using this solution.

Microsoft has a lot of support available for Microsoft Endpoint Configuration Manager. When we open a support ticket Microsoft solves them in the set out the time frame in the SLA.

We were using other solutions previously.

The installation is not easy. As with most on-premise solutions, they are not easy to install. Microsoft documentation is complicated and goes on and on. It's a lot to try to assimilate the information. With a cloud solution, it makes it a bit easier. However, even with Microsoft Endpoint Configuration Manager being on-premise with Intune, it's still not straightforward. The time the implementation took for us to complete was a couple of weeks with a five-person team.

In recent times, a lot of companies have begun to move away from Microsoft Endpoint Configuration Manager. The endpoint configuration is very convoluted to implement. In most companies, you need to have a very large dedicated team to manage the solution on the back end. 

A lot of companies are looking to cost savings. With the advent of cloud solutions, companies have the opportunity to receive a lot of cost savings. There are a lot of ITSM tools that will do asset management for you, change management, converged asset management, and updates. There are other ways to configure updates and deployment. The solution is a bit convoluted and expensive.

The price of Microsoft Endpoint Configuration Manager is expensive.

I have a very good idea of what my present workplace pays for this solution because it's usually a mixture of different solutions. For example, if you have an Azure P2 license, it tends to cover Microsoft 365 E5. We have a number of licenses. 

The licensing is typically paid monthly or annually as part of the agreement by the customer.

I would recommend this solution to others if you're an Azure-centric organization. If you have your workloads on Azure and are a Microsoft-based organization. For example, you have Microsoft servers, Microsoft endpoints, Azure workloads, BD VMs, Data Factory, and SQL.

I would advise others to use online help forums instead of Microsoft documentation because they can tend to be complicated and lengthy.

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

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.

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. 

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.

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

I've been using this solution for nine years.

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. 

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

We've had good experience with Microsoft technical support. 

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. 

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

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. 

I like its ease of use. It does what you need it to do, and it's a one-stop-shop for the company and for all your deployments. If you incorporate Intune into it, you can have both. You can bring your own devices and corporate devices, and everything runs out of SCCM and Intune.

They should improve their anti-malware policies like the SCEP policies. For instance, you can't have different policies for different servers, there is only one policy in all the servers, and everything is covered under that. 

For example, say you want to scan one group of servers on Saturday, and then you want to scan another group of servers on Sunday, you can't do that. You have to scan all your servers, a regular scan or a full scan, on the same day and at the same time. That's definitely one thing they need to resolve. 

In the next release, it would actually be nice if they included Apple products. It will also help if you can use Intune again. Their compliance reporting feature could also be better. They can maybe work a bit on that for patching now.

It would be better if SCCM came with the functions of Right Click Tools built-in. If SCCM would have all those functions already built-in, we won't have to go and spend $5,000, just as an add-in from another company to get those functions.

I have been dealing with SCCM for nine years.

I used to be the SCCM administrator for quite a big company that had 80,000 people. That's pretty much all I did all day, every day.

BigFix is the poor man's SCCM. It's for people that can't afford SCCM and for small and medium-sized businesses. There's nothing else out there that can do what it can do.

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

We are using it for software deployment. Our network team uses this solution. It is mostly our tier-two team. 

We're on the latest version.

Software deployment and WSUS are most valuable.

There should probably be better remote support. They should also continue to improve on patch management, patching, and creating or turning products in software into deployable apps.

We have been using this solution in our organization for ten years.

The version that we have is MEMCM, and it works fine.

I've had interaction with Microsoft support, and their support is fine. It is what it is. It is always nice if it is better, but I certainly don't have any complaints.

I don't look at it from an ROI perspective. It provides what we need. It is a critical piece of infrastructure. If you want to run networking and support devices, you have no choice. You have to have it.

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