Overview
When deploying the CrashPlan app, administrators must choose between two distinct installation types: System (default) and Per-user.
The System installation type (sometimes labeled as "Standard install" or "Install for everyone") deploys a single instance of the CrashPlan app for all Operating System (OS) users on a device. This is the default, recommended installation method and is the best choice for the vast majority of deployments.
The Per-user installation type (sometimes labeled as "Install just for me" or "Only for me") deploys an isolated instance of the CrashPlan app for each individual OS user on a device. This is a specialized deployment method typically reserved for shared devices where strict data separation between users is required, and centralized monitoring features are not needed.
Installation type comparison
Review the table below to understand how the two installation types handle backups, permissions, and settings.
| Feature | System install (Default) | Per-user install |
|---|---|---|
| Authentication | A single CrashPlan account is used, regardless of which OS user is signed in to the device. | Each OS user signs into their isolated CrashPlan app instance using a distinct CrashPlan account. |
| Licensing | Consumes a single license per device, covering all OS users on that machine. | Each OS user's isolated installation consumes a separate, distinct license. |
| Backup archive | All selected files on the device back up to a single, shared backup archive. | Each OS user's isolated installation backs up to its own unique backup archive. |
| Encryption key | A single encryption key secures the shared backup archive for the entire device. | Each OS user's isolated backup archive is secured by its own unique encryption key. |
| Backup permissions | Can back up any file on the device, except those contained in admin exclusions. | Can only back up files the specific OS user has permission to access, except those contained in admin exclusions. |
| Backup activity | Backs up constantly in the background, regardless of whether an OS user is actively signed in to the device. | Backs up only when the specific OS user is actively signed in to the device. |
| Encrypted file systems | Supports encrypted systems run at the system level (e.g., macOS FileVault). | Supports encrypted systems run at the OS user level (e.g., Windows EFS). |
|
App access |
The app and system tray icon are visible to all OS users on the device. | The app and system tray icon are visible only within the specific OS user's profile. |
| File restore | Any OS user who opens the app can restore any file from the shared backup archive. | The OS user can only restore files backed up from their specific isolated archive. |
Considerations for per-user installations
Because per-user installations operate with restricted permissions, review the following limitations before deploying this method:
- System requirements: Per-user installations are only supported on Mac and Windows. Linux devices only support system-level installation.
- Strict permission boundaries: The CrashPlan app relies entirely on the user's OS-level system permissions. It cannot access or back up any files or folders the OS user does not explicitly have permission to view. Furthermore, backups will completely halt when the OS user signs out of the device.
- Volume Shadow Service (VSS) limitations (Windows only): The CrashPlan service coordinates with VSS to back up open files. In a per-user installation, the CrashPlan service does not have full system-level access to VSS. Consequently, open files may fail to back up regularly. The service will retry later and succeed once the file is closed.
- Mixed installations are not supported: You cannot install the CrashPlan app using both installation types on a single device. You must choose either a System install or a Per-user install.