Accidental deployment

[robby_barnes]

Hello,

I made a pretty noob mistake when preparing an install package for OS 10.10.1. I tried it on a test machine and it works great, but I didn't think my deployment strategy through 100%.

I had the right idea. I have the image cache to every compatible computer first (works great) so that once it's cached I wanted it to be available in self service as an installable item. That's exactly how I want it to work, but the problem is I cloned another install policy and didn't look very carefully, and had it execute at the recurring check in, so many of our computers just initiated the install automatically. I have since fixed that problem with the "install policy", and learned the lesson about cloning other policies... But my question is that there are a few computers that we can't update to 10.10 yet due to some software issues.

They are on the screen where the popup has come up warning them that the computer will shut down 5 minutes after clicking ok, and that's where I'm stuck. Is there a way to cancel it at this point? Is there a way to clear the cached file so that it can't execute properly on these computers? The other problem is that if the computer restarts for any other reason (we had a server reboot due to minor power interruption) it starts the process automatically at that point.

I've fixed the install policy, but it seems that the one I did previously has already "executed" on these machines. Any ideas?

[justinrummel · Accepted solution]

So there are two items:

1. Your Cached Installer is being stored in /Library/Application Support/JAMF/Waiting Room. You'll need to open Terminal, sudo -s to get in as root and remove the cached item.
2. Your Startup disk is set for the installer. Open System Preferences => Startup Disk and select the hard drive.

I believe this will solve the issue. Be sure to update your scope so the installer doesn't get re-cached.

[robby_barnes]

I'll give that a try. I don't mind it re-caching, it was the installer that was the problem. That should already be solved now.

Thanks!

[jhalvorson]

Besides stept number 2 posted by @justinrummel][/url, take a look at the root of the drive and you'll see a folder that only exists prior to the rebooting and kicking off the OS installer. I can't remember what the title of the folder is, but you could delete that, which should also prevent it from installing. I'll try to recreate to get that folder name for you.

I would the two steps mentioned by @justinrummel][/url and also delete that folder.