Microsoft Configuration Manager Reviews

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.

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. 

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.

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.

We use Microsoft Endpoint Configuration Manager for application deployment, patch deployment, and many other things. If you have any script that needs to be deployed to all the devices, you can do it with this solution. 

If you have this solution in your environment, it's a win-win situation. You can deliver anything that the customer requires. If the efficacy is somewhere around 80 to 90%, everything isn't well because some devices aren't coming online because of bandwidth issues or they aren't compliant. 

However, if we have 80% to 90% efficacy, we can achieve compliance. The compliance we reached was around 95%, but that 5% was probably due to a decommissioned device or one that wasn't in the environment. So, for efficacy, delivery, and reporting, this is one of the best tools.

The major features of this product are the reporting tools. The most valuable features are package deployment and application deployment. Security management is also good because any vulnerability will be identified, and you can fix it. It's the best tool because you never know what kind of client you will have. For example, you may have your offices in low bandwidth remote areas. But it's achievable because it accommodates the bandwidth that you have available.

Microsoft Endpoint Configuration Manager is an excellent reporting tool for your environment. If you want to know the details about the hardware configuration, software configuration, what is causing a problem, or when a new feature update comes in for Windows, even that goes on SCCM itself. A lot of deployment stuff.

It would be better if reporting were more user-friendly. I would like to see an upgrade in the reporting structure in the next release. At the moment, you have to use an SQL query or configure it to pull reports through the graphical user interface. 

Their updates could be more regular. I think Mircosoft updates it every six months. They are also moving many things to Intune, and Microsoft decided to move the deployment solution there. I think SCCM is getting old, and Intune is new. 

I have been working with Microsoft Endpoint Configuration Manager for about seven years.

Microsoft Endpoint Configuration Manager is very stable. It's very reliable, and it's a proven product.

Scalability is difficult for the inexperienced. But if you know how to use these tools, scalability is also good. When Intune matures, you can also use it together with Microsoft Endpoint Configuration Manager to scale and co-manage the environment.

Microsoft support is good, but it does take time. There are two types of support provided by Microsoft, paid and unpaid. The paid option offers a real-time system, and they help because we have to pay in dollars. Sometimes it takes two or three days to get to the submission. I cannot comment much because we only had a few cases and had to connect with them. Usually, these issues are related to some upgrades and some tool-related issues. Although it's good, I think Microsoft support could be better because they still take too much time.

The deployment process is very simple. It's not difficult because it gives you a variety of features. You have to create a collection or a group, and you deploy it. It's very slow and dependent on the network. 

A single person can install and deploy this solution. If you have an application already created and tested, that's fine. If you do not have one, then you have to build the application and test it. If everything goes fine, you can simply deploy it to the list of people you want to target. I wouldn't say that you need many people, but it depends on your operation and how you manage your environment.

The deployment time depends on the location it's going to, the bandwidth, and more. You can configure a time for the application to replace the policy or when the machine will replace its policies in the configuration settings. Suppose I'm an administrator and deploying something on your device; your machine will not get turned on. I will go ahead and update the application evolution cycle and machine policies so that it happens automatically. Once the 30 minutes clock starts, it'll update, and once it refreshes, it will see something I sent, and it'll start downloading it. 

Downloading is always completely dependent on how fast your internet is. Once the package is downloaded, you can simply go ahead and install it. Small packages will take about an hour at most to deploy. For bigger packages, it's completely dependent on the internet because this tool does only one job. It's like a postman as it takes one thing from you and gives it to the other person.

There are periodic updates, and the maintenance is also done. The patch update service is critical and has a significant impact.

Microsoft Endpoint Configuration Manager is suitable for small businesses. If you have fewer offices and fewer users, then the efficacy of this product is very high. If the company doesn't have a system for a long time or doesn't have many employees or environmental issues, they can open Intune and have a cloud-based solution and get all the features together there.

You can stage your content, and you can share where you have no connectivity. You can go ahead and do the whole deployment and a lot of things. Intune is still improving, but SCCM has a feature of all this deployment and all other things.

So I would say that SCCM has a stronghold and is still relevant. It's an excellent product, but Intune will take it over in a few years. But not entirely because they will coexist. They are working in an environment simultaneously, hand in hand, but I think the market will move more toward Intune (if it's not moving already).

I would advise potential users to take a structural approach. They should know the customer's requirements, the number of users, and the locations. They need to have the setup, create a cache, and then binary and secondary options for these deployments. But if you're using a cloud-based solution, you don't have too much worry about it because everything will come from the internet. 

On a scale from one to ten, I would give Microsoft Endpoint Configuration Manager an eight.

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. 

We use this solution to test out VMs.

The ability to make collections and deploy to them has been great.

The ability to integrate MDM would be great.

We just set up our lab, so we've only been using this solution for three months.

So far, we've had no issues with bugs or glitches. 

SCCM is highly scalable.

I have not had to contact technical support.

As someone who is quite familiar with IT, the initial setup was quite straightforward. It would definitely be complicated if you're not familiar with IT.

Presently, I am using a free trial version. 

I really like SCCM. I am constantly learning new things all the time. So far, it seems pretty straightforward.

It's a good product designed for medium to large-sized environments that need to automate their deployments and set them in an organized manner.

Overall, on a scale from one to ten, I would give this solution a rating of eight.

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.