The scalability of Microsoft Endpoint Configuration Manager is great. We are able to extend the solution to multiple site locations.

The solution can scale well. We weren't surprised about anything. It does what needs to be done. 

MECM has impressive scalability. It can support up to 150,000 devices, and if you require more, you can simply add another primary site. This scalability is as advertised, and I have experience working in a large environment. I would rate it 9 out of 10. 

We have only one primary site server for the entire agency in all our different sites across all the computers. Adaptiva does all our heavy lifting as far as moving data across the network. Thus, our scalability is fine.

I would rate the scalability as 10 out of 10.

The solution is highly scalable.

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.

In terms of scalability, I believe there's room for improvement. While SCCM is capable of handling our current needs effectively, scalability could be enhanced to accommodate future growth and larger deployments.

It is a scalable solution and better suited for big companies.

I rate MECM eight out of 10 for scalability.

Microsoft Endpoint Configuration Manager is very scalable. We probably have 150,000 users right now.

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

The solution is scalable.

The tool is scalable. 

We have approximately 10,000 users using the solution.

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

The scalability of Microsoft Endpoint Configuration Manager is good.

It is scalable, but we are far from reaching that limit. We don't have any problem with its scalability.

We have three people working on the SCCM side. In terms of the implementation, we have 6,000 PCs that have this installed. It is being used daily.

The scalability is excellent. 

To improve scalability across on-premises and cloud environments, Microsoft introduced Intune which is a service implemented with MECM in the cloud in order to provide communication with devices in remote locations. So if you need to manage remote devices with MECM, you can do so by buying the Azure tenant service, and attach it to your MECM.

In total, we are using MECM and Intune to configure almost 2,000 devices across the company.

The solution is scalable. 

Microsoft Endpoint Configuration Manager is a scalable solution.

The scalability of SCCM is good, it can scale a lot. You can manage a very small environment and go up to a couple hundred thousand PCs.

No. SCCM has the ability to be as big or as small as needed by the business. It can be used by businesses ranging from single office companies to massive international corporations.

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

The solution is scalable.

We have 100,000 people using the solution.

We are utilizing the solution on a regular basis.

I rate the scalability of Microsoft Endpoint Configuration Manager 

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 have found the solution to be scalable. We have around 50,000 users using the solution.

We have clients in both the private and public sectors. 

The solution requires fine-tuning and configuration tweaks. In order to scale it, you will need a knowledgeable person to manage the process.

The solution is scalable to match our needs.

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.

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.

The solution is scalable.

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.

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

SCCM is highly scalable.

In terms of scalability, at that time I didn't need to scale the development. However, in the near future, it is possible. I don't have any idea of the timeline for our scaling the solution as I focus on VMware technology at this time.

Our company has around 60 users. However, we offer this solution to one of the enterprise customers that use it for bank data centers. They have around 3000 staff.

We are using the System Center to manage around 2000 virtual machines.

It scales, but it gets expensive. If you're looking to do - and this is something I hear they're changing in one of the future versions - built-in HA, high-availability, right now you have to use Microsoft clustering. So you have to buy Microsoft clustering to make it highly available. 

As far as load balancing across, they don't have that support yet, so that you can actually build multiple primaries and have it load balance across. They don't have any of that functionality yet. That would be a nice feature, to scale that way. The way they have designed SCCM is to put the load in the offices. You put secondary sites out there where you put DPs on the sites and they pull from the local site, not from across the LAN. That helps with the load, it doesn't really hit the primary server.

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. 

A company can easily scale this product if they need to.

You can scale it up if you need to. You can add the client servers, for example. I've had multiple primary sites that I get as I go. A company that needs to scale can do so with relative ease.

We deal with companies that are often medium-sized or enterprise-level.

This is a scalable product. The biggest group that I have been involved with was maybe 15,000 people. Typically, the sizes are in the 1,000-person area and it's not the type of product that you put together and configure for an office.

The scalability of Microsoft Endpoint Configuration Manager is good.

The solution is highly scalable.

We have two IT engineers using the solution.

It's a scalable product. We have 1,000 users in our organization.

We have plans to continue using this solution.

This solution is very scalable. As your network becomes bigger, you're able to accommodate more computers in terms of deploying the updates that you need to.

The scalability of SCCM is good but now that it is on the intune platform, it's even better.

The usage and how extensively it is being used depends on the client and the client's roadmap.

The only thing that I did not appreciated it was the case that, if you do not have CAS, you can install only one primary sites and all other sites could be only secondary sites.

This problem could be solved installing CAS later but about secondary site upgrade I am not aware that they can be automatically updated to primary site without uninstallation and re-installation.

I have not scaled with this solution. I use it for a specific reason.

We are running almost 5,000 machines, and it was working fine from a performance perspective. 

I can't really say that the scalability is good or bad because I haven't had to do much of it.

I cannot say anything about its scalability at this time. We are still exploring this solution. We are using SCCM for the server, so only IT people use it or log into it. In terms of nodes, about 500 nodes are using the product effectively.

Everyone in our organization uses SCCM, as it's on all of the device endpoints. There are two to three people that have access to the SCCM  servers. 

The scalability is very easy. If a company needs to expand it to more endpoints they can do so easily.

The scalability is quite good.

We don't have a separate team using it. It's an operations team, where everyone works in every technology.

There are about 5 - 10 people using it - Windows server persons, applications teams, and other teams.

No issues with scalability.

Microsoft Endpoint Configuration Manager is very scalable.

Microsoft Endpoint Configuration Manager is scalable.

I have used this solution in a couple of banks I have worked in.

SCCM does not scale well, which is one of the reasons we are not going to continue to use it.

We have six people in our organization who are using it.

Currently, our business is really stable, and there is no need to increase the devices in our organization. We have six technicians who are using it currently.

The solution is scalable. We do have options to integrate other products as well. You want to combine your MDM solution with SCCM, for example. Scalability is something I would give them five stars for.

As admins, we do have rules for distributing. Basically, to manage inventory on all those steps. In our current organization, we are connected to approximately 300 million servers.

The solution is very scalable. If an organization needs to scale up, the can do so easily using this product.

Right now, we have about 4,000 users on the solution.

The scalability is good.

This is a scalable product. We have approximately 1,000 users and we plan to continue using it into the future.

We do not have any issues with scalability.  

We use the solution for a user base of approximately 500. It is scalable.