DOCUMENTATION
- Home
- Documentation
- Zluri Agents
- Zluri Agents
- Deploy Chrome Agent Through Jamf
Deploy Chrome Agent Through Jamf
To deploy Chrome Agent through JAMF, You need to have an active Jamf Integration. To integrate Jamf with Zluri, Please navigate to 'Sources->Integrations' to connect Jamf with Zluri. It takes 24-48 hours for the sync to complete. Once the first sync is complete you can proceed with the below steps.
Please follow the below steps in order to install Zluri Chrome agent through Jamf.
Login to the jamfpro https://[instance].jamfcloud.com/
Visit 'Settings' at bottom right corner, Search 'Category' in the search box and Create a new category, name such as zluri-orgname. You can follow the steps here to create a category.
Create a new policy. You can follow the documentation here to create a policy.
Download the package from this link and Upload the package in Jamf. You can follow the documentation here to upload the package.
Under 'Computer Management', Select package.
Click + New
Under Category, choose the category that was created in Step 2
Under Filename, choose the .pkg and let it upload and click Save.
Now, to add the scripts, follow the Jamf pro documentation:
Ensure that you name the preinstall script “preinstall” and paste the script’s contents into the scripts area.
Copy the preinstall script from: https://pastebin.com/JLusiknn
Choose the Category as the category created
Now, under Options, choose Priority as Before
Now repeat the same steps for postinstall script
Paste the postinstall script from https://pastebin.com/pXrjcVi2
Replace the org_token with the token provided to you by the Zluri customer success team.
Name the script as post install
Choose the Priority under options pane as “After”.
Save the settings.
Now, Choose Policies from the left-menu, choose the Policy you created in Step 1
Under Options, in Packages, Choose Distribution point as Cloud distribution point as shown in the screenshot above.
Select the package that you uploaded in Step 4-d.
Then, under the Scope pane, set All Computers under Target Computers and All Users under Target Users and Save.
Again, go to Options under the Policies, Click on Scripts.
Select preinstall script, set the priority to Before and for post install select After.
And finally, in the General pane, Ensure to click the Enabled checkbox
Enable the Recurring Check-in checkbox to ensure the policy runs every 15 mins
Set the Execution Frequency to Ongoing
Now that you’ve performed all the steps properly, go to Policies from the left-sidebar menu.
Here, you’ll see an overview of the policy (here ZLURI DA MDM) and the scripts and .pkg in the right order to execute.
The above steps will ensure that the Policy runs on the targeted devices and runs the preinstall.
After following the above steps, the policy is ready to install the Zluri app in the targeted devices.
Note: Please note that the updated logs of policy run in the targeted systems might be delayed.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article
To deploy Chrome Agent through JAMF, You need to have an active Jamf Integration. To integrate Jamf with Zluri, Please navigate to 'Sources->Integrations' to connect Jamf with Zluri. It takes 24-48 hours for the sync to complete. Once the first sync is complete you can proceed with the below steps.
Please follow the below steps in order to install Zluri Chrome agent through Jamf.
Login to the jamfpro https://[instance].jamfcloud.com/
Visit 'Settings' at bottom right corner, Search 'Category' in the search box and Create a new category, name such as zluri-orgname. You can follow the steps here to create a category.
Create a new policy. You can follow the documentation here to create a policy.
Download the package from this link and Upload the package in Jamf. You can follow the documentation here to upload the package.
Under 'Computer Management', Select package.
Click + New
Under Category, choose the category that was created in Step 2
Under Filename, choose the .pkg and let it upload and click Save.
Now, to add the scripts, follow the Jamf pro documentation:
Ensure that you name the preinstall script “preinstall” and paste the script’s contents into the scripts area.
Copy the preinstall script from: https://pastebin.com/JLusiknn
Choose the Category as the category created
Now, under Options, choose Priority as Before
Now repeat the same steps for postinstall script
Paste the postinstall script from https://pastebin.com/pXrjcVi2
Replace the org_token with the token provided to you by the Zluri customer success team.
Name the script as post install
Choose the Priority under options pane as “After”.
Save the settings.
Now, Choose Policies from the left-menu, choose the Policy you created in Step 1
Under Options, in Packages, Choose Distribution point as Cloud distribution point as shown in the screenshot above.
Select the package that you uploaded in Step 4-d.
Then, under the Scope pane, set All Computers under Target Computers and All Users under Target Users and Save.
Again, go to Options under the Policies, Click on Scripts.
Select preinstall script, set the priority to Before and for post install select After.
And finally, in the General pane, Ensure to click the Enabled checkbox
Enable the Recurring Check-in checkbox to ensure the policy runs every 15 mins
Set the Execution Frequency to Ongoing
Now that you’ve performed all the steps properly, go to Policies from the left-sidebar menu.
Here, you’ll see an overview of the policy (here ZLURI DA MDM) and the scripts and .pkg in the right order to execute.
The above steps will ensure that the Policy runs on the targeted devices and runs the preinstall.
After following the above steps, the policy is ready to install the Zluri app in the targeted devices.
Note: Please note that the updated logs of policy run in the targeted systems might be delayed.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article