Microsoft Configuration Manager Reviews

I am using Microsoft Endpoint Configuration Manager for patch management and asset inventory.

The most valuable feature of Microsoft Endpoint Configuration Manager is it's incredibly simple to configure and execute changes in bulk, allowing for seamless deployment. With this solution, you can easily track the status of all modifications and send them with ease, making it a comprehensive and efficient solution for any necessary adjustments.

The assets have reached their end-of-life, and patching them is a complex and laborious task. It would be highly advantageous if there were an integrated solution that provided distinct options for each end-of-life asset, streamlining the process and facilitating comprehension.

I have been using Microsoft Endpoint Configuration Manager for approximately one and a half years.

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

We have approximately 10,000 users using the solution.

I rate the scalability of Microsoft Endpoint Configuration Manager a ten out of ten.

I use Tanium in parallel with Microsoft Endpoint Configuration Manager. Tanium is a similar solution that has features, such as asset patching, and encryption, and can be configured around Microsoft assets.

The initial setup of Microsoft Endpoint Configuration Manager is simple.

There is an annual license needed to use the solution.

This tool is helpful for Microsoft assets but it is important to have clear visibility before implementation. It can be a complete solution but a plan.

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

We use this solution to apply new group policies.

The solution was particularly helpful for patching the OS, and for the VM in our environment. With 10 branches, we have a huge number of VMs. Using ECM, we can download the new patches one by one, apply and then restore them. It saves us a lot of time. 

The valuable feature is the ability to gain all the data you need. We can collect data and get insight into the functionalities of their scope. As system administrators, we get a summarized report for each site with the installed version of the OS for all PCs in our environment. We know which meet the requirements and which don't. For those that don't, we can mitigate any potential vulnerabilities or threats.

I think managing Linux devices could be improved. It would help our colleagues and other departments like the dev opps, who only use Linux machines to quickly patch their VMs.

I've been using this solution for two years. 

The solution is stable. 

The solution is scalable. 

The technical support could be improved. 

The initial setup is very straightforward. We have six users. 

It's important to keep the database going at all times to avoid any interruption of the service. The implementation must be very well designed because you have to know the scope of your workload and that should be addressed in the action plan before proceeding with the deployment. 

I rate this solution eight out of 10. 

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. 

This is a diverse tool so its use case varies. Most people use it for patch management and software distribution, and operating system deployment. It can also be used for policy management and for maintaining a baseline on the computer, depending on the company and its goals. We are consultants and resellers and deploy this solution on the cloud and on-prem. We use Azure for our cloud deployments. I'm a consultant and president and CEO of our company. 

The solution enables significant streamlining and reduces resources from a personnel perspective.

Patching is very effective and reporting is very good. In general, the software distribution and operating system deployment are very good. Most organizations with small support resources leverage it, along with the Azure Autopilot component or the Intune Autopilot component. The customer orders the solution, it's shipped to them, they open it, log on with their Azure credentials and it builds the machine for them as opposed to going to an imaging center, and having a dedicated staff for that particular function. 

I think the asset management component, the TSM piece, could be improved. That would allow them to compete with other products. It's currently very basic and rudimentary because there are no other connectors such as PeopleSoft that you can get.

I've been using this solution for 24 years. 

This is a very mature product so it's very stable. In the 24 years I've been using it, most of the kinks have been worked out. It's all about having a healthy network and a healthy, active directory structure. If those two things are in place, you'll have a really good experience. If not, it will definitely show its head in the SCCM product. 

The scalability is excellent. 

Technical support for SCCM is good. You have to get past the tier one person, but once you get to a dedicated MECM engineer, it's good. The support forums are also helpful. 

If the solution is being deployed by someone with experience, it can be done in about two hours. They're pretty good with hydration kits where you can configure all the prerequisites and all the components, and you're up and running in about two clicks. It's the customer and budget that dictates how complex or how involved a setup is. If they're only leveraging a couple of the core features of the product, it's pretty straightforward, but if they want to use more advanced functions and distribute that out and do low balancing and that sort of thing, it takes a little more time. Generally, clients allow us to integrate for them, we conduct a turnkey training solution, and then they take it over.

Although the solution is not as expensive as Ivanti, the cost is still quite high. Certain licensing arrangements can get you a better deal, but it's still expensive. It's based on a CAL license, so if you have a client on an endpoint, there's going to be a charge. I think it's around $US35 per license per year. It's not too bad. 

If you're new to the solution then it's worthwhile studying the documentation because it's not easy in terms of all the components that make it up such as SQL and so forth. 

I rate the solution nine out of 10. 

The tool's most valuable features are easy patch management and software deployment. We use it because it is a Microsoft product, which makes it more secure and easier to use.

Microsoft Configuration Manager makes it easier to control remote desktops. It supplements other products. 

The tool's deployment can be cumbersome. 

Microsoft Configuration Manager's stability is very good. I rate it an eight out of ten. 

We don't contact Microsoft directly for support. We get support through a third-party vendor. 

I rate the product's ease of deployment a four out of ten. 

A contractor helped us with the product's deployment. 

I rate the overall solution an eight 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. 

The primary use case of the solution is to deploy patches, and applications, and upgrade our client operating systems.

Without the solution, we would have to manually install all patches and software and upgrade our operating system with the help of our support team, which would take a long time. With SCCM, this process is automated, making it a highly valuable feature.

The most valuable feature of this solution is its ability to deploy patches to nearly all applications.

SCCM should strive to enhance the accuracy of its reporting functions in order to avoid any issues with incorrect or inaccurate data.

Microsoft could supply an installation guide to make setup easier.

I have been using the solution for ten years.

The solution is stable and we have not had any issues.

The solution is scalable.

We have 100,000 people using the solution.

The technical support is good. We can call the hotline or use the website to generate the tickets.

Positive

The initial setup is straightforward.

I give the solution a nine out of ten.

Maintenance for the solution is easy.

I recommend the solution to others.

We mostly use Microsoft Endpoint Configuration Manager for patch management and application deployment. We will check and post a critical or supplement patch if there is a vulnerability.

I like Mircosoft's technical support. Microsoft has a few updates, like some of the critical KBs. They are published within the interval time, and in case of an escalation on the client missions, we will raise a ticket with the Microsoft team. They will create a hotfix or a critical update. They will chat with us, and that is one thing I like about Microsoft. Whenever any issues occur at my organization, they will help you out soon as possible within the SLA.

It would be better if automation options were available. For example, in Nexthink or SysTrack, there is an analytical tool. Creating dashboards would be very easy if you implement the same thing in Microsoft. That report will be a daily cost to the customers and good revenue for our organization. The price also could be better.

In the next release, we need to include some features like tables, dashboards, surveys, services, and metrics in the dashboard. Whatever we are implementing will be downloaded by a report. Apart from the report, we will telecast from the dashboard. It's very easy to compare, and it will be easy to telecast to the end-users.

I have been using Microsoft Endpoint Configuration Manager for five years.

Microsoft Endpoint Configuration Manager is a stable solution. There is nothing to worry about. When Microsoft pushes updates or patches, they will be in the W-Sync server. We have some people who will concentrate on Sync's parameters. Apart from that, everything is perfect.

Microsoft Endpoint Configuration Manager is a scalable solution.

From my point of view, I'm just giving 60% to 70% marks to those who support us with these issues. If there are any new issues, they will check in with the corresponding team, which takes some time. If there are issues with a single machine or server, or it affects the whole environment, they will analyze it from their end and provide a hotfix.

On a scale from one to five, I would give Microsoft technical support a four.

Positive

I would tell potential users that for 15,000 or 30,000 machines, you must go with Microsoft Endpoint Configuration Manager as it's the best tool. We can install the clients on all the end-user machines. All the data will be recorded in the Microsoft console itself. There's no need to worry if the patching activities will be hygienic, which will be very useful. 

You can go with another third-party software if you're just a small organization with 50-odd machines. The Microsoft license cost is relatively high, but everything will be perfect, stable, and reliable.

The initial setup is straightforward because Microsoft is always user-friendly. They will share the parameters, like troubleshooting steps and the pre-request. They will send the database knowledge-base document to us. It will be a step-by-step procedure. There won't be any worrying or alarming issues with Microsoft. If we have any problems, we will raise a ticket with Microsoft, and the team from Microsoft will help us. We can implement this solution within two or three hours, depending on the bandwidth speed.

On a scale from one to five, I will give the initial setup a four.

We implemented this solution.

The price could be better.

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