Prey unattended install for computers
Before We Start
Download the latest Prey installers for laptops from our GitHub releases page (MSI for Windows included).
You can find your API Key on your account settings, white over blue at the bottom-left corner of the screen.
Check this article if you're deploying on phones.
There are two different installation methods for Windows. A pre-configured installer that will get the devices added to your account, or
MSI packages that you can run with Group Policy, Active Directory, etc.
You can create installation packages your Pro account here: Unattended installation.
To get the installer, click on Create and you'll get both an email with download instructions and a link You can pass that installer or link to your teammates or employees, and when they install Prey into their computers, they'll be added to your account. No Prey login required.
- Each unattended installer is created for a specific user. If your account has more than one user, be careful.
- Installers created this way will be available for as long as you need. Once you're done and don't want the package to be usable anymore, you can revoke the access from the same page and it will stop working for new installations. All computers already protected will be unaffected.
- The unattended install package will not create an uninstall file. To remove Prey from any of the computers, you'll have to run a command prompt as an admin and then run the following command:
wmic product where name="Prey Anti-Theft" call uninstall
MSI and EXE installers
If your environment doesn't support the pre-configured package, you can use our regular MSI and EXE installers instead. Both will work and install Prey on your systems, with two main differences.
MSIpackage is completely silent. There won't be any user dialog when installing. Any error will break the installation, and the output be written into a log file. No will be created.
EXEpackage requires a few clicks, will create an
,and will remove any previous Prey installation.
Run the command prompt as an admin, and run the following command on it:
msiexec.exe /i prey-windows-1.X.X-xxx.msi /lv installer.log /q AGREETOLICENSE=yes API_KEY=foobar123
Which should look like this:
If you need a confirmation message at the end of the process, you can change the
/q parameter to
This method will fail on computers without an internet connection. In order to disable the immediate validation against the Prey servers just add the
SKIP_VALIDATION=yes parameter. In that case, the command would look like this:
msiexec.exe /i prey-windows-1.X.X-xxx.msi /lv installer.log /qn+ AGREETOLICENSE=yes API_KEY=foobar123 SKIP_VALIDATION=yes
The MSI installer will not create an uninstall file. To remove Prey from any of the computers, you'll have to run the same MSI package again, or open a command prompt as an admin and then run the following command:
wmic product where name="Prey Anti-Theft" call uninstall
EXE installer is more oriented to individual users, not to organizations. It will require a few clicks even on its most silent mode, and will create an in case you need it in the future. To get an unattended install of the
EXE file run the command prompt as an admin and run:
prey-windows-1.X.X-xxx.exe /S /API_KEY=foobar123
The command should gracefully look like this:
/S parameter makes the though it can't be completely silent. For that please prefer the MSI method.
Open a terminal and run the following command:
API_KEY=foobar123 sudo -E installer -pkg prey-mac-1.X.X-xxx.pkg -target /
Important: You must pass a valid API_KEY value or the process won't work.
The script will actually check if the key is valid and if the account has available slots before copying anything to disk. This means that if the
API_KEY verification fails, the install process will exit with a fatal error and it won't copy anything.
Ubuntu and Debian-based Distributions
Run the following commands a terminal:
sudo apt-get update API_KEY=foobar123 sudo -E dpkg -i prey_1.X.X_amd64.deb
In case dependencies aren't found, just run these two additional commands:
sudo apt-get -f install API_KEY=foobar123 sudo -E dpkg -i prey_1.X.X_amd64.deb
npm install -g prey # this will make the 'prey' command available system-wide sudo prey hooks post_install sudo prey config account authorize -a foobar123 # foobar123 is your API key
We only provide official Linux support for Ubuntu systems. It is only a tiny fraction of our users, and most of them run Ubuntu. Let us know if we can help you with anything else by reaching us at firstname.lastname@example.org.
To image deploy Prey on your computers is simple. Steps must be followed entirely, though, or bad things might happen. The most important part is that Prey must be the last app to be installed on the master machine. You can't connect it to the internet after this process or you'll get cloned machines on your Prey account.
Once you're done with everything else and you are ready to setup Prey,
- Install the regular Prey package on the master machine, double clicking on the installer.
- When the process the config dialog. Do not enter your account's credentials. We can't insist enough on this.
- Disconnect from the internet.
- Edit the
prey.conffile and add your API Key to line 36. The location of the file is:
- macOS & Ubuntu:
- Save changes.
Do not connect to the internet.
Now you can deploy the image into other computers. As soon as the new devices connect to the internet they'll be added to your Prey account.
Troubleshooting and Known Issues
Cloned Devices From an Unattended Install
Device registration is based on hardware.
device key. That means that a single device entry on your Prey account will manage several computers, the one sharing hardware information.
To prevent this from happening you can disable the "Overwrite devices if their hardware information already exists on this account" option from the Device Management settings and install Prey again.
Cloned Devices From Image Deployment
If the previous case doesn't fix the problem, then it means that you connected the master machine to the internet after installing Prey. That made it create the device on your Prey account, and then it cloned that same configuration all other computers. To fix that, completely uninstall Prey and start again.