IT Services Desktop Engineering team manages a central enterprise CrashPlan (Code42) cloud-based workstation backup and recovery service. This service allows divisional IT partners the opportunity to create and manage their own independent organization within the central IT Services CrashPlan (Code42) service framework. As a divisional IT partner, you have full control of your organization setup within CrashPlan (Code42), which allows you to configure and manage both the administrative and client settings to best suit your divisional backup and recovery needs.
The table below lists the privilege levels, roles, and responsibilities of both the IT Services Desktop Engineering team and divisional IT partners within the CrashPlan (Code42) framework.
|
Divisional IT Partners |
IT Services Desktop Engineering Team |
|
|---|---|---|
| Software Distribution, Installation, and Configuration | ||
|
Make default, system-specific client installers available online |
|
✓ |
|
Create department-specific client installers |
✓ |
|
|
Create department (sub-org) within CrashPlan (Code42) administrator console |
✓ |
|
|
Install client software |
✓ | |
|
Post and maintain documentation indicating include/excludes for default configurations |
|
✓ |
| Account Management | ||
|
Identify a single individual to act as a "Client Contact" for technical communications |
✓ |
|
|
Create Grouper group for CrashPlan (Code42) User Directory Sync (UDS) tool account creation/collaboration and assign rights for department IT administrators |
|
✓ |
|
Add Users to department Grouper group |
✓ |
|
|
Remove Users to immediately deactivate user accounts and delete all user archives when users or devices become ineligible for the service. |
✓ |
|
|
Notify ITS if unauthorized user accounts are identified and corrective administrative action is needed. |
✓ |
|
|
Review the number of client licenses used by each Organization Serial Code. |
|
✓ |
|
Support and Incident Management |
|
|
|
Administer and troubleshoot the CrashPlan (Code42) server |
|
✓ |
|
Troubleshoot client software |
✓ |
|
|
Push out updated client software |
✓ |
|
|
Restore individual user data |
✓ |
|
|
Perform individual test restores |
✓ |
|
|
Send automatically-generated emails alerting users to missed backups |
|
✓ |
|
Monitor individual user backups |
✓ |
|
|
Monitor system-wide backup performance |
|
✓ |
|
Privacy and Security |
|
|
|
Enforce encryption of backup data, authentication mechanisms, and proper handling of user archives |
|
✓ |
|
Collect identifying client information, including IP address and location, authenticating activity (CNetIDs), specific restore and backup actions |
|
✓ |
|
Maintain healthy SSO (Shibboleth) connectivity |
|
✓ |
|
Perform log analysis to identify suspicious activity |
|
✓ |
|
Conform to the responsibilities for handling electronic data as found in the UChicago Security Administrative Guide |
✓ |
✓ |