-
Notifications
You must be signed in to change notification settings - Fork 76
Installation
You can get the latest version of the node client in our download page. The installers are available for both 32 and 64 bit architectures. Please, make sure you download the version that corresponds with the architecture of your Operating System.
### Operating System Architecture If you need help identifying your Operating System architecture, here's how:
- Windows: Windows XP Professional, Windows Vista, Windows 7, Windows 8, Windows 8.1
- Mac OS X: Lion (10.7), Mountain Lion (10.8), Mavericks (10.9), Yosemite (10.10)
- Ubuntu: All currently supported versions by Canonical
- Other GNU/Linux:
The installation process takes care of uninstalling and cleaning any traces of previous versions of Prey installed in your system, including the bash client. This applies for both the attended and unattended installation processes, the latest being very handy when it comes to upgrading from the bash client to the node client in a huge amount of devices.
Regardless of the Operating System, the installation process is very straight-forward. Just execute the installer and follow the instructions. After you're done, the Prey configurator will open up and let you enter your authentication credentials.
Download the latest version of Prey (MSI installers are available on demand for Pro users), run the command prompt as an administrator, and follow the instructions bellow.
Important: Please reboot after installing Prey.
Both the MSI and the NSIS .exe packages support silent installation. Unlike the OS X version, the verification is done after the files have been copied, and there's a difference in the behaviour between theMSI and the EXE, as described below. The commands are:
msiexec.exe /i prey-windows-1.X.X-x64.msi /lv installer.log /q AGREETOLICENSE=yes API_KEY=foobar123
The /q parameter can be changed to /qn+, in which case a window is shown at the end of the process showing whether the installation succeeded or not.
In order to disable API_KEY validation, and to simply copy it to the prey.conf file (useful when installing without and Internet connection), add the SKIP_VALIDATION=yes parameter.
msiexec.exe /i prey-windows-1.X.X-x64.msi /lv installer.log /qn+ AGREETOLICENSE=yes API_KEY=foobar123 SKIP_VALIDATION=yes
And for the EXE package:
prey-windows-1.X.X-x64.exe /S /API_KEY=foobar123
The difference between these two methods is that:
The MSI package will fail and rollback the installation if it's unable to verify the API_KEY, either because it is invalid or there was a connection error.
The EXE package, however, will not fail and finish the installation. This allows running the command afterwards or opening the GUI to finish the installation correctly.
So basically we can choose any of the two behaviours based on the requirements of a specific user. The EXE package is mostly intended for regular users (i.e. not corporate deployments), however we thought it would be good to have the API_KEY option anyway.
The EXE installer already performs a check if a pre-1.x.x config file is found, so basically the account authorize logic was already there.
Donwload the latest Prey installer for OS X, open a terminal and run the following command:
API_KEY=foobar123 sudo -E installer -pkg prey-mac-1.X.X-x86.pkg -target /
Important: You must pass a valid API_KEY value.
The same PKG we distribute for normal users also contains the logic to check if an API_KEY env var is present when running the command. 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.
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
Just download the latest version of Prey, and run the following commands on 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
All major Operating Systems have their own tools or third-party softwares for mass-executing instructions on more than one computer at a time.
If you are already using a software for managing devices in your organization then al you have to do is massively run the unattended install process in the devices you want to add to your Prey account. Otherwise, below you will find a few softwares that can help you achieve this.
## Configuring Prey
Due to the fact that Prey is a security software, there's no shortcut to the Prey configurator. Instead, you have to manually run it, by following the instructions below.
Go to the directory where you installed Prey (by default C:\Windows\Prey) and execute the installer, that can be found in [prey directory]\current\lib\conf\gui\windows\prey-config.exe. From there, just follow the instructions to get Prey up and running.
Run the following command to bring up the Prey Configurator and then follow the instructions.
sudo /usr/lib/prey/current/lib/conf/gui/mac/PreyConfig.app/Contents/MacOS/PreyConfig
Run the following command to bring up the Prey Configurator and then follow the instructions.
sudo /usr/lib/prey/current/lib/conf/gui/linux/prey-config.py