Microsoft Endpoint Configuration Manager is stable.

It is stable. It's reliable. There are no bugs or glitches. It doesn't crash or freeze. 

I would rate it six or seven out of ten.  There have been significant issues in the past, particularly over the last three years. Sometimes, the activities we attempt to implement are not entirely successful, and they end up being ignored. Achieving a full implementation success rate of 100% is challenging; typically, we reach about 90-95%. It requires substantial effort and diligence to get everything working as it should, highlighting the need for improvements in this regard.

The stability on SCCM is fine. However, we are still on Windows 7 with some computers on Windows 10, neither is better nor different with SCCM. 

It seems as if SCCM will only work if the WMI Database and its health on a computer is working properly. If it breaks, then the SCCM client doesn't work. It's not a function of SCCM because the WMI Database is part of the Windows operating system. The SCCM client relies on the Windows OS, but something will break on its own (anywhere from one to five percent of the computers), and we are always chasing this down.

I would rate the stability as 10 out of 10.

The stability is good.

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

I rate SCCM around an eight for stability. It has proven to be a reliable tool for application management and deployment within our organization.

The product is very stable compared to older versions. The configuration is easy to upgrade, and if there is a problem with a combined server, the user can roll back to a previous version. Additionally, there are many tools available for covering different aspects of the product, which makes it a very important configuration.

I rate MECM nine out of 10 for stability. 

Microsoft Endpoint Configuration Manager is stable.

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

The solution is stable.

The solution is stable.

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

Microsoft Endpoint Configuration Manager is highly stable.

Its stability is quite good, and its performance is quite good. There is nothing to complain about.

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. 

MECM is stable. However, whenever Microsoft makes changes or updates to the workstation operating system (Windows 10, for example), you also have to adapt your version in the server accordingly. So, in future, if you're going to be deploying Windows 11, you will also need to upgrade your version of Windows in MECM. This means that you are always thinking about which versions of operating systems you have in your workstations as well as which versions you have in MECM.

You have to do such maintenance every six months, where you need to consider the versions of operating systems while upgrading and testing to see if they are compatible with your MECM. On the whole, it ends up being a lot of work.

The solution is stable. 

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.

SCCM is stable.

Improperly set security settings can lead to console performance issues. SCCM client issues are also inevitable. We recently had to diagnose and fix downloading issues caused by older BranchCache issues with the old client. Otherwise, the client and server are very stable.

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

I rate Microsoft Configuration Manager a nine out of ten. 

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

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

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

The solution is stable most of the time.

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

We don't have very many issues in SCCM. It's not a plug and play software, however. From time to time it does require fine-tuning. You need the right management and administrative people in place to manage the product. This is essential in order to keep it running correctly.  

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

Microsoft Endpoint Configuration Manager is a stable solution.

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

The solution is stable.

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

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. 

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

The solution is extremely stable. We've only really had to restart the solution twice in the first year. It's very reliable.

We've had no stability problems at all. Things have been running great for a year, we haven't had any real issues with the system itself. We've had to tweak some things like everybody does, some registry keys here and there, but there has not been a stability problem at all.

The solution is very stable. 

The solution offers good stability. there are no bugs or glitches. It's reliable. It doesn't crash or freeze. The performance overall has been very good.

The solution is quite stable. We haven't really dealt with bugs or glitches. It doesn't crash or freeze. It's reliable.

SCCM has no issue with stability.

Microsoft Endpoint Configuration Manager is a stable solution.

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

It's a stable solution.

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

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.

The stability is only as good as your infrastructure.

About stability I did not find any particular problem.

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

SCCM is a stable solution.

It is not always stable. When it works it works, but It has a very sensitive database and it almost always crashes when we use it, especially if you don't take care of it.

It's constantly running alongside computers. When they are on, SCCM is on. It's a stable product. There aren't issues with it crashing or getting glitchy. There is no issue, we have not faced any issue with SCCM.

The stability is also quite good.

It is stable. We haven't experienced crashes for the last four or five years. Since Windows Server 2012, crashes are literally nonexistent.

The stability is very good.

The solution is stable.

It's a stable product. In terms of our experience with any bugs, glitches, or crashes there were not more than what is normal for Microsoft.

It is stable. When the applications are set up correctly, we didn't face any major problems. Most of the problems are related to DNS and other things that are outside of SCCM. They are not related to SCCM.

The stability is very good. We don't have any issues with it. It's very reliable. I'd give it five stars.

The solution is very stable. It's reliable. You don't have to work about bugs or glitches. There aren't any crashes. It doesn't freeze.

The stability is good. 

I haven't had any problems with stability.

The stability of the product is good.  

The solution is stable enough to manage your Windows operating system.