Microsoft Endpoint Configuration Manager Spoke
-
- UpdatedMay 20, 2025
- 4 minutes to read
- Yokohama
- Now Platform Capabilities
Microsoft Endpoint Configuration Manager Spoke
The Microsoft Endpoint Configuration Manager (MECM) spoke automates actions to manage user collections, device collections, devices, and application deployments.
Request apps on the Store
Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Integration Hub subscription
This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.
Spoke version
Microsoft Endpoint Configuration Manager spoke v1.8.1 is the latest version.
Supported versions
This spoke was built for Configuration Manager 2006, but may be compatible with later versions.
Spoke dependencies
- Complex Object (com.glide.cobject)
- ServiceNow IntegrationHub Runtime (com.glide.hub.integration.runtime)
- ServiceNow IntegrationHub Action Step – PowerShell (com.glide.hub.action_step.powershell)
- ServiceNow IntegrationHub Action Template - Data Stream (com.glide.hub.action_type.datastream)
- ServiceNow IntegrationHub Action Step – JDBC (com.glide.hub.action_step.jdbc)
- ServiceNow IntegrationHub Action Step – REST (com.glide.hub.action_step.rest)
- ServiceNow Flow Designer - Dynamic Inputs (com.glide.hub.dynamic_inputs)
Spoke subflows
The Microsoft Endpoint Configuration Manager spoke provides sample subflows to demonstrate automating tasks. To customize a sample subflow, copy it to the required application scope. Available sample subflows include:
Spoke actions
The Microsoft Endpoint Configuration Manager spoke provides actions to automate tasks when events happen on your ServiceNow instance. Available actions include:
Category | Action | Description |
---|---|---|
Advanced Actions | Look up Device Collections Stream (Database) | Retrieves the device collection data from the MECM server using the Java Database Connectivity (JDBC) connection. |
Look up User Collections Stream (Database) | Retrieves the user collection data from the MECM server using the JDBC connection. | |
Applications | Look up Applications | Retrieves the application data from the MECM server. |
Device Management | Look up CMPivot Response by Operation ID | Retrieves CMPivot response from the MECM server. |
Look up Device by ID | Retrieves the device data from the MECM server. | |
Run CMPivot Query | Runs the CMPivot query and retrieves the operation IDs from the MECM server. | |
Run MECM Script | Runs the MECM script and returns the operation ID from the MECM server. | |
Look up MECM Script by Name | Retrieves the Globally Unique Identifier (GUID) of the MECM script from the MECM server. | |
Look up MECM Script Response by Operation ID | Retrieves the MECM script response from the MECM server. | |
Look up MECM Script Execution Response | Retrieves the MECM Script Execution Response from the MECM server. | |
Data Management Note: These actions are available only when the Client Software Distribution 2.0 application is installed. |
Look up Configuration Data | Retrieves the configuration data from the requested item or software configuration. |
Prepare Deployment Data | Prepares the deployment data for the requested item. | |
Prepare Revocation Data | Prepares the revocation data for the requested item. | |
Store Discovered Data | Stores the applications and deployment data in the corresponding tables. | |
Deployments | Look up Deployments | Retrieves the deployment data from the MECM server. |
Device Collections | Add to Device Collection | Adds the named device to the collection specified. |
Is Device in Collection | Checks if a device exists in the device collection in the MECM server. | |
Look up Device Collections | Retrieves the device collection data from the MECM server. | |
Remove from Device Collection | Removes the specified device from the collection in the MECM server. | |
User Collections | Add to User Collection | Adds a user to a collection. |
Is User in Collection | Checks if a user exists in a user collection in the MECM server. | |
Look up User Collections | Retrieves the user collection data from the MECM server. | |
Remove from User Collection | Removes a user from a collection in the MECM server. |
Spoke module
Connection and credential alias requirements
Integration Hub uses aliases to manage connection and credential information, and OAuth credentials. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection.
For information about setting up the spoke, see Configure Microsoft Endpoint Configuration Manager and set up the spoke.
MID Server requirements
To use these actions, your instance must have a MID Server set up and configured to use PowerShell. For more information about running actions on the MID Server, see Integration steps. For information, see MID Server.
To set up the MID Server for this spoke, see Set up MID Server for a spoke.