{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":21308,"path":"integrate-applications/integration-hub/ms-endpoint.md","title":"Microsoft Endpoint Configuration Manager Spoke","bundle":null,"doc_type":null,"release":"australia","body":"\n# Microsoft Endpoint Configuration Manager Spoke\n\nThe Microsoft Endpoint Configuration Manager \\(MECM\\) spoke automates actions to manage user collections, device collections, devices, and application deployments.\n\n## Request apps on the Store\n\nVisit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).\n\n## Integration Hub subscription\n\nThis spoke requires an Integration Hub subscription. For more information, see [Legal schedules - IntegrationHub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf).\n\n## Spoke version\n\nMicrosoft Endpoint Configuration Manager spoke v1.10.2 is the latest version. For version history of the spoke, see [Microsoft Endpoint Configuration Manager spoke release notes](https://www.servicenow.com/docs/r/store-release-notes/store-integrationhub-rn-ms-endpoint-manager.html).\n\n## Supported versions\n\nThis spoke was built for Configuration Manager 2006, but may be compatible with later versions.\n\n## Spoke dependencies\n\nIf you’re having trouble installing the app, ensure that these dependent plugins are installed:\n\n-   Complex Object \\(com.glide.cobject\\)\n-   ServiceNow IntegrationHub Runtime \\(com.glide.hub.integration.runtime\\)\n-   ServiceNow IntegrationHub Action Step – PowerShell \\(com.glide.hub.action\\_step.powershell\\)\n-   ServiceNow IntegrationHub Action Template - Data Stream \\(com.glide.hub.action\\_type.datastream\\)\n-   ServiceNow IntegrationHub Action Step – JDBC \\(com.glide.hub.action\\_step.jdbc\\)\n-   ServiceNow IntegrationHub Action Step – REST \\(com.glide.hub.action\\_step.rest\\)\n-   ServiceNow Flow Designer - Dynamic Inputs \\(com.glide.hub.dynamic\\_inputs\\)\n\n**Note:** Some of these plugins are licensable features and need appropriate licenses, if used outside the spoke implementation. For information on licenses, contact your account manager.\n\n## Spoke subflows\n\nThe 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:\n\n<table id=\"table_pg2_xz3_srb\"><thead><tr><th>\n\nSubflow\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nCreate Collection\n\n</td><td>\n\nCreates a collection in Microsoft Endpoint Configuration Manager and creates corresponding records for the new collection in the MECM Collections table.**Note:** This subflow is executed by AI agents.\n\n</td></tr><tr><td>\n\nDelete Collection\n\n</td><td>\n\nDeletes the specified collection from Microsoft Endpoint Configuration Manager server and removes the corresponding records from the MECM Collections table.**Note:** This subflow is executed by AI agents.\n\n</td></tr><tr><td>\n\nAdd Target Collection to Application\n\n</td><td>\n\nAdds a target collection to the specified application in Microsoft Endpoint Configuration Manager and creates a corresponding record in the MECM Deployments table accordingly.**Note:** This subflow is executed by AI agents.\n\n</td></tr><tr><td>\n\nRemove Target Collection from Application\n\n</td><td>\n\nRemoves a target group from the specified application on Microsoft Endpoint Configuration Manager server and removes the corresponding records from the MECM Deployments table accordingly.**Note:** This subflow is executed by AI agents.\n\n</td></tr><tr><td>\n\nConfigure Collection\n\n</td><td>\n\nCreates a collection and configure it with specified Application ID in the Microsoft Endpoint Configuration Manager Portal.\n\n</td></tr><tr><td>\n\nCreate Software Configuration\n\n</td><td>\n\nCreates the software configuration record of the specified Microsoft Endpoint Configuration Manager application.\n\n</td></tr><tr><td>\n\nLook Up Collections\n\n</td><td>\n\nReturns the list of all instal or uninstall Collections associated with the given Microsoft Endpoint Configuration Manager Application ID.\n\n</td></tr><tr><td>\n\nRevoke Application\n\n</td><td>\n\nAdds a user or device to an uninstalled collection and then removes it from the installed collection in the MECM server.\n\n</td></tr><tr><td>\n\nLook up Configuration Data\n\n</td><td>\n\nRetrieves the configuration data for the requested item.\n\n</td></tr><tr><td>\n\nDeploy Application\n\n</td><td>\n\nAdds a user or a device to an installed collection and then removes it from the uninstalled collection in the MECM server.\n\n</td></tr><tr><td>\n\nDiscover and Store Data\n\n</td><td>\n\nFinds the data from the server and then updates the records in the Application, Collection, and Deployment tables.\n\n</td></tr></tbody>\n</table>**Note:** These subflows are available only when the [Client Software Distribution 2.0 application](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/csd-app-2.md) is installed.\n\n## Spoke actions\n\nThe Microsoft Endpoint Configuration Manager spoke provides actions to automate tasks when events happen on your ServiceNow instance. Available actions include:\n\n<table id=\"table_rg2_xz3_srb\"><thead><tr><th>\n\nCategory\n\n</th><th>\n\nAction\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td rowspan=\"2\">\n\nAdvanced Actions\n\n</td><td>\n\nLook up Device Collections Stream \\(Database\\)\n\n</td><td>\n\nRetrieves the device collection data from the MECM server using the Java Database Connectivity \\(JDBC\\) connection.\n\n</td></tr><tr><td>\n\nLook up User Collections Stream \\(Database\\)\n\n</td><td>\n\nRetrieves the user collection data from the MECM server using the JDBC connection.\n\n</td></tr><tr><td>\n\nApplications\n\n</td><td>\n\nLook up Applications\n\n</td><td>\n\nRetrieves the application data from the MECM server.\n\n</td></tr><tr><td rowspan=\"7\">\n\nDevice Management\n\n</td><td>\n\nLook up CMPivot Response by Operation ID\n\n</td><td>\n\nRetrieves CMPivot response from the MECM server.\n\n</td></tr><tr><td>\n\nLook up Device by ID\n\n</td><td>\n\nRetrieves the device data from the MECM server.\n\n</td></tr><tr><td>\n\nRun CMPivot Query\n\n</td><td>\n\nRuns the CMPivot query and retrieves the operation IDs from the MECM server.\n\n</td></tr><tr><td>\n\nRun MECM Script\n\n</td><td>\n\nRuns the MECM script and returns the operation ID from the MECM server.\n\n</td></tr><tr><td>\n\nLook up MECM Script by Name\n\n</td><td>\n\nRetrieves the Globally Unique Identifier \\(GUID\\) of the MECM script from the MECM server.\n\n</td></tr><tr><td>\n\nLook up MECM Script Response by Operation ID\n\n</td><td>\n\nRetrieves the MECM script response from the MECM server.\n\n</td></tr><tr><td>\n\nLook up MECM Script Execution Response\n\n</td><td>\n\nRetrieves the MECM Script Execution Response from the MECM server.\n\n</td></tr><tr><td rowspan=\"4\">\n\nData Management**Note:** These actions are available only when the [Client Software Distribution 2.0 application](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/csd-app-2.md) is installed.\n\n</td><td>\n\nLook up Configuration Data\n\n</td><td>\n\nRetrieves the configuration data from the requested item or software configuration.\n\n</td></tr><tr><td>\n\nPrepare Deployment Data\n\n</td><td>\n\nPrepares the deployment data for the requested item.\n\n</td></tr><tr><td>\n\nPrepare Revocation Data\n\n</td><td>\n\nPrepares the revocation data for the requested item.\n\n</td></tr><tr><td>\n\nStore Discovered Data\n\n</td><td>\n\nStores the applications and deployment data in the corresponding tables.\n\n</td></tr><tr><td rowspan=\"5\">\n\nDeployments\n\n</td><td>\n\nAdd device collection to application\n\n</td><td>\n\nAdds a Device Collection to a targeted application in Microsoft Endpoint Configuration Manager. **Note:** The application must have at least one deployment type and content distributed to a distribution point before deployment.\n\n</td></tr><tr><td>\n\nLook up Deployments\n\n</td><td>\n\nRetrieves the deployment data from the MECM server.\n\n</td></tr><tr><td>\n\nRemove User Collection from Application\n\n</td><td>\n\nRemoves a user collection from an application in the MECM.\n\n</td></tr><tr><td>\n\nAdd User Collection to Application\n\n</td><td>\n\nAdds a user collection to a targeted application in MECM. **Note:** The application must have at least one deployment type and content distributed to a distribution point before deployment.\n\n</td></tr><tr><td>\n\nRemove Device Collection from Application\n\n</td><td>\n\nRemoves a device collection from an application in MECM.\n\n</td></tr><tr><td rowspan=\"6\">\n\nDevice Collections\n\n</td><td>\n\nAdd to Device Collection\n\n</td><td>\n\nAdds the named device to the collection specified.\n\n</td></tr><tr><td>\n\nIs Device in Collection\n\n</td><td>\n\nChecks if a device exists in the device collection in the MECM server.\n\n</td></tr><tr><td>\n\nLook up Device Collections\n\n</td><td>\n\nRetrieves the device collection data from the MECM server.\n\n</td></tr><tr><td>\n\nRemove from Device Collection\n\n</td><td>\n\nRemoves the specified device from the collection in the MECM server.\n\n</td></tr><tr><td>\n\nCreate Device Collection\n\n</td><td>\n\nCreates a new device collection in MECM with a unique collection name.**Note:** Provide values for the following input fields:\n\n-   **Collection Name**: Mandatory input. Name of the collection that is a group of devices or users that you manage together.\n-   **Limiting Collection Name**: Optional input. An existing collection that will define which device can be the member of this new collection. Only the devices which are the member of Limiting collection can be added in this new collection. For device collections, default limiting collection is \"All Systems\".\n\n</td></tr><tr><td>\n\nDelete Device Collection\n\n</td><td>\n\nDeletes a device collection from Microsoft Endpoint Configuration Manager \\(MECM\\) by Collection ID, avoiding ambiguity from duplicate collection names.\n\n</td></tr><tr><td rowspan=\"6\">\n\nUser Collections\n\n</td><td>\n\nAdd to User Collection\n\n</td><td>\n\nAdds a user to a collection.\n\n</td></tr><tr><td>\n\nIs User in Collection\n\n</td><td>\n\nChecks if a user exists in a user collection in the MECM server.\n\n</td></tr><tr><td>\n\nLook up User Collections\n\n</td><td>\n\nRetrieves the user collection data from the MECM server.\n\n</td></tr><tr><td>\n\nRemove from User Collection\n\n</td><td>\n\nRemoves a user from a collection in the MECM server.\n\n</td></tr><tr><td>\n\nCreate User Collection\n\n</td><td>\n\nCreates a new user collection in MECM with a unique collection name.**Note:** Provide values for the following input fields:\n\n-   **Collection Name**: Mandatory input. Name of the collection that is a group of devices or users that you manage together.\n-   **Limiting Collection Name**: Optional input. An existing collection that will define which device can be the member of this new collection. Only the devices which are the member of Limiting collection can be added in this new collection. For device collections, default limiting collection is \"All Systems\".\n\n</td></tr><tr><td>\n\nDelete User Collection\n\n</td><td>\n\nDeletes a user collection from MECM by Collection ID, avoiding ambiguity from duplicate collection names.\n\n</td></tr><tr><td>\n\nSoftware Management\n\n</td><td>\n\nCreate Catalog Item\n\n</td><td>\n\nCreates a catalog item of the specified MECM Application.\n\n</td></tr></tbody>\n</table>## Spoke module\n\nThe MECM spoke adds the MECM application to your instance. The application includes the following modules and data accessed through the spoke modules stored in the respective tables:\n\n|Module|Description|Table|\n|------|-----------|-----|\n|Applications|Displays the list of applications from the Microsoft Endpoint Configuration Manager server.|Application \\[sn\\_ms\\_epcfgmgr\\_spk\\_application\\]|\n|Configurations|Stores the software configuration details for the applications.|Configuration \\[sn\\_ms\\_epcfgmgr\\_spk\\_sf\\_config\\]|\n|Server Instances|Stores the details of the servers provided.|Server Instance \\[sn\\_ms\\_epcfgmgr\\_spk\\_server\\]|\n|Deployments|Displays the list of deployments from the Microsoft Endpoint Configuration Manager server.|Deployment \\[sn\\_ms\\_epcfgmgr\\_spk\\_deployment\\]|\n|Collections|Displays the list of collections from the Microsoft Endpoint Configuration Manager server.|Collection \\[sn\\_ms\\_epcfgmgr\\_spk\\_collection\\]|\n\n**Note:** These modules are available only when the [Client Software Distribution 2.0 application](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/csd-app-2.md) is installed.\n\n## Connection and credential alias requirements\n\nIntegration 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.\n\nFor information about setting up the spoke, see [Configure Microsoft Endpoint Configuration Manager and set up the spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/csd2-conf-sccm.md).\n\n## MID Server requirements\n\nTo 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/integration-steps.md). For information, see [MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-server-landing.md).\n\nTo set up the MID Server for this spoke, see [Set up MID Server for a spoke](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/config-adv-mid-settings-for-oauth-on-mid.md).\n\n"}}