Installation workflows for Computers

Depending on your operating system and preferred installation method, Prey allows you different options to deploy the client to your devices. In this article you can find the workflows available per operating system, directions on how to deploy via imaging, and general recommendations for deployment via MDM.

While we do have a number of unattended installation options for most operating systems, its important to note that these workflows are not silent, and will be visible to any user currently logged into the device. As with any unattended installation workflow, no prompts will be required from the user.

All unattended installation methods use your Setup Key (not to be confused with the Developer API). You can find it in the Setups section of the Settings menu of your Control Panel.

Normal installation (login required)

You can always install Prey manually on each device, by executing the corresponding installation file on your device and entering your login credentials on the required fields. This method requires you to manually enter your login credentials, and as such, we recommend this only for limited-sized fleets.

Unattended installation

For deployment on larger fleets that will not prompt the user to enter your login credentials, you can use one of our unattended installation workflows.

  • For Windows devices, you can follow one of the following deployment options.

    Unattended installer link

    You can find the unattended installation link by clicking in the button in your Device List view, or in the Unattended installation section of your Settings menu. This method will create a link where you can download a pre-configured .exe file that will install Prey and add it to your account without the need for login credentials or additional steps.

    To create the link, just click on next to the name of the user under whom you want to add the device. You can either distribute the link to your end users so they can download the file and execute it, or download the file yourself and distribute it through an MDM or RMM, always keeping in mind that, while this won’t prompt the end user to do anything, an installation window will pop-up.

    MSI file deployment

    This method requires a string to be executed in a command prompt with administrator privileges.

    You can find the MSI file in our downloads page and in your panel, by clicking on the button in your Device List view. The string to be executed in a command prompt depends on the version of the Prey for Computers client that you’re installing, and your personal Setup Key - we recommend you take the string directly from your panel, as it will already have all the required variables.

    Image Deployment

    Installing Prey on your computers using image deployment is easy if you follow our instructions. The Prey app must be the last app installed on the master machine. You can't connect this machine to the internet after this process, or you’ll risk getting machine duplicates on your Prey account.

    Go through your complete setup process, and when you’re done, follow these setup instructions:


    1️⃣ Install the regular Prey package on the master machine (not the unattended installer). Download the latest installer here:


    2️⃣ See the image below, make sure to uncheck the box and when the process is finished, close the window. Do not enter your account's credentials. We can't emphasize this enough. 



    3️⃣ Now, disconnect from the internet.


    4️⃣ Add your Setup Key to the device's database by following these steps:

    • Open a CMD window as admin and run the following command

    c:\Windows\Prey\current\bin\prey config settings update control-panel.api_key SETUPKEY

    • Make sure to replace the SETUPKEY parameter with your unique Setup key, found in the Panel under Settings > Setups (not to be confused with the Developer API).

    • 5️⃣ Confirm the configuration is correct by checking that the Setup key field has your key and the device key is blank. c:\Windows\Prey\current\bin\prey config settings list

      6️⃣ Now, save the image for all future deployments. Just make sure your saved version has no associated device key. Do this before going back online (and store the image safely!).

      7️⃣ Now you can deploy the image into other computers. Make sure the master device is disconnected to the internet to do so.

  • To run an unattended installation for MacOS, you first need to download the latest MacOS installer from our downloads page, and have access to your Setup Key (see note above). With that in hand, generate the following string:

    API_KEY=your_setup_key sudo -E installer -pkg prey-mac-1.X.X-xxx.pkg -target /

    Replace the your_setup_api_key and prey-mac-1.X.X-xxx.pkg placeholders with your setup API key and the name of the package you just downloaded, correspondingly.

    After you create the string, open a Terminal window, navigate to the folder in which you downloaded the package, and paste the created string in the prompt. Wait for a few minutes, and the device will automatically be added to your Prey account.

  • Before you start any of the workflows outlined below, make sure the relevant dependencies are installed in your machine. You can install them using Ubuntu’s advance package tool (apt) by running the following string:
    sudo apt install libgtk-3-dev scrot streamer mpg123

    If you’re running Ubuntu 20 or earlier, run
    sudo apt install python-gtk2 scrot streamer mpg123 instead.

    Afterwards, create the following string and save it:

    API_KEY=your_setup_key sudo -E dpkg -i Downloads/prey_1.X.X_amd64.deb

    Replace the your_setup_key and prey_1.X.X_amd64.deb placeholders with your setup key and the name of the package you just downloaded, correspondingly.

    Afterwards, run sudo apt-get update in a terminal window, followed by the string you created.

    After a few minutes, the device will be added automatically to your account.

Considerations for Deployment via MDM

While all MDMs work differently, there are a few considerations that you should take into account when creating the policy:

  • Make sure the installation file is cached in the target directory instead of immediately removed.
  • All strings should be executed with admin privileges or using sudo passwords when required.
  • If you need assistance in creating the policy for your MDM, please contact our Support Team - they’ll be happy to help.

Was this article helpful?

0 out of 0 found this helpful