Unattended Install for Windows
You can create installation packages for 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 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
Make sure you have the latest msi installer at hand. You can download it from our GitHub releases page
Also, you will need your account's API Key at hand. You can find it on the About page in your panel. Click on it to save to the clipboard.
For MSI and EXE command deployment, when replacing the installer name, you should include its location directory just before the installer name.
MSI package 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.
Open 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:
Note: The version in Prey-windows-x.x.x varies depending on the latest release.
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
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 finishes, close 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
- 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.