Problem overview
Deploying Prey manually across multiple Windows devices can be time-consuming and prone to errors. This automation simplifies the process by using a Level custom field to store the API key, ensuring a seamless, secure installation without manual input on each device.
When any of these happen
Prey Tag Applied
With conditions
Perform these actions
Install - Prey Anti-Theft
With conditions
Prey Install Failed Alert
With conditions
This automation installs Prey on Windows devices using a predefined API key stored in a Level custom field. It can be executed manually or triggered automatically by tagging a device with “Prey.” The installation script references the stored API key, ensuring correct authentication with the Prey service. If the installation fails, an alert is created to notify IT teams for quick resolution.
Use cases
- Rapid deployment of Prey across Windows endpoints
- Automating security software installation for lost or stolen device protection
- Reducing manual input errors by referencing a Level custom field for the API key
- Ensuring compliance with organizational security policies
- Reducing manual setup time for IT teams
Recommendations
- Custom Field Setup: Ensure the Level custom field for the Prey API key is configured correctly before running the automation.
- Testing: Run this automation on a test device before deploying it at scale.
- Triggers: Use device tagging to automate the installation process.
- Monitoring: Watch for failure alerts to ensure successful deployments.
- OS Support: Currently supports Windows only. Contact support for macOS or Linux inquiries.
- Prey Configuration: After installation, log into the Prey dashboard to verify the device is registered properly.