Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
For automatic deployment of the Code42 client via JAMF you need to create a JAMF policy in your Site which uses a global script available in the Campus JAMF system. Some deployment policy changes may be needed to your Organization in the Code42 console, which must be made by the ITS Code42 team.
Once installed, Code42 will begin backing up the computer automatically, regardless of login method chosen (user-account or machine-account)
For user-account login to the Code42 application (ie youreid@eid.utexas.edu):
Once deployed, backups will begin, but when the user logs in the first time they will be prompted to "Set up Device". The device is already set up, but they must click on Set Up Device, then click on Add New Device and click New. See [Code42 first time login]
To enable, request the following from the Code42 Team (utbackup-support@utlists.utexas.edu) for the Code42 Organization you want to use (or, request a new Org be created)
Please create a deployment policy for Code42 Org: [Org name]
Set Auto Register to Yes
Set Launch Desktop app after install to: [Yes or No]
Add the following Mac user-detection script:
Code Block | ||||
---|---|---|---|---|
| ||||
#!/bin/sh C42_USER="$(defaults read /Library/Managed\ Preferences/edu.utexas.inventory eid)@eid.utexas.edu" echo "C42_USERNAME=$C42_USER" echo "C42_USER_HOME=/Users" |
Wait until the Team makes the changes and provides the deployment policy token for the Org
For machine-account login to the Code42 application:
This method will create an account in Code42 with a name based on the computer name.
Users will not be able to log in to the Code42 application at all, and only Code42 console users with access to the Org will be able to do restores or check status
To enable, request the following from the Code42 Team (utbackup-support@utlists.utexas.edu) for the Code42 Organization you want to use (or, request a new Org be created)
Please create a deployment policy for Code42 Org: [Org name]
Set Auto Register to Yes
Set Launch Desktop app after install to: No
Add the following Mac user-detection script:
Code Block | ||||
---|---|---|---|---|
| ||||
#!/bin/sh
echo "C42_USERNAME=$(scutil --get ComputerName)-$(date +%Y-%m%d-%H%M)@eid.utexas.edu"
echo "C42_USER_HOME=/Users" |
Wait until the Team makes the changes and provides the deployment policy token for the Org
Create policy in JAMF:
The policy will pass the deployment policy token from Code42 - you will need that first.
Log in to the JAMF console at https://mdm.utexas.edu
At the top right make sure your site is selected, not Full Jamf Pro
Click on Computers on the left, then Policies, then click New on the right
General
Display Name:
If the deployment policy token is for user accounts:
SITE - Install Code42 - user account
If the deployment policy token is for machine accounts:
SITE - Install Code42 - machine account
Trigger: As preferred
- If the policy will run repeatedly, make sure parameter Reinstall (below) is blank or No
Suggestions:
- if Recurring Check-In is selected use Once per Computer
- select Custom and use Custom Event SITE-code42-install
Packages
Click Packages on the left
Click the Configure button
Find the current Code42 package and click Add
- e.g Code42_8.8.2_1525200006882_143_Mac-x86-64.dmg
Action: select Cache
- IMPORTANT: Do NOT select Install or Install Cached
Scripts
Click Scripts on the left
Click the Configure button
Find "GLOBAL-code42-install-mac" and click Add
Parameter Values
Code 42 Package: the name of the package you entered above
Deployment Policy Token: the token from the Code42 Org deployment policy
Reinstall: leave blank normally, put Yes if the client should be uninstalled first
Scope
Click on Scope at the top
Targets
Select All Computers in [SITE]
Or
Select "Specific Computers" and desired Computer, Computer Groups, etc
Exclusions
Add any exclusions you need.
Click Save in the lower right
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|