- Jamf Nation Community
- Products
- Jamf Pro
- Re: delete
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
delete
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-14-2017 11:26 AM
Reply
9 REPLIES 9
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-14-2017 12:39 PM
Is this true across your entire fleet?
In my environment we have had some problems with Self Service, but they're intermittent. In those cases, we use Apple Remote Desktop to copy a "good" Self Service client to the affected computers.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-14-2017 03:59 PM
Is this all packages? If it's just this package, is this a particularly large installer?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-14-2017 08:21 PM
@lotonyni When you're looking at your Policy in your JSS console, make a note of the the Policy ID in the URL for that page. Using that ID, and a terminal session on a machine that the policy fails to complete via Self Service, issue the command sudo jamf policy -verbose -id <THE_ID_YOU_FOUND>. That will run the policy in verbose mode, and hopefully give you an idea why it's hanging up.
Reply
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-15-2017 01:10 PM
I think this may be a bug. We have this happen quite often, JSS version 9.98. When this occurs, disabling and re-enabling the policy or removing the offending device from the scope of the policy and then re-scoping has fixed it every time.
Reply
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-15-2017 06:55 PM
What's your JSS infrastructure? how many clients?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-21-2017 06:16 AM
delete
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 08-21-2017 06:16 AM
delete
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 12-29-2017 12:39 PM
Not sure if you've been able to troubleshoot further. By chance, are you only encountering this problem with a single package (other packages install via Self Service just fine?). If so, is it possible that you started to install this package and clicked cancel (or the install was interrupted midway?). I think this issue may occur as a result of canceling a package mid way via Self Service, and other subsequent tries will fail (probably because there is a partial package downloaded). I think modification of the policy may cause the entire policy to re-fresh and re-run (in the event that the package changed). Just a theory.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 05-05-2019 08:39 PM
delete
