Skip to main content
Question

Bootstrapping non imaging with Quick Add .pkg

  • June 5, 2015
  • 1 reply
  • 3 views
G
Forum|alt.badge.img+16

So...

From this thread and Greg.....

https://jamfnation.jamfsoftware.com/discussion.html?id=14541

I am going to give this a try ...

"Boot the machine in TDM, install your bootstrapping pkgs, shut down. Connect to network, start up. Let your management system set the machine up to your standards."

On Greg's web site he points out that booting to the recovery partition is a better way than TDM...

So my plan is

  1. Boot to Recovery partition
  2. Plug in USB drive
  3. Open terminal and have onsite engineers run one script.
  4. That script will install a Quick Add .pkg and other required files (Maybe only the Quick Add .pkg will be needed, but I am guessing not )
  5. The JSS takes over and binds to AD and pushes required files.... : )

I have hunted and searched a little, but I haven't found anybody's else workflow/scripts to copy.

Has anybody else giving this a try?

I spent a few hours yesterday trying to install the Quick Add .pkg and there are issues. I am guessing that I have to copy the Quick Add .pkg to the "HD" and then install it ...

Thanks for your help!!

C

    1 reply

    bpavlov
    Forum|alt.badge.img+18
    • bpavlov
    • Esteemed Contributor
    • June 5, 2015

    @gachowski I've been working on something to kind of make this happen. But it's not for use in Recovery Partition. It's intended to be used in Casper Imaging. It involves some Applescript and curl to access the JSS API (I'm not sure the former will work in the Recovery Partition). However, you could possibly swap those parts out using bash so its all command line based. It's still in testing but once it's ready I can certainly share the pieces.

    But enough about this, have you tried actually copying the QuickAdd.pkg to a directory to on the local drive while in terminal? What's the error you get? Ultimately if you're going this route you will need to definitely script things together. This may mean creating a main script that will copy all the packages, daemons, and scripts to a directory on the local drive of the new computer and then runs the on first boot via a launchdaemon.

    It's an interesting approach for sure and definitely eliminates needing to deal with an image not working on special builds of hardware. Interested in hearing what you find.

    Terms & ConditionsCookie settingsAccessibility statement