Home Forums Software InstaDMG multiplescripts that need to be run, can this be done in InstaDMG, what is best way

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #378481
    sgstuart
    Participant

    Hi All,
    I have multiple scripts that need to be run. Including a script that will give the computer a unique name, and then another script that would bind the computer to AD with that unique name. Now can I run these scripts and many more somehow thru InstaDMG, or should these scripts be run thru ARD after? I would prefer running them somehow thru InstaDMG or somehow getting them setup to run as a loginhook, but how would I do that thru InstaDMG as well.

    Any help would be greatly appreciated.

    Thanks,
    Steven Stuart

    #378483
    Rusty Myers
    Participant

    I used to do this with my instadmg image. I’ve since moved to deploystudio for most of the post imaging tasks. Anyway, you need to install a script and a launchd item to the system image then run said script the first time your machines boot.

    The scripts can call each other or you can use a master script to call them individually.

    Your launchd item should be in /Library/LaunchDaemons so it runs at boot and as an authenticated user (root I think). I can provide some scripts to do these actions if you’d email me. There are also plenty of examples on this site and google.

    rustymyers (at) gmail dot com

    #378484
    larkost
    Participant

    I just want to emphasize/clarify one point that Rusty glossed over: InstaDMG can’t run these sort of scripts for you since it only runs when you are creating the image, not while you are deploying it. So to make this happen you have to install something in the image that will do it for you (or use something in your deployment tool, or your subsequent management tool). Once you have these scripts packaged up, InstaDMG will be happy to help you install them.

    When I do this sort of thing it is almost always with a LaunchDaemon, and I have been pushing recently to make sure that my scripts are all smart enough that they can be run at every boot and not slow things down when they are not needed. Partially this is because I am not using any real management tool for the installed computers, and this is taking its place, and partially this is because my computers can wander a bit before they make it to my subnet, and once they are there I want them looking like I set them. So special-case reasons, but I still think that it is generically good advice.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Comments are closed