Patch My PC Feature and Application Request
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
Will be useful as there will be frequent updates.
Please reach out to Crowdstrike and perhaps as a partner they will give you access to sensor builds and documentation. The sensor package just needs to know each customer's unique CID for initial install and the bulk maintenance token for upgrades.
Automatic installation
To automate silent installations on many devices, including installations using a deployment tool such as Windows System Center Configuration Manager (SCCM), complete these steps.
Use Google Chrome to download the sensor installer from Host setup and management > Deploy > Sensor downloads.
Copy your customer ID checksum (CCID) from Host setup and management > Deploy > Sensor downloads.
Run or configure your deployment tool to use this command, replacing
<installer_filename>with the name of the install file you downloaded, and<CCID>with the CCID from step 2 :<installer_filename> /install /quiet /norestart CID=<CCID>For information about these parameters and their functions, see Appendix A.
Sensor upgrades with uninstall protection enabled and cloud updates disabled
Use this upgrade path if you don’t use cloud updates and want to automate silent sensor upgrades on uninstall-protected devices. You might manage installations using a deployment tool like Windows System Center Configuration Manager (SCCM).
Use Google Chrome to download the sensor installer from Host setup and management > Deploy > Sensor downloads.
In the sensor update policy you want to update, turn on Bulk maintenance mode. Make sure the Sensor version updates off build version is selected and Uninstall and maintenance protection is turned on.
Retrieve the bulk maintenance token to include in the deployment package. This token doesn't change, so you don't need to modify your deployment package each time you enter bulk maintenance mode.
Run or configure your deployment tool to use this command, replacing
<installer_filename>with the name of the install file you downloaded:<installer_filename> MAINTENANCE_TOKEN=<bulk maintenance token> /install /quiet /norestartFor increased security, turn off bulk maintenance mode after completing your upgrades. This restores the per-sensor maintenance token and disables the bulk maintenance token.
Appendix A: Installer parameters
This is a complete index of all parameters that the Falcon sensor installer accepts.
All installer parameters are case-sensitive.
Some parameters require a leading slash, and some require no leading slash.
Installation parameters
Parameter
Description
CID=0123456789ABCDEFGHIJKLMNOPQRSTUV-WXYour Customer ID Checksum, which is required when installing.
/installInstalls the sensor (default).
/passiveShows a minimal UI with no prompts.
/quietShows no UI and no prompts.
/norestartPrevents the host from restarting at the end of the sensor installation.
GROUPING_TAGS=Assigns user-selected identifiers you can use to group and filter hosts.
ProvToken=Optional security measure to prevent unauthorized hosts from being accidentally or maliciously added to your customer ID (CID).
BILLINGTYPE=Sets the sensor to use standard billing or Pay-As-You-Go billing.
BILLINGTYPE=Default: standard billing per sensor
BILLINGTYPE=Metered: Pay-As-You-Go billing
Sensor startup parameters
Parameter
Description
NO_START=1Prevents the sensor from starting up after installation. The next time the host boots, the sensor will start and be assigned a new agent ID (AID). This parameter is usually used when preparing master images for cloning.
VDI=1Enable virtual desktop infrastructure mode.
Proxy parameters
Parameter
Description
Usage
APP_PROXYNAME=<Proxy FQDN or IP>APP_PROXYPORT=<Proxy server port>Configure a proxy connection using both a proxy address (by FQDN or IP) and a proxy port.
Cannot be used with the
PACURLparameter.PACURL=<PAC file URL>Configure a proxy connection using a PAC file.
Cannot be used with the
APP_PROXYNAMEandAPP_PROXYPORTparameters.PROXYDISABLE=1By default, the Falcon sensor for Windows automatically attempts to use any available proxy connections when it connects to the CrowdStrike cloud. This parameter forces the sensor to skip those attempts and ignore any proxy configuration, including Windows Proxy Auto Detection.
ProvNoWait=1The sensor does not abort installation if it can't connect to the CrowdStrike cloud within 20 minutes (10 minutes, in Falcon sensor version 6.21 and earlier). (By default, if the host can't contact our cloud, it will retry the connection for 20 minutes. After that, the host will automatically uninstall its sensor.)
Use this parameter when upgrading to version 3.5 or later if you use IE proxy detection for Falcon, because proxy data will not be available until another user logs into the host.
ProvWaitTime=3600000The sensor waits for 1 hour to connect to the CrowdStrike cloud when installing (the default is 20 minutes).
Use this to install the sensor on hosts that require more time to connect to the CrowdStrike cloud.
In Windows sensor version 6.22 and later, this parameter is usually only used by request from our Support team. It’s typically not needed because the sensor can complete installation even if all channel files can’t be downloaded.
Troubleshooting parameters
Troubleshooting parameters
Description
/?Show help information for the installer.
/repairRepair the sensor installation.
/log log.txtChange the log directory to the specified file.
MAINTENANCE_TOKENAn optional single-use security token used when uninstalling or installing sensors.
Apps without public download URLs or are behind a paywall or login present challenges for us at PMPC as we don't always have access to the downloads. This particular app may be better suited for our Custom Apps feature.
push push push lol
Please please please :)
Yes, please! The frequent updates to this app really do cause a struggle.
The unique company CID is a command line parameter at install time, so it would be added in the console.
This is a simple MSI install that all paremeters get passed to. Utilizing the current deployment methods PMPC has in place right now would work 100%.
Ps. The only part that work work for it is the uninstall, as this you would need a unique code per machine.
Bump
Just curious, the install for the CS agent has a unique code tied to firm account. I am not sure if having installation package will work without that code. The version update may be more useful as long as it doesn't override the firm code.
We can also provide installation scripts we currently use and validate it on SCCM and InTune. We currrently push it out via InTune.
Hi. It would really help us out if you can add CrowdStrike Falcon Sensor to ConfigMgr Apps deployment. We use SCCM to deploy applications, but CrowdStrike does not have .MSI instructions, only .exe. We can provide anything you need from CrowdStrike (latest sensor download, instructions, etc.) Thanks
Any update on this?
What if one of us provided you with the EXE file?
Can this be possible with the local content repo?
Hi Adam, I have a CrowdStrike contact for you if you would like to work directly with them. Please message me.
Here is the idea I posted on Crowdstrike's portal https://eu-1.ideas.crowdstrike.com/ideas/IDEA-I-7811
Hi Adam, I have opened a case with Crowdstrike if you would like to provide Patch My PC contact info I will push to reach out to you and work on this.
Just to give you all an update, we're currently trying to source the software from the vendor. Unfortunately so far they haven't been very cooperative but we will keep trying.
Also will not work if write protection is enabled
Upvoting because the console does a poor job of updating from older versions, and because sometimes it straight up fails to update. The folks who run the updates, I suspect, are often different than those who manage the Falcon console.
But you still have to do the initial deployment. Having it built and updating the installer automatically would be a nice improvement.
what Rob Gura said.