![]() ![]() # By adding in parts of the installPKGfromDMG script from JAMF, we can install the PKG from the DMG. ![]() # and that makes it the perfect source for obtaining the installer. # The CrashPlan Server will always host the most current version of the CrashPlanPROe client installer Not sure how to adjust if you have CrashPlan SAS. Here's how to escape the process of updating your CP PROe package or making the users wait for the update to take place - the magic of curl. Between 3.5.3 and 3.6.1.4 a new setting appeared, but it wasn't major and the custom setting for 3.5.3 was working properly when 3.6.1.4 was being deployed So depending on how old your custom script is, you may or may not need to update that but generally you don't have to revise it for every version. I last updated my custom script when version 3.6.1.4 became available. With help from JAMFNation, I've revised my deployment of CrashPlan PROe via self service to the following:ġ) Install the custom settings via a packageĢ) Install the latest client directly from our Master using a script. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |