rtrouton / first-boot-package-install Goto Github PK

I have a few packages I made that call osascript from bash to join our active directory and set the machine name by presenting dialog boxes. When I run the packages on my regular Mac, when Installer gets to 'Running package scripts' the dialog boxes appear and the script runs normally. However, when I install the same packages through First-Boot-Package-Install the package fails to install.

So....Filevault. :-)

Since the FileVault user 'logins in' at the EFI prompt, there is no login window. The packages still install but LoginLog window is not displayed. This wouldn't be a huge deal except it reboots the machine when the packages are done without any user interaction. Just blip....reboot.

I was working through the workflow of FBPI and I don't see a way to refactor this to work properly with FileVault on.

Any ideas?

When firstboot package is runing it dont run the packages is the right order.
It starts with 03 and then 04, 02, 00 and 01

In firstbootpackageinstall.sh its a line with:
install=($(/usr/bin/find "$install_dir" -maxdepth 2 ( -iname *.pkg -o -iname *.mpkg )))

I think "find" need -s flag to work.

Hi,

Here, in the schools of Geneva, Switzerland, we have using First-Boot-Package-Install for many years now, in conjunction with AutoDMG.

Now, i try to make a new master with MacOS 10.12 and i use First-Boot-Package-Install.pkg. I restore a mac with an image created with AutoDMG, the mac boots, the window with the list of the packages appears. Everything seems good, but when the mac restarts, it shows again the window with the list of the packages and install them again... and again. We have to manually delete the folder inside Shared to be able to start normally the mac.
Thanks for your help.

Christian

Could you please confirm: in order to disable network check, I need to install iceberg, then modify the /Users/localfinraadmin/Desktop/testelcap/First-Boot-Package-Install-master/Iceberg_project_files/First Boot Package Install/resources/var/firstbootpackageinstall.sh file and then recompile the project?

Please also confirm that lines 76 through 114 lines of script should be commented out.

Thank you very much in advance!

Documented at https://managingosx.wordpress.com/2017/11/17/customized-high-sierra-install-issues-and-workarounds/ distribution-style packages need to have a unique product id included in the distribution file for it to work with startosinstall's --installpackage option. Without a product id the package is not included in the output of that tool.

This FR is to ask to include a product ID when building a distribution pkg.

Example:
Add <product id="com.foo.bar.pkg" version="1.0"/> to the distribution. This is done as part of the productbuild binary as productbuild --identifier com.foo.bar.pkg.

<?xml version="1.0" encoding="utf-8"?>
<installer-gui-script minSpecVersion="1">
    <pkg-ref id="com.foo.bar.pkg">
        <bundle-version/>
    </pkg-ref>
    <options customize="never" require-scripts="false"/>
    <choices-outline>
        <line choice="default">
            <line choice="com.foo.bar.pkg"/>
        </line>
    </choices-outline>
    <choice id="default"/>
    <choice id="com.foo.bar.pkg" visible="false">
        <pkg-ref id="com.foo.bar.pkg"/>
    </choice>
    <pkg-ref id="com.foo.bar.pkg" version="1.0" onConclusion="none" installKBytes=“3">#FooBar.pkg</pkg-ref>
    <product id="com.foo.bar.pkg" version="1.0"/>
</installer-gui-script>

Hi Rich

You may already know this trick but in case you haven't I noticed an easy way of getting First-Boot-Package-Install to work with bootstrappr, I add my First-Boot-Package-Install package and package that installs a LaunchDaemon that triggers a script to reboot the machine.

When the machine reboots First-Boot-Package-Install kicks in and installs my packages (this works really well for quickadd), I am seeing the issue with the process page not appearing but that's no big deal.

Thanks for all your work it is greatly appreciated!

Alex

Hi,
In High Sierra, the LoginLog appears, but it doesn't list the pkgs which are installed. There is only an empty window. In fact, all the pkgs are correctly installed (but I can't see if the installation of a package makes an error).
This morning, with macOS 10.13.3, it's worse, LoginLog doesn't appear anymore. But again all the pkgs seem to have be correctly installed.
An idea ?