Microsoft Configuration Manager Reviews

It is used only for endpoints. We are trying to decide if it is useful for server-based evaluation as well. Like everybody else, we want to track what software is deployed. We have a one-half deployment of this product now, and I'm not sure if it's useful for what we want to do, which is server-based. It is designed to detect any PC. Thousands of people are using it this way, and it's not a new thing, but some people also seem to use the product for server-based detection, and it looks like there are modules you can download for Linux and other things to make it work beyond just the endpoint, which is what I am after.

It works well for the endpoints for the customer I'm consulting. It has a bunch of knobs, and you can tune it to do lots of things. 

It is designed to detect any PC. You can do it agent-based, or you can do it by some other method. If it is agent-based, then as long as the PC has the Endpoint Manager agent on it at the time when the batch job runs, it detects the hardware and software and puts it in the database. 

I'm looking for a single solution for all discovery needs. It fulfills about 40% of the requirements, and I'd like to see the other 60% so that I don't have to keep doing this.

I've been consulting in this space for five years. It has been used by the customer for years.

I don't have enough data on that. While I've been observing it, it has been stable.

When you buy it, you license it with a total number of devices to be managed, and that's a wall. When you hit the wall, you're going to need more licenses. So, you can scale right up to the spot where you have hit your boundary on licensing. To that boundary, it scales just fine.

I don't have any experience with their support.

This client uses seven or eight different things to perform this function of discovery. They use two different things for networks, and they use a hodgepodge of things to track VMware and Virtual Data Images (VDIs) and basically back of the envelope to track things that are on servers.

As far as I know, it is an annual operating expense license.

You may need complementary products to handle the holes not envisioned by SCCM.

For what it was designed to do, I would rate it a nine out of 10.

We primarily use the solution for patch management, application deployment and operating system deployment.

It has improved our ability to remediate against critical CVE's in a timely manner across the enterprise.

The patch management is great. The ability to be able to centrally purchase servers is quite useful.

The ability to monitor only after you have rebooted devices allows you to see if they have compliance or not.

The efficiency - as opposed to patching once you have the time - of having a central repository to manage everything you need is very helpful.

The solution is quite stable. 

It's perfect for enterprises.

We have found the scalability to be quite good.

In terms of the monitoring, the timeframe it takes to actually report back on the compliance of a device after it has been patched is a bit too long. That could be better. Sometimes you could be looking at a screen and may take about five to 10 minutes before you get back the actual compliance status and that could be reduced.

Having a cloud solution is better in a lot of ways. For the deployment of the operating system, with InTune and modern end-point management, you no longer have to image machines and waste a lot of hours. You no longer have your technicians spending four, five hours imaging machine sessions for drivers and things like that. You can make use of an autopilot, which reduces resources and can cut down the timeframe drastically. There's a lot of wins with the cloud technology that's coming forward, that enterprises and organizations can make use of.

I've used the solution over the three years. It's been in our organization for the past six years.

It's a very stable product. It is definitely an enterprise-grade patch management solution.

The product is very scalable. When we have migrations and we bring on additional devices, such as during an acquisition of companies, it's great. We can bring them right into our environment. It's very scalable in terms of deploying and adding a new division to the solution. 

Currently, we have it deployed to support over 20,000 PCs.

Likely, we will increase usage. There are also new tools that are modern tools that we are starting to make use of. As much as you're doing something for patch management, where you need to enter the discussion is you need to start looking at modern endpoints, which is InTune, for example. We will start making use of InTune for the patch of end-points. We could also do scheduling of those patches as well from the cloud to the client. We are using, a hybrid approach. Generally, our goal is to expand usage.

In terms of technical support, once you have a Microsoft agreement, the level of support would be the same across all our products. We have an enterprise-grade level of support. Therefore, once I create a critical case, I get support within the hour. We are quite satisfied.

We have had a deployment in our enterprise for more than five years. It's a relatively complex deployment due to the fact that we have a large organization.

I am one of the enterprise engineers. I make deployments happen at a new location and it may just be a matter of training the onsite technician at that new division on how to make use of it. We have an enterprise-grade deployment and we have divisional deployments where divisions can make use of it to still manage their in-house shops.

A consultant would've assisted in the initial deployment.

We do pay a licensing fee on a yearly basis. 

There is a license cost and it is licensed per deployment. We do pay licensing costs for all of the deployments that we have on our end, across the enterprise.

With the way everything is moving to the cloud, you need to have all of these licenses in place.

We're partners with Microsoft.

For people looking into implementing Configuration Manager at this point, I would recommend it. They should also look at InTune, which is more of an endpoint deployment. For the servers, you can still look at what we have, however, just the way, how things are developing, I can see the industry and patch management moving away from on-prem management to more like making use of the cloud and use of our Microsoft for business in terms of managing the updates, ease of updates and things like that. What is happening now is a paradigm shift.

I'd rate the solution at an eight out of ten. It's great for enterprises.

The on-premises useability is very good.

The solution is stable. 

For the most part, for our needs, the scaling is fine.

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.

We have used the solution for the past decade. It's been around ten years at this point.

The solution is stable. There are no bugs or glitches. It doesn't crash or freeze.

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.

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.

We are trying to transition from SCCM to Bigfix.

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.

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.

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.

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.

Microsoft Configuration Manager helps with patch management. 

The tool's deployment is difficult. Microsoft needs to improve documentation with videos. 

I have been working with the product for ten years. 

Microsoft Configuration Manager is stable. We have experienced downtime from time to time. 

We use the tool's free license. It is expensive. 

I rate Microsoft Configuration Manager a six out of ten. 

We use Microsoft Configuration Manager for patch management. 

The product has improved time and security. 

Microsoft Configuration Manager is integrated with other Microsoft products. 

The product needs to improve scalability. 

I have been working with the product for three years. 

I rate Microsoft Configuration Manager a nine out of ten. 

I rate the tool's scalability an eight out of ten. 

The tool's deployment is easy. It takes between five to 25 minutes to complete. 

I rate Microsoft Configuration Manager a nine out of ten. 

I am using Microsoft Endpoint Configuration Manager for software distribution and patch management.

The most valuable feature of Microsoft Endpoint Configuration Manager is the software deployment. Additionally, Microsoft integrates most of the other solutions well with one another.

The support could improve.

I have used Microsoft Endpoint Configuration Manager for approximately five years.

We are utilizing the solution on a regular basis.

I rate the scalability of Microsoft Endpoint Configuration Manager 

The availability of technical support could improve.

I rate the support from Microsoft Endpoint Configuration Manager as seven out of ten. 

Neutral

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

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

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

The primary use case of this solution is the application and device management for any windows desktop and mobile device clients.

The most valuable feature is the restriction of data transfer between unmanaged applications and managed applications, specifically on mobile devices. For example, if a user wants to transfer data from email to WhatsApp, that can be restricted.

The solution can be improved by speeding up the synchronizing of the policies on the devices. Technical support can benefit from shortened response times and making sure all of the support team are at par with their knowledge regarding the solution.

I have been using the solution for four years.

The solution is stable. We currently have seven to nine thousand users.

The solution is scalable to match our needs.

The technical support team's response time can be slow at times and some people are more knowledgeable than others depending on who you have assigned to the ticket.

Neutral

The initial setup is straightforward. I give it an eight out of ten for ease.

The price is competitive and reasonable. I would give the solution an eight out of ten on price.

I give the solution a nine out of ten.

The solution doesn't require any maintenance from our end because it is a cloud-based solution and Microsoft takes care of everything. 

The solution is easy to integrate with the durations and application, and administration is also very simple. When you go with the combination of licenses, the cost is also good, and reasonable.

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.