What is your primary use case for Microsoft Endpoint Configuration Manager?

We use the solution for remote control, patch management, and software deployment.

We use the solution to monitor our servers and clouds. We also use it for software and hardware inventories.

We primarily utilize SCCM for deploying and updating applications across our network. This includes managing crucial Windows updates to ensure our systems are up-to-date and secure.

Microsoft Configuration Manager helps with patch management.

We use Microsoft Configuration Manager for patch management.

We utilize it for tasks such as ongoing OS patching, application deployment, configuring services, making adjustments to conferencing settings, comparing configurations across different systems, and implementing security measures, among other things.

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

We were replacing SCCM. It's been easy enough to do in terms of getting the devices and seeing what's being discovered from that type of info. We're looking for hardware and software data coming across.

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

We use MECM for intelligent logic automation. About 400,000 users are impacted by the solution, but there are around 20 admins who work with it directly. We have multiple automation tools and use the one that makes sense as needed.

We use it to manage our enterprise desktops and laptops. Most of our enterprise computers are managed using this platform, but we also include some mobile devices. It allows us to manage our desktops effectively with policies in place. I estimate that over 50% of our laptops are managed using this platform.

The primary use case of this solution is the application and device management for any windows desktop and mobile device clients.

I use the solution to manage security and policies.

First off, to clarify some confusion, Microsoft recently changed the name of a previous on-premises tool called SCCM (Microsoft System Center Configuration Manager) to MECM (Microsoft Endpoint Configuration Manager). In our company, we originally used SCCM with all our Microsoft products, but after a while, many companies including ours started to move their on-premises devices to the cloud, and MECM, along with Intune on an Azure tenant, became our preferred solution for managing devices that are both on-premises and in the cloud. I worked with a team to complete the upgrade of our SCCM solution to the current version of MECM, which we now use exclusively to deploy software packages, scripts, updates, and operating systems via task sequences. Then, after buying an Azure AD tenant, we took out a license for Microsoft Intune (now part of MECM), in order to link our use of MECM for managing devices that exist on the internet, such as in the case of teleworkers.

The primary use case of the solution is to deploy the computers and servers.

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.

Microsoft is working on migrating the function of Microsoft Endpoint Configuration Manager to the cloud. Every week and every month there is something new that's happening to move to the cloud. Microsoft Endpoint Configuration Manager is used for installing new workstations without the interaction of people, it does the deploying of workstations automatically. Autopilot is used for automatic deployment installations of workstations without IT support. We only have packages at home and we do not need a VPN to configure workstations from home. The patching of inventory to patching of Windows and applications, such as Office, inventory of wiping security, deploying new software, reinstalling software, uninstalling software, and wiping the device. This is insecurity from Active Directory services, some functionality we are moving to a group policy. By having less IT support you can handle more workstations.

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.

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.

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.

We use SCCM to access user data.

We use this solution to deploy all of the packages to the workstations.

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 use this solution to test out VMs.

In most cases, it is used by us to deploy software or manage configurations of certain applications. We are pushing the WSUS updates through it and getting the normal systems grouping. You can do your software package through it and you can create and run scripts.

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.