Skip to content

Commit f9e530b

Browse files
authored
Update README.md
1 parent c1bebb3 commit f9e530b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ TenantName="" # Display name for tenant (for logging)
5353
############################################################################
5454
```
5555
So why this method is working like this? in Microsoft Defender there is a library upload limit, somthing like 10MB, so you can't upload the Crowdstrike sensor to the Defender library and just deploy it. so this method make it work.
56-
1. This part your are doing on your own Linux host, not the host you want to deploy Crowdstrike on, so start by editing the script, change `Operation` to "Split" `Parts` to "6" and `OriginalFilePath` to the sensor path.
56+
1. This part you are doing on your own Linux host, not the host you want to deploy Crowdstrike on, so start by editing the script, change `Operation` to "Split" `Parts` to "6" and `OriginalFilePath` to the sensor path.
5757
2. Run the script, and upload the 6 parts to Defender library and then upload them from Defender library in to the host. (the default library upload path on Defender is "/var/opt/microsoft/mdatp/response")
5858
3. Edit the script to "Deploy" and fill in the rest of the information, and run the tool again, deploy mode is not only rebuilds the sensor it is also automatically initiates a sensor installation
5959
And that's it, now you have CrowdStrike on this host.

0 commit comments

Comments
 (0)