![]() Mkdir -p /Library/Application\ Support/CrashPlanÄEVICE_CLOAKED=false" > /Library/Application\ Support/CrashPlan/deploy.properties Our Jamf script looks something like this: You can create a script in Jamf to write the Deployment policy file to the appropriate location on the endpoint just add the script to your Crashplan policy in Jamf. More info here (the page references Incyder, but the concepts are the same) Once built, the Deployment Policy is a downloadable text file with few lines in it. In turn, the Deployment profile will allow the client app to download any customization templates before 1st launch, allowing for custom logos, text fields, etc. The Deployment policy tells the desktop client things like server URL, Reg Key, default Organization for new devices, Silent install configuration, etc. Within the Crashplan console you can create Deployment policies and Customization Templates. We haven't had on-prem servers for like 5 years now. Caveat: We're on a hosted version of Code42 I have no idea if this is also supported in the on-prem versions. ![]()
0 Comments
Leave a Reply. |