Actually that should have been semaint and it did work - needs a little refining though..
Migrating to OS/2 Warp Server for e-business (SG24-5135-00) has add some additional information in chapter 5 that could be useful when using SRVIFS approach also for pristine installations. The network redirection is nowadays the most convenient way to install every OS/2 version starting with Warp Connect (beyond bare metal recovery solutions to identical hardware). For a small bunch of systems it may sound too time-consuming regarding the preparation. But this approach will pay off when dealing with dozens of virtual machines or you have to create emergency plans and procedures - I know it's a boring topic.
I don't know of your network infrastructure, but we keep at most sites OS/2 Warp Server with RIPL service to help with critical system administration tasks for Intel-based servers. Using a DOS RIPL requester via a dedicated network adapter can deliver any diskette (image) to a machine without a floppy drive. And it works for firmware updates of the system BIOS or RAID controllers. For Thinkpads a docking station with a RIPL-capable network adapter is a real time saver. Only one machine definition is needed for the DOS RIPL requester which contains only tools to create a small FAT partition a copies the required device driver files on it. Alternatively it's also possible to write prepared images. Perhaps somebody remembers IBM's LCCM which had much more capabilities and integration features?
Of course this step is not required if your OS/2 system installation is also performed via RIPL or PXE (without any local installation media) which should automatically include the NDIS drivers via response files or a similar mechanism. Profound knowledge in this area is not limited to OS/2-based installations, the same concepts are used for high-availability or redundant solutions using Windows Servers.