Failure to do so may result in the MECM client becoming unresponsive, becoming non-compliant in the MECM Client Check, and generating errors in log files. Be sure to include your unit's CrowdStrike instance CID in the request.Īdditional information on CrowdStrike management models can be found here.ĭisabling MECM Endpoint Protection Managementįor both Community and Named/Self-Managed models, IT Pros will want to disable the management of Endpoint Protection via the MECM client for machines with CrowdStrike installed. Instead, IT Pros should submit an MECM support request to have a copy of the application placed in their unit folder. See the 'Disabling MECM Endpoint Protection Management' section below for additional information.įor MECM stakeholders utilizing the Community management model:ĭeploy CrowdStrike using a package found at “\Software Library\Overview\Application Management\Applications\MANAGED APPLICATIONS\CrowdStrike\*”.įor MECM stakeholders utilizing the Named or Self-Managed management model:ĭue to the requirement of providing a unique customer ID checksum ("CCID" or "CID") for your unit's specific CrowdStrike instance at the time of installation, EPS cannot package a global installer that will work out-of-the-box for Named/Self-Managed instances. Be sure to disable MECM's management of Windows' endpoint protection prior to deploying CrowdStrike to your endpoints.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |