Mon Nov 14 13:26:26 L3MBA13-OSXTEST jamf: Checking for policy ID 187...Mon Nov 14 13:26:27 L3MBA13-OSXTEST jamf: Executing Policy Office 2016Mon Nov 14 13:26:27 L3MBA13-OSXTEST jamf: The network connection was interrupted while downloading the package from Attempting to reconnect...Mon Nov 14 13:26:29 L3MBA13-OSXTEST jamf: Error: Microsoft Office 2016.dmg is not available on the HTTP server.Mon Nov 14 13:26:29 L3MBA13-OSXTEST jamf: Inventory will be updated when all queued actions in Self Service are complete.
My Jamf instance is hosted at jamfcloud.com.Our packages are uploaded to and deployed from jamfcloud.com.My caching servers are online and operating. My apple push certs are all renewed and valid. The SS policies are failing during the download of packages that are stored on the JSS server.
I'm trying to get this identified as an issue right now actually. M1 machines shipping with macOS 11.1 or 11.2 and going through ADE enrolment. Self Service will not install anything, policies don't finish executing. Jamf binary has no problems executing the same policies. Deleting com.jamfsoftware.selfservice.mac.plist and relaunching Self Service fixes it. This is not a Rosetta issue.
I've seen similar behavior on Intel builds at previous employers. Self Service gets into a funky state and won't run anything until com.jamfsoftware.selfservice.mac.plist is deleted and Self Service is relaunched. The M1 chip may be a bit of a red herring here.
Another circumstantial element to consider - the preference file domain changed recently from com.jamfsoftware.selfservice.plist to com.jamfsoftware.selfservice.mac.plist - something my support agent wasn't aware of and maybe because Enabling Debug Mode is outdated.
@dtmille2 We just got a help desk ticket for this exact issue (Self Service is not opening on an M1 Mac mini running macOS 11.3.0) Jamf Pro 10.27 here. The user's Self Service plist is not getting generated (com.jamfsoftware.selfservice.mac.plist). Did you open a Jamf case
@pat.best the administrators guide states here that scope can include \"individual computers, mobile devices, or users\" amongst other items. I too am experiencing the same issue as @huangbe and I'm currently working with support on why the policy will not install from self service. If I type
How do you make apps available to all Macs all the time We have separate policies to install applications based off smart groups. What I would like is to allow users to reinstall these apps at their leisure. We have Self service enabled and for each of the policies already is there a way to do this without having to create separate policies just for self service
EG Self service we have \"install firefox\" and reinstall firefox. Those policies only trigger through the command jamf policy -event install_firefoxThe polices within self service unless neede do not include a version number.
Some of those self-service policies may include scripts to delete or uninstall the existing installed app (or driver or plugin or...). And Jamf 10 made the button names a little 'wonky' because now there is a second button option for each self service policy, so adjust that secondary button label as needed so it's not to confusing.
With all that, users should only ever see one self service item per application. That should be a reinstall for anything they already have installed (so they can reinstall it as a troubleshooting measure), an upgrade when a new version is available, and an install for stuff we don't normally pre-install for them (Cyberduck for example).
When a new version comes out we just package it up (if it's not already a usable pkg), upload it to the server, swap the old package in Jamf Admin with the new package, change the three Self Service policies to use the new package, and then change the smart groups to use the new version. Doing it in that order means that the self service polices will run the right version even if the user is clicking it because they had an even older version.
And we use the Featured category as the default category on launching self service, and important updates or new installs are marked as Featured to emphasize their importance (Security, functionality, or work mandated new app). Updates go in a category simply called \"Updates\". A category called \"Installed\" is where the reinstall policies could be found (in addition to being in other categories like Internet for browsers). Between the Search, putting stuff in multiple categories, and flagging important stuff as Featured we've tried to make it easy for our users to stay up to date.
We tell them they should check Self Service before they go on any assignments (never know when you'll go to a bombed out village in Syria and its too late to get that important update), and at least check self service once a week otherwise.
What I ended up doing is modifying our current policies (prefixed with Deploy-) so that they are set up just for self service purposes. IE scoped them out to all computers, removed all triggers except a custom trigger, deploy_, and changed the frequency to ongoing. This makes the apps always available in self service. Next I created new policies (prefixed with Auto-) which will keep our automation in place. These policies are scoped to the smart groups for systems that do not have the apps, have a trigger for reoccurring check-in and a frequency of once per computer. All the Auto- policies do is call jamf policy -event deploy_ which is what rderewianko suggested. Overall this seems to be working well and only requires us to maintain the Deploy- policies. Thank you all for your input!
@MM2270 I checked and there is no other policy scoped that would cause this. I restored my test Mac again, enrolled under a different name again, same process. Got all the other policies for standard enrollment, then the software updates hits it. I see it initiate in Terminal when i perform a check in. I scoped just that one test Mac to that Self Service Policy with no trigger. Had frequency as \"ongoing\" since I wanted it to always be available in self service. I also didn't realize there are no logs for Self Service Policies Anyway, unless you see something I may have wrong, I'll put in a ticket and see what happens. I am going to test again, but have that policy shut off.
Submitting log to Executing Policy Install Rapid7 with PKGDownloading Rapid_7.pkg...Downloading -jcds.services.jamfcloud.com//download/8a3d328b6c854e328a76c7bc18e8fd4b/Rapid_7.pkgtoken=40857e851e444ebab8b4175881f1c9c4jwxpzvmv78o6u1sta3c8gcka7yjx7s35...Verifying package integrity...Installing Rapid_7.pkg...Successfully installed Rapid_7.pkg.Submitting log to Executing Policy Install ZoomDownloading Zoom456_5666_1020.pkg...Downloading -jcds.services.jamfcloud.com//download/8a3d328b6c854e328a76c7bc18e8fd4b/Zoom456_5666_1020.pkgtoken=40857e851e444ebab8b4175881f1c9c4jwxpzvmv78o6u1sta3c8gcka7yjx7s35...Verifying package integrity...Installing Zoom456_5666_1020.pkg...Successfully installed Zoom456_5666_1020.pkg.Submitting log to Executing Policy Install Zscaler App (only on Laptops)Downloading Zscaler-osx-184.108.40.206-installer.pkg...Downloading -jcds.services.jamfcloud.com//download/8a3d328b6c854e328a76c7bc18e8fd4b/Zscaler-osx-220.127.116.11-installer.pkgtoken=40857e851e444ebab8b4175881f1c9c4jwxpzvmv78o6u1sta3c8gcka7yjx7s35...Verifying package integrity...Installing Zscaler-osx-18.104.22.168-installer.pkg...Successfully installed Zscaler-osx-22.214.171.124-installer.pkg.Running command sudo -s open /tmp/Zscaler_installer/Zscaler_1_4_2_3.app...Result of command:The file /tmp/Zscaler_installer/Zscaler_1_4_2_3.app does not exist.Submitting log to Executing Policy Microsoft Office 2019 ver. 16.30.19101301 10/22/19Downloading Microsoft_Office_16.30.19101301_BusinessPro_Installer.pkg...Downloading -jcds.services.jamfcloud.com//download/8a3d328b6c854e328a76c7bc18e8fd4b/Microsoft_Office_16.30.19101301_BusinessPro_Installer.pkgtoken=40857e851e444ebab8b4175881f1c9c4jwxpzvmv78o6u1sta3c8gcka7yjx7s35...Verifying package integrity...Installing Microsoft_Office_16.30.19101301_BusinessPro_Installer.pkg...Successfully installed Microsoft_Office_16.30.19101301_BusinessPro_Installer.pkg.Installing all available Software Updates...
I know this doesnt answer the why this is happening question you have but you can do this without a script. Just create a policy that has the payload \"Files and Processes\" then under \"Execute Command\" add the SoftwareUpdate -ia or SoftwareUpdate --all --install --restart (thats what I have for mine). Set the \"Execution Frequency\" to ongoing but do not select any triggers. Make sure you enable it for self service and give it a nice icon and description then scope it to everyone or just a group of users you want. I've attached some screenshots of my self service upgrade policy. Hopefully that helps some.
Faculty/staff can manage their own software installs, updates and computer restarts. Using a self-service application already installed on UNF-managed Windows and Mac computers, faculty/staff can install programs without administrative rights and control when their computer will restart to apply required software updates. If software update notifications are ignored, a computer will automatically restart about four-hours after a user logs in to it. Warnings will be displayed so the user will have plenty of time to save their work. 153554b96e