What is your primary use case for SCCM?

I use the solution to manage security and policies.

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.

SCCM is used in the insurance and public administration sector. We have various sized customers using it. We are using the solutions for PC application inventories, patch management for new PC installation, PC reinstallation, and zero-day patching. We're using it to its full capabilities. It's a complete solution in the Microsoft environment.

We are using Microsoft Endpoint Configuration Manager to manage our client's Microsoft estate.

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.

Microsoft Endpoint Configuration Manager is used for ingenuity and automation.

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.

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

It is used for software deployments, PC operating system deployments, and security patch deployments. Currently, we are using it on-premises, but we are slowly moving to the cloud solution that is called Intune or Microsoft Endpoint Management (MEM).

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.

We are using Microsoft Endpoint Configuration Manager in our organization for patch deployment. Additionally, we deploy and manage Microsoft antivirus solutions to most of the desktops and the servers which we have.

SCCM is used to manage both users, and your devices. It's an administration tool used for endpoint protection.

We use it and our clients use it for device patch management, servers, and management processes. We deploy it for clients but we don't usually maintain it for them.

We use this solution for image and software deployment.

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.

This solution helps to manage different areas. For example, asset inventory and software inventory. You are able to patch products, do software deployment, and software packaging.

We are using Microsoft SCCM as the deployment platform for our environment to deploy laptops and PCs for the help desk technicians. We also use it to deploy applications and servers and provide some reports to the organization about what is currently deployed. We are using its latest version.

We primarily use the solution for patch management.

We have just implemented a patch management solution. We are using SCCM for the server. For the client or endpoint, we are using a different product called Ivanti.

SCCM does everything from A to Z for a Windows operating system. It provides a full-featured deployment for Windows-based systems from the setup screen.

We are using SCCM to manage the virtual machine configuration. We had around 100 or 200 virtual machines and wireless, and we need to configure different settings on all of the virtual machines. We need to handle patching, updating, and installing security updates. We prefer to use System Center instead of other solutions like GFI LanGuard that are already installed in other environments.

The primary use case for SCCM is for managing workstations. All of the software that runs on our workstations is packaged and distributed and managed. Along with that, some of our security software is managed a little bit differently, but is accounted for in that way. We also use it for keeping track of our patches.

Our main use is, first of all, to update the patches and to push the patches from SCCM, to check systems software, and to see which software is installed along with the systems. These are the major three things that we use on SCCM. We are on the endpoint side. We just ensure that the SCCM agent is installed appropriately. I have an on-site server also. There are the primary servers, and then there are site servers of SCCM. I have a site server also. With the site server, I have to make sure it is working and there is no hardware level or any other issue on these machines. This site server is replicating with the main servers in our data center. Due to the fact that we have different sites in different locations including the UAE, Oman, and other sites, there are other site servers, that are replicating with the main servers. They may be taking other information from SCCM as well.

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 am a system administrator and I use the System Center Configuration Manager for test deployment and Windows update.

My primary use case is for the product is mainly for helping with competitive analysis. It is not my main solution but it is one of the components.

We primarily use the solution for client and server deployments, and software deployments, as well as software metering.

We primarily use the solution for client management, especially for day-to-day operational activities, like access management or software deployment.

Our primary use case for this product is for patching and sending back packages to the client.

The primary uses are PC imaging, application deployment and updates, Windows patching, and baselining.

We have an environment of eight thousand machines and eleven thousand users.

Our primary uses for this solution are packaging, imaging, and patching.

We use this solution for implementing System CenterConfigMgr in our organization, and for standardization.

We use this solution because we need to manage patching and system provisioning.

This solution is used for vulnerability management. Our primary use case is for software updates, including ad-hoc and monthly updates, as well as security patches.

We use it for deployment purposes, for all managing all the devices and patching. It has performed very well.

It's mainly end-point management, right imaging, patching,and third-party application.

We primarily use it for deploying software and software updates, such as monthly Microsoft updates. We also deploy images and collect our computers' inventory (in regards to what software is being installed) along with their configuration. I have been using the product for approximately 22 years, when it was still called SMS. My first product version was SMS 1.1.

Systems management, inventory, pushing out deployment, and patching. It has multiple purposes.

* Application deployment * Software metering * Batching

Primary use case is for Windows Desktop Operating System configuration management, primarily for fully automated operating system deployment. We use it for additional Microsoft operating system and application update delivery and malware reporting for 300 laptops/desktops distributed across eight international locations. We also use it for configuration management and update management for Windows Server operating systems.

Our Windows environment has about 100 servers, Windows 2012/2016, and more than 500 desktop and laptop computers with Windows 7/10. We use SCCM 2012 mainly for installing and deployment of images for new operating systems on end-user computers, for application management, distribution of new applications, software and hardware inventory, remote assistance, application virtualization and, of course, for software updates on servers and workstations.

We use System Center Configuration Manager (SCCM) to manage workstations and servers in our Windows environment. We are primarily a Windows-only environment, which is what SCCM is designed to manage. It uses WMI underlying technology to ensure that it is compatible with all versions of Windows, from Windows XP to Windows 10. We use it to manage our Windows workstations and Servers. We use SCCM to do many things, like deploy operating systems, deploy applications, configure settings, gather compliance data, enforce software patching and run reports for software installations information. We do not use it to do Mobile Device Management, though it does have that capability. It does not manage products outside of Microsoft operating systems, so this product would be for Microsoft-heavy businesses.