Quickadd Package & DeployStudio

[sinergi]

Does anyone else use the QuickAdd package to enrol the machine using DeployStudio without any problems?

I created a simple workflow, name the machine, skip registration and install the QuickAdd package created from Recon. For some reason I can't seem to get this to work;

'installer: The install failed (The following installation step failed: run postflight script for QuickAdd. Contact the software manufacturer for assistance.)'

Thanks

[rtrouton]

Are you installing the QuickAdd as a postponed install, so that it installs at the Mac's first boot?

If it's not set as a postponed install, you'll need to do that. The QuickAdd's installer scripts won't run properly and the install will fail in a manner similar to the way you've described.

[sinergi]

I've tried both sadly with no luck :-/

I'll create a new workflow and try again, see attached;-

http://postimg.org/image/lw4fwhult

[rtrouton · Accepted solution]

You may want to build a new QuickAdd. There may be an issue with the installer itself.

I've been deploying QuickAdds with DeployStudio since we started using Casper a few years ago. DeployStudio installs the QuickAdd like it does any installer package.

[sinergi]

That was my suspicion, when you suggest create new package. Just use the Recon app or do you use any other fancy way?

Many thanks.

[mm2270]

Yeah, we install our QuickAdd via DeployStudio as well with no issues, as long as there is an active network connection of course. It works. Have you tried manually installing the same QuickAdd pkg to see if you get any errors when run outside of DeployStudio?

[scottb]

A dumb question - because I did this when I started :)
Did you use the QuickAdd.pkg downloaded from the JSS or made my Recon.app?
If you don't use the Recon version, it won't work... Not meant to insult - like I said...

[sinergi]

@mm2270][/url the package does in fact work when it is manually installed.

@boettchs I had used Recon as the primary way to create the quickadd.pkg, no offence taken :D

@rtrouton][/url, the new package did in fact work. The problem that was occurring was deploystudio failed to install the package and it had that horrible restart loop.

[rtrouton]

One way to avoid the restart loop is to check the Ignore install failures option in the Installer workflow task's options for that installer package.

external image link

With that option checked, if installation of that particular package fails, DeployStudio will note it in the log and proceed with the rest of the workflow.