Endpoint Security, CrowdStrike, Installation via Munki & SCCM
Endpoint Services-specific information about installing CrowdStrike via Munki and SCCM.
System Center Configuration Manager (SCCM) Current Branch
Munki Mac Endpoint Management
University of Illinois IT Pros leveraging Technology Services CrowdStrike
University of Illinois IT Pros leveraging Technology Services Endpoint Service SCCM Current Branch and/or Munki Mac Endpoint Management systems.
Manual installations and additional install parameters are covered in the knowledgebase article, Endpoint Services, CrowdStrike, Manual Installation and Uninstallation.
For SCCM stakeholders utilizing the Community management model:
Deploy CrowdStrike using a package found at “\Software Library\Overview\Application Management\Applications\MANAGED APPLICATIONS\CrowdStrike\*”.
For SCCM stakeholders utilizing the Organizational management model:
Due 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 organizational instances. Instead, IT Pros can copy the Community installer to their unit's folder within SCCM and modify the deployment type to include their unique CCID.
For both Community and Organizational models, IT Pros will want to disable the management of Endpoint Protection via the SCCM client for machines with CrowdStrike installed. Failure to do so will result in the SCCM Client Check failing. This can be accomplished by configuring the client setting "Manage Endpoint Protection client on computers" to "No". Please note that this will disable management and reporting pertaining to Endpoint Protection/Windows Defender.
macOS CrowdStrike deployments include a) the CrowdStrike base installer and b) a unit-specific license package. EPS provides the base installer at the UIUC repository level, but due to the fact that each unit has a unique customer ID checksum ("CCID" or "CID") for their specific CrowdStrike instance, units will be required to create their own license package. This should generally be a one-time task with which EPS can assist during initial provisioning into CrowdStrike. The unit license should be made an update for the base installer.
Steps to deploy CrowdStrike via Munki:
- Ensure your unit-specific license package is in your Munki repository. For stakeholders utilizing the Community instance, please contact EPS to request that a copy of the Community license package be placed into your unit's Munki repository.
- Add crowdstrike_falcon to the Managed Installs (or Optional Installs) section of your unit's Munki manifest(s), and run Managed Software Center. The installation will require a restart.
- On macOS 10.13.4 and above: after the restart, log in and follow the prompts to approve and load the CrowdStrike kernel extension. This step won't be necessary if the Mac is enrolled in Workspace ONE and has already received the kext.crowdstrike profile.
- On macOS 10.15, in addition to the above step, you will also need to grant full disk access in order for CrowdStrike to function properly. This step won't be necessary if the Mac is enrolled in Workspace ONE and has already received the fda.crowdstrike profile.See our KB article for instructions.
- Run Managed Software Center a second time to install the unit license; no restart is required this time.