Solution Concepts

Hax - OS - Remote Installation

 

"Making IT happen on the
Information Superhighway"

 

2600 | Antionline | Astalavista | Blacklisted 411 | Crypto-Gram | Defcon | Geeks Are Sexy | IT Conversations | Shoutwire | Slashdot | Tech Tales | The Daily WTF |

Forums | Linux | News |Telephone | Windows |

 
http://ask.slashdot.org/article.pl?sid=06/06/09/1831211 

Remote Installation Applications  

Remote Installation Notes from various sources #1  
  • I use a single image that operates on Dell GX110, 150, 260, 270, HP DC 7100c, HP xw8000, Compaq 1830 laptop, Dell C500, C510, C600, C610 and D610 laptops, Dell P650 and P670, and Dell Precision M70 laptop. I think that's it, but it's kinda hard to keep track of them all.

    The ACPI isn't the biggest problem. The main problem is, astoundingly, the IDE driver.

    Here's what you do.
    1. Install Windows on a system and then load all the drivers.
    2. Set it for Uniprocessor ACPI.
    3. Set the IDE driver to the generic driver.
    4. Move the drive image to another system (swap hard drives, clone the drive with Ghost, whatever).
    5. Boot up, install drivers for new system.
  • 6. Move image to previous system.
    7. Set for system-specific IDE driver.
    8. Repeat steps 3-7 for each type of system.
    9. Move image to last system and switch to system-specific IDE driver.
    10. Sysprep and save a Ghost image.

    Also, if you're using a lot of different types of systems with GhostCast Server, PXE booting is the only way to fly. Use pxelinux (part of syslinux) with the keeppxe option along with the 3COM universal NDIS driver, and you'll never have to worry about NIC-specific drivers with Ghost again (unless you have a system that can't boot PXE, like my Compaq 1830s -- they're a pain in the ass!) If you absolutely can't boot PXE, use Bart's tools (BFD and BCD) to make a bootable floppy or CD-ROM with all the drivers.

Remote Installation Notes from various sources #2  
  • Ok some tools I use to make my life easier (all free):

    • nlite (creates unattended installs, needs dotnet) slipstreams automatically service packs and hotfixes and allows other unattended options (more then MS tools). w2k and higher only. http://www.nliteos.com/ [nliteos.com]
    • autopatcher contains all the hotfixes, tweaks and third party extras like dotnet 1,2, flash, shockwave, java. http://www.autopatcher.com/ [autopatcher.com] **
    • driverpacks contains all the winxp drivers in existence (I think) http://driverpacks.net/Projects/DriverPacks/ [driverpacks.net]
    • RVM packs, contains hotfixes and some extras. And is compatible with nlite. http://www.ryanvm.net/msfn/ [ryanvm.net] 
  • Basic usage:
    • Drop the contents of your winxp install CD onto your HD. Download the latest service pack.
    • Start and Point nlite to both.
    • Choose any option that you like but don't create an iso.
    • It will automatically integrate the service pack.
    • About integrating hotfixes see RVM packs, which is compatible with nlite. http://www.ryanvm.net/msfn/ [ryanvm.net] (also more info about appz integration)
    • Again options, choose what fits you. (Talking about nlite)
    • Save
    • Now follow the driverpacks site instructions to add the drivers to your install CD/DVD.
    • About integrating extra applications see: http://unattended.msfn.org/unattended.xp/page/list /switch/ [msfn.org] for general info look at its home site: http://unattended.msfn.org/unattended.xp/ [msfn.org] and google for specific appz.
    • After first boot run autopatcher latest version. (if needed, RVM packs if done well, don't need this step)
    • Run your personal little script.
    • Now you have a working winxp installation with all tools and most actual updates.
    • Deploy!

Remote Installation Tutorials  
  •