Winbom.ini

[rdalling]

Quick question for everyone, does anybody besides me use winbom.ini to install software on an unattended build before they reseal with sysprep?

[robr]

depends what you mean by using winbom to install software. i use winbom.ini to point to the WinPE configuration on the network, the WinPE software installs are located in the config set. No idea if you mean something else by using winbom.ini.

[rdalling]

I work for a large corporation (in the top 25 of the fortune 500) in the Enterprise desktop support dept. I have been tasked with rolling out XP to 6800+ desktops of 15 different hardware builds. My process is as follows:

-I boot WinPE and login to a Novell network

-I kick an install script which does the following

-- Partitions the drive into 2 partitions

-- copies all the source for windows XP, patches, programs that are generic to the company

-- copies all source that is specific to the model of the computer

-- kicks Winnt32 as an unattended install

-The system reboots and the process continues until it starts using Winbom.ini. I use 3 different Winbom.ini files. The first has unique information about each PC that I’m building. the second winbom.ini has all the standard applications we install on each computer. the third winbom.ini is the cleanup phase and removes everything we don’t want to keep on the computer before we call a sysprep and ghost the computer for distribution.

Basically, I'm wondering if there are others in the forum that do the same thing (process) that I have setup for consistency.

Roger

[n00b]

I use Winbom.ini (sysprep factory preinstallation) but I only use one Wimbom.ini. I install all my apps, hotfixes, and do cleanup at the end.

One major problem I have with it is that the digital signatures for the drivers are lost ... XP thinks my video/NIC driver is not digitally signed