From a pure functional standpoint, I don’t see any major difference between what is available in prior versions of OS X Server in terms of NetBoot service to the Mt Lion version; other than it is now “NetInstall”.
There are some minor changes such any mention to support OS9 has been removed, and you cannot set the log level via the GUI. If you really need to increase the log level for NetInstall, run the following command:
NetInstall Configuration Settings
From the first Image you can see we have the options to select an interface to provide our NetInstall service. This will always be an Ethernet unless you enjoy a slow painful death of being attacked by a swarm of bees. You can also filter by Mac Address on the primary page (machine model filtering is possible, just not on the first tab).
And finally, you can assign if you are storing Images, Client Data (for diskless operations), or both.
On the Images tab, you will be able to see your NetBoot/NetInstall/*.nbi listed (once you copy to the usual /Library/NetBoot/NetBootSP0 folder). From there select the name of your image and click on the gear icon to “Edit Image Settings”.
From there you can select the protocol (NFS or HTTP), filter Machine Model Access, adjust the image index, and finally if you want this *.nbi to be provided in diskless mode.
Comments are closed. If you have a question concerning the content of this page, please feel free to contact me.
Since upgrading to mountain lion nfs won’t start automatically at boot… but i can start it manually. I’ve configured in etc/exports the nfs mounts to be available.
The nfs mounts are in an external disk (Share HD).
I think to do that I’ve to start NetInstall.
I edit storage settings and indicate Share HD to be storage for clients and data. Every time i turn NetInstall on i Get the message “Unable to start Netinstall. To start netinstall, you must have at least one image available to acres by clients.”