Removing Jamf Pro Package Receipt

I love the diverse methods that we all use to achieve the same result.
I cant help you with clearing the list.

I am presuming you are using the installed package result to build a smart group.

I would use a different method to achieve the same result.
I would script building a plist, with Student or Staff as its payload.
Then build an Extension Attribute to read the plist for its payload.

After a recon / inventory update, the EA results will be available in your Jamf. Simple to create a smart group based on the result.
You can script a change or removal of the plist and then run a recon and the EA will change its result, and therefore the group membership will change straight away.

I know this is not the answer you are exactly looking for, but hopefully it helps a bit.
I use this method as a part of my setup process.

Yeah, we are now in the process of changing the identification method, but it will take some time doing the changeover. Was hoping to find some method to do this while we still have a bunch of devices with the package receipt.

Guess I’ll also open up a ticket with Jamf to see what they have to say.

Thanks for another method to do this. We are going with creating an “app” by creating an empty folder under Applications named Student.app. That way we don’t even need to make an EA to track it.

Tim

I went through Support and there is no method anymore for removing entries from that list.

​@musat Question for you.

What brings you to this method for identifying between staff and student devices? I can see several future challenges with that methodology, but don’t want to assume I know much about your environment or reasoning. Especially since you must already have a method for defining those devices. 

This original method is something that has been in place for about 15 years, and at the time was a recommendation from the installation group. It has only recently stopped working. Given the length of time the process has been in place, we hadn’t even really noticed that it was something that would be affected by the Jamf Admin change way back when.

As mentioned, we are in the process of transitioning to a new method for making this distinction, but that transition will take a while as devices finally check in after summer to get “updated”. Just looking for some stopgap option to manage that “Packages Installed by Jamf Pro” list in the meantime. Though according to Jamf Support it looks like there is no mechanism in place to do that.

Oh well.

Interesting that Jamf Support told me that there was no method for doing this. Knowing this tidbit will completely make the transition to the new designation simple. This was the one piece that was missing to allow a smooth transition.

Thanks

Not sure what to tell you on that one. Support is usually really good so, I would recommend double checking any transcripts or email just in case it was a statement from Support in reference to another technology or roadmap. However, I did take a moment to test this in one of my environments and it does seem to work as I described. 

… and whatever you transition to, I highly recommend using departments for this type of separation. That, or static grouping if you must. There’s way too much communication and steps/components involved in what you’re currently describing as your setup. With many chances to break or be dependent on technologies to continue forward. Separating devices by user, group, OU, or whatever should really be simple, reliable and supported.

As ​@PaulHazelden mentioned multipleways to accomplish the intended tracking, I don’t have additional to add to removing the folder, however...
Though Departments can be used, I reserve that item for department names in my org.

I use ExtenstionAttributes (manually set in Jamf or a plist (computers only) or other searchable file from the computer) if something MUST be on the device itself.

More heavily in my organization, mainly devices environment, I use pop-up EAs like:
OrganizationGroup ie “Security Cellphones”
Environment “Production, Test, etc”
Facility “Hospital 1, Hospital 2”

I also have one for “LeadSupervisorManagerDevice” as a empty (false) or True, value to be set.  Default for every device is empty, so ‘false’, You could use just a ‘isStaff” EA and set True for staff and assume empty is student, or vice versa.

Nothing needs to ‘exist’ on the device/computer for us to assign this info, then smartgroups, etc are used for configs, apps, and inventory assignment groups, etc.

An additional item is a separate Prestage Enrollment for Staff or Student computers, then you can test the value in the computer record for the Prestage group.

Donald