Waiting Room package goes bye bye??

donmontalvo
Esteemed Contributor II

We have a policy that first "Caches" a 5GB package, then runs recon, and then becomes in scope for the "Install cached" Self Service policy. A funny thing happened.

The 5GB package completed download to /Library/Application Support/JAMF/Downloads folder, then a few seconds later moved itself (the package and the associated XML file) into /Library/Application Support/JAMF/Waiting Room folder.

So far so good, right? We thought so too.

Bathroom break. 5 minutes later, and BAM the package and XML file is gone.

The "Install cached" policy is a Self Service only policy, and we didn't run it.

We checked JSS, policy history for the Mac clearly shows "Cache" policy completed without errors.

To cover all bases we checked /Library/Application Support/JAMF/Receipts/ and didn't see a receipt for the install either.

#scratcheshead

Is there an undocumented condition that would result in a cached package going bye bye?

I mean, it just disappeared...and covered it's tracks.

TIA,
Don

--
https://donmontalvo.com
2 REPLIES 2

stevewood
Honored Contributor II

@donmontalvo any other policies run after the cache policy?

donmontalvo
Esteemed Contributor II

Weird, since this was a test computer (MacBook Air), we wiped it, removed it from JSS, reran the policy and it works fine now. Very strange.

--
https://donmontalvo.com