Crashplan can be deployed via a push with a script or by setting up accounts manually.

The video tutorials seemed particularly helpful to improve comfort with using the tool, but that is partially dependent on the level of file access your user base will have. Crashplan also has an “ End User Adoption” page with resources to help your end-users.

Identify how you would like to contact your user base.

These changes can be made by your Org Admins.

Review the settings options and determine what fits for your organization.

Decide whether it makes sense for your org to push the deployment to end-users or set them up individually in the Crashplan system.

If you have a more complicated situation, have a lot of different budget codes, or need assistance, contact ISC Client Care. To set up the budget code(s), go into the Crashplan console, open up the top level associated with the budget code, and then enter the budget code in the 'Reference' section in the 'External Reference' field. Some schools are billing at the level of their school or center while others have created sub-orgs for organization and/or billing purposes.

Enter your budget codes in Crashplan for billing purposes.

The option to use PennKey SSO is available but requires that your users are using as their usernames.

Decide whether you want to use Single Sign-On (SSO) for logins.

These people will be granted Org Admin access in the system.

Identify the IT users in your organization who will be administering the Crashplan accounts for your school or center.

Submit a ticket to ISC Client Care to get the planning discussion started. These are some of the primary decisions/options to consider when setting up a new instance of Crashplan. ISC Client Care can assist you in the planning and setup of Crashplan for your school or center.

Mac code42