Code42 platform hardware and software requirements
Who is this article for?
Incydr, yes.
CrashPlan for Enterprise, yes.
Code42 for Enterprise, yes.
CrashPlan for Small Business, no.
Overview
This article outlines the hardware and software requirements for components of your Code42 cloud environment.
Code42 console requirements
End user application requirements
The system specifications listed below are the minimum requirements needed to successfully install the Code42 app. Devices on unsupported operating systems may be unable to upgrade to the most recent Code42 app version.
Code42 app ports
List of ports that require outbound traffic to Code42. You must have both port 443 and 4287 open for use by Code42 apps.
Port |
Protocol |
Source |
Destination |
Description |
---|---|---|---|---|
443 | HTTPS | Code42 endpoint agents | Code42 cloud | Communication for File Metadata Collection and deployment policy information |
HTTPS | Web Browsers | Code42 cloud | Web restore (both zip file and device) and user activity profiles | |
TLS | Code42 endpoint agents | Code42 cloud | Communication from device to the Code42 cloud (only applies to Code42 environments that sign in to the Code42 console at: https://www.crashplan.com/console) | |
4285 | HTTPS | Web Browsers | Code42 cloud | Web restore (both zip file and device) and user activity profiles |
4287 | TLS | Code42 endpoint agents | Code42 cloud | Communication from the device to the Code42 cloud |
Additional services integrated with Code42
These are some additional ports used by services that are commonly integrated with Code42 environments.
Port |
Protocol |
Source |
Destination |
Description |
---|---|---|---|---|
8200 and 8201 |
TLS | Code42 cloud | Vault | Communication between a Vault instance and the Code42 cloud |
443 | HTTPS | Code42 cloud | AD FS server | Sync with AD FS |
636 | LDAPS | Your directory server | The Code42 User Directory Sync tool | Used by the Code42 User Directory Sync tool to sync with your directory service |