[Justin-Credible]

I've been developing an application off and on for a year or so. Its basically a front end for building a bootable CD that automatically installs Windows.

You can add drivers, customize the unattended answer file, specify how the hard drive should be formatted etc. Then you burn the ISO to disc and you have a fully automated Windows (2000 or XP) install disc.

I originally designed this for my co-workers to use after I leave (I'm the only one who was able to create automated installation discs for them), so it should be easy enough for anyone to use.

It does make use of Windows PE, so you will need a WinPE disc to build your ISO.

I used a lot of information from the Windows PE board here (great forum!!) and I thought someone might find this tool useful.

You can download it here: AutoInstall CD-ROM Builder

And some screenshots: Click Here

[sintaxasn]

Let me be the first to say, well done, excellent solution. I'm actually working on something pretty much identical for my company, which basically allows every country to configure XP to their liking, while still having a common configuration (apps, policies etc).



Dan

This post has been edited by sintaxasn: 22 June 2005 - 06:55 AM

[Astalavista]

Let me pls second that!

Holy cow! it is awesome...

but how do u install applications?

[Justin-Credible]

We use Active Directory where I work so all the applications and settings are pushed out when the computer reboots after the install.

For the next version (if I have time ) will be to add more customization (for RUNONCE and other things that will let you install applications after reboot).

Any other suggestions would be appreciated!

[Astalavista]

A large number of uses use WPI method. pls add an option for this method.

thank you!

again great work

[Justin-Credible]

I took a look at WPI, and I have to say I was quite impressed with it being a HTA and all.

I don't think I will be adding it into AutoInstall CD-ROM Builder because it is a bit more advanced to setup and get working for a normal user. However my program does have an option to add additional files before the ISO is finalized, so you can add it manually.

[MAVERICKS CHOICE]

Justin-Credible, on Jun 26 2005, 09:09 AM, said:

I took a look at WPI, and I have to say I was quite impressed with it being a HTA and all.

I don't think I will be adding it into AutoInstall CD-ROM Builder because it is a bit more advanced to setup and get working for a normal user. However my program does have an option to add additional files before the ISO is finalized, so you can add it manually.
<{POST_SNAPBACK}>

Just Dled & installed very promising Justin, great program .

[dirtwarrior]

very kewl

[Bilou_Gateux]

It's Just Incredible

awesome tool.
even the GUI is well designed.

Thanks for sharing your work!

some typos errors in v2.2 build 199 you might want to edit for the next build
Answer File > Dynamic Answer File Parameters > Add Parameter
Choose a catatory:
Choose a paramter:

This post has been edited by Bilou_Gateux: 26 June 2005 - 04:26 AM

[Justin-Credible]

oops. Thanks for letting me know. I had a hard time getting those drop down boxes to work, I guess I was so tired of working on them I never came back to check them after they were working.

This post has been edited by Justin-Credible: 26 June 2005 - 11:14 AM

[Shotgun]

Can I use Bart's PE instead of Microsoft PE?

[oioldman]

looks a fantastic program, and i'll certainly have a look.
where can i get a copy of WinPE from though?

[Bilou_Gateux]

Shotgun, on Jun 27 2005, 06:18 AM, said:

Can I use Bart's PE instead of Microsoft PE?
<{POST_SNAPBACK}>

Furthermore, what are exactly the files needed from the winPE CD?

i have actually Windows OS (2003 Web w/o SP) English + MUI and a localized WinPE CD (French Windows Server 2003 OPK w/o SP) and i'm not sure i can use source CD with different languages.
if i slipstream first SP1 to my Windows OS CD and burn a new CD, will it works with my w/o SP WinPE CD.

Before starting my first AutoInstall CD with your tool, i want to be sure what can be done?

Otherwise, i will first try with Windows 2003 Standard French and WinPE CD (French Windows Server 2003 OPK)

Note: w/o SP = without Service Pack

@oioldman
Tools: Microsoft Windows Preinstallation Environment

Bart's Preinstalled Environment (BartPE) bootable live windows CD/DVD

This post has been edited by Bilou_Gateux: 27 June 2005 - 06:51 AM

[oioldman]

@Bilou_Gateux, Thanks, for the links.
Hope it works with BartPE as we don't have WinPE within the company and certainly not able to afford it via the license methods.

[gmx]

nice app i like some of your other application remote copy too thanks

[Bilou_Gateux]

Ok, starting to play with the tool.
@all
Basically, Justin-Credible has made a nice tool to achieve the method described Deploying Windows XP, Using the Windows PE
Booting from a Windows PE CD (or DVD) which contains a copy of the operating system source files.
and allows customization of the operating system source files (unattended install + adding OEM Drivers)
and a nice GUI front-end.
have put a lot of time to make it

I have checked the "View Build Details" to debug the build.

• You cannot use BartPE: "AutoInstall CD-ROM Builder v2.2" uses the MSFT tools located in the \WINPE folder of the "WinPE OPK CD" to build a new bootable CD.
  
• My first build fails because "AutoInstall CD-ROM Builder v2.2" searchs for Factory.exe and Netcfg.exe in the \I386 folder of the "WinPE OPK CD".
  On my "WinPE OPK CD", both exe's are located in \TOOLS\X86 and in \I386\SYSTEM32
  
• The "AutoInstall CD-ROM Builder v2.2" use xcopy.exe. If you're running a Lite flavor of Windows on your box, checks this command line utility has not been removed...

@Justin-Credible
Feature request:

• Section Interface: Small Banner Image
  can you add Windows 2003
  
• Section Interface: we can configure "Bootup text" (loader prompt in TXTSETUP.SIF)
  can you add configure "NoGUIBoot"

How to boot the Windows Preinstall Environment from an RIS server by using PXE-enabled clients

Quote

At the line that begins "OSLoadOptions," add the /noguiboot switch. For example, type OsLoadOptions = /noguiboot /fastdetect /minint.

Question:
Section Drivers > Drivers Used During Install (Mass Storage Devices)
Are these drivers integrated to $OEM$\TEXTMODE in AI\SOURCE\I386 (OS Source)and WINNT.SIF/UNATTEND.TXT relevant section or
Are these drivers integrated to I386\SYSTEM32\DRIVERS and relevant section in TXTSETUP.SIF(WinPE)
How to add unsupported or updated third-party mass storage drivers to a customized WinPE CD
or
both?

If i add a specific mass-storage driver not included in the original Windows source CD, i need it both in WinPE to have access to the drive connected to the controller during boot and in Windows source CD to allow unattended install on the drive.


Notes: (from the help file)
AutoInstall CD-ROM Builder uses the Windows PE 1.2 image builder engine which has a known bug when using a Windows XP SP2 or Windows 2003 Server SP1 disc to build it. This bug prevents the Disk Partition command line tool (diskpart.exe) from being able to run, which will render your DiskPart scripts unusable. It is recommended that you use a regular Windows XP (or XP SP1) or a regular Windows 2003 Server disc to build your AutoInstall CD.CD.

@Justin-Credible
This problem has been solved by Bart when building BartPE CD with Windows 2003 Server SP1 or Windows XP SP2 binaries
dcomlaunch plugin
FAQ #17

Quote

Q: When I boot BartPE build from WinXP/Sp2 from CD-Rom, diskpart does not work. When I try to execute diskpart, I get the following message: The disk management services could not complete the operation.
A: You must enable the dcomlaunch plugin "RpcSS needs to launch DComLaunch Service first - SP2 only".

Maybe can you add the needed reg data and values to the hives when building WinPE?

This post has been edited by Bilou_Gateux: 27 June 2005 - 08:58 AM

[Justin-Credible]

Wow, didn't expect to see so many posts here! Lets see...

Bilou_Gateux-- I haven't messed with MUI packs or different languages of Windows. All I can say is... give it a try I would suggest using VirtualPC or VMWare to test your disc before you burn it.

Let me clarify something here... The "Windows Installation Source CD" is the path to the files of the version of Windows you want to install on the target computers. The "Windows XP or Windows 2003 Server" is the path to a version of Windows (XP or 2003) that you will use to build the CD and its graphic interface (this has nothing to do with the OS that is installed, it simply makes the interface).

The only combination of the two that will have problems is if you are using a Windows XP SP2 or Windows 2003 Server SP1 disc as the "Windows XP or Windows 2003 Server" with Windows PE 1.2. This causes the Disk Partitioning feature to not work because of a bug in Windows PE 1.2.

I did see the Q/A about the DComLaunch Service from BartPE, but I didn't have time to get this to work in Windows PE. I do plan to fix this in the next version.

As far as files that are used from the Windows PE CD; only the files under the WINPE folder are used.

I did plan on doing a version that would allow you to use either WinPE or BartPE to build the disc, but again due to time limitations I didn't get to include that feature in this version.

As for the drivers question; The "Drivers to Install with Windows" are driver sets (.INFs with a bunch of additional files such as .SYS, .VXD, .DLL, etc). These are the drivers you normally download from the web or get from a motherboard CD.
These drivers are copied to the root of the hard drive, are are added to the unattended answer file (WINNT.SIF) so during Windows PnP hardware detection, the drivers will be automatically installed. These drivers are stored in the \AI\SOURCE\i386\$OEM$\Drivers folder on the CD.

"Drivers Used During Install (Mass Storage Drivers)" are drivers (.SYS) that you normally nload by pressing F6 during a normal install of Windows. This is a driver file that allows you to access a hard drive that may be on a SATA or SCSI controller that WinPE doesn't include by default. This gives you access to the hard drive during bootup and will allow you to install files to the HDD. These drivers are added to the TXTSETUP.SIF file and are placed in \i386\SYSTEM32\DRIVERS directory on the CD.

So if you need a mass storage driver, yes, I do believe you will also need the drivers for the "Drivers to Install with Windows" section.


Here is what I have planned for the next version:
Windows 2003 Small Banner Option
Fix spelling errors
Support for BartPE
Ability to use the /noguiboot switch
Include XCOPY for those systems that do not have it

[Bilou_Gateux]

Thanks for the clarification.

Just received a new french WinPE 2005 OPK CD.
I have checked the \WINPE\WINPESYS.INF and new registry keys value and data are added:

;; XP SP2 Specifics;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

[AddReg.5.1.2]

HKLM,"Setup\AllowStart\DcomLaunch"

HKLM,"ControlSet001\Services\DcomLaunch","Description",0,"%REMOTE_PROCEDURE_CALL_LAUNCHER_DESCRIPTION%"
HKLM,"ControlSet001\Services\DcomLaunch","DisplayName",0,"%REMOTE_PROCEDURE_CALL_LAUNCHER_SERVICE%"
HKLM,"ControlSet001\Services\DcomLaunch","ErrorControl",0x00010001,1
HKLM,"ControlSet001\Services\DcomLaunch","Group",0x00000000,"COM Infrastructure"
HKLM,"ControlSet001\Services\DcomLaunch","ImagePath",0x00020000,"%SystemRoot%\system32\svchost.exe -k DcomLaunch"
HKLM,"ControlSet001\Services\DcomLaunch","ObjectName",0x00000000,"LocalSystem"
HKLM,"ControlSet001\Services\DcomLaunch","Start",0x00010001,2
HKLM,"ControlSet001\Services\DcomLaunch","Type",0x00010001,32
HKLM,"ControlSet001\Services\DcomLaunch\Parameters",,0x00000012
HKLM,"ControlSet001\Services\DcomLaunch\Parameters","ServiceDll",0x00020002,"%SystemRoot%\system32\rpcss.dll"

HKLM,"ControlSet001\Services\Rpcss","DependOnService",0x00010000,"DcomLaunch"

I hope it will solve the diskpart issue with the newest WinPE OPK 2004 & 2005 CDs.

You can release an intermediate release (build 200?) with only small changes which do not requires too much work:

Quote

Windows 2003 Small Banner Option
Fix spelling errors 
Ability to use the /noguiboot switch

Quote

Include XCOPY for those systems that do not have it.

It's not really necessary as most users works on regular Windows. If the file is missing, it's just as easy as copying it in our %Windir%\system32 folder.

This post has been edited by Bilou_Gateux: 28 June 2005 - 03:36 AM

[NikLok]

Whether to me here it is interesting the given program can to collect a disk from different catalogues.
The matter is that at configuration of disks for systems w2k wXp w2k3 wXp64 it is necessary to store{keep} the same set of distribution kits in each catalogue of a target disk as I create iso an image by means of program CDIMAGE 2.47 © Microsoft, 1993-2000. The given program takes files and catalogues only from the catalogue of a source, but not the list of catalogues.
Therefore such structure is duplicated in catalogues for all systems. It borrows{occupies} a lot of place, but also very uneasily to update their contents. Use of symbolical communications{connections} under wXp has not helped{assisted}. Them CDIMAGE 2.47 for catalogues ignores! There can be your program solves this problem more elegantly, or you know the best decision?

[cobyjones]

I tried using the dynamic answer file. but every time i get to the third dynamic parameter, i get the following error:
Run-time error '9':
Subscript out of range

any ideas?