privatela.blogg.se - Code 42 console

Which name you see in the product, filenames, or paths depends on what version you are using. Crashplan was renamed Code42 after it was sold, then renamed again back to CrashPlan after it was sold again.

select Custom and use Custom Event SITE-code42-installįind the current Code42 package and click Add.

if Recurring Check-In is selected use Once per Computer.

If the policy will run repeatedly, make sure parameter Reinstall (below) is blank or No.

If the deployment policy token is for machine accounts: If the deployment policy token is for user accounts: The policy will pass the deployment policy token from Code42 - you will need that first.Īt the top right make sure your site is selected, not Full Jamf ProĬlick on Computers on the left, then Policies, then click New on the right

Wait until the Team makes the changes and provides the deployment policy token for the Org Set Launch Desktop app after install to: Īdd the following Mac user-detection script:Įcho "C42_USERNAME=$(scutil -get ComputerName)-$(date +%Y-%m%d-%H%M)" Please create a deployment policy for Code42 Org: To enable, request the following from the Code42 Team for the Code42 Organization you want to use (or, request a new Org be created)

The device is already set up, but they must click on Set Up Device, then click on Add New Device and click New. Once deployed, backups will begin, but when the user logs in the first time they will be prompted to "Set up Device". Once installed, Code42 will begin backing up the computer automatically, regardless of login method chosen ( user-account or machine-account)įor user-account login to the Code42 application (ie ): Some deployment policy changes may be needed to your Organization in the Code42 console, which must be made by the ITS Code42 team.

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.