diff --git a/articles/deploying-crowdstrike-with-fleet.md b/articles/deploying-crowdstrike-with-fleet.md
index bc11b59191..dd4dd178c4 100644
--- a/articles/deploying-crowdstrike-with-fleet.md
+++ b/articles/deploying-crowdstrike-with-fleet.md
@@ -17,6 +17,8 @@ Your CrowdStrike **Customer ID** can be found on the Sensor download page in the
 
 The **Customer ID** _must be collected_ during the installation to activate the Falcon application. Adding the platfom-specifc scripts below as a post-install action to the uploaded CrowdStrike Falcon custom package settings in Fleet will allow the host on which the application has been installed to collect the **Customer ID** for activation in the CrowdStrike tenant. 
 
+![Add software advanced options](../website/assets/images/articles/fleet-crowdstrike-post-install-script-800x450@2x.png)
+
 >For reference, Crowdstrike Falcon scripts and install documentation can be found at: https://github.com/CrowdStrike/falcon-scripts
 
 ## macOS
diff --git a/website/assets/images/articles/fleet-crowdstrike-post-install-script-800x450@2x.png b/website/assets/images/articles/fleet-crowdstrike-post-install-script-800x450@2x.png
new file mode 100644
index 0000000000..177a9f1ac0
Binary files /dev/null and b/website/assets/images/articles/fleet-crowdstrike-post-install-script-800x450@2x.png differ