Issues with unattended install of 2K Server Std from CD

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Okay, so I found out that it wasn't properly reading my unattend.txt file.
Fixed that, now I have another issue just as bad. Setup fails with the
message "Setup was unable to copy the file" blah, blah, blah.

It actually fails on every file in the OemBootFiles section of the
unattend.txt file. Why? I have created the appropriate directory structure
on the cd ie.

\i386
\$oem$\
\$1\Drivers\SCSI
\Textmode

At least, this is the way I understand it needs to be. The OemBootFiles
section lists every file in the textmode directory since they are necessary
for the Smart Array 6i controller the Dl380's have. Please help, I have
exhaustingly searched the web and can't find anything helpful.
Obviously, setup then fails completely and blue screens at the next reboot
when it tries to boot to the c drive.



"Jared" wrote:

> Alright, I appreciate ahead of time any input you can give me to this issue.
>
> I am currently using the compaq smart start scripting tool kit to build an
> unattended install of Windows 2000 Server Std. Although I had numerous
> problems with getting it to work on our Compaq DL380 G4's, I have finally
> been able to get it to successfully begin setup. It also successfully copies
> all files during the text mode until it reaches 100%. At that point, the
> activity led's on the hard disks go to nearly a constant flash and the setup
> stops. there are no stop messages or anything, it just stops at 100% and
> stays there. Anyone have any idea what the heck could cause this.
>
> I have modified my unattend.txt a dozen times changing the
> oemextendpartition, the autopartition, the filesystem sections to no avail.
> It obviously is loading the Smart Array 6i drivers okay otherwise it would
> fail before it began to copy files to the partition on the only volume on the
> computer.
>
> Please help.

Archived from groups: microsoft.public.win2000.setup_deployment (More info?)

Oh yeah, and the files in the oembootfiles section only include the file
names and not the complete paths. remember, this is from a cd.

"jhedman2" wrote:

> Okay, so I found out that it wasn't properly reading my unattend.txt file.
> Fixed that, now I have another issue just as bad. Setup fails with the
> message "Setup was unable to copy the file" blah, blah, blah.
>
> It actually fails on every file in the OemBootFiles section of the
> unattend.txt file. Why? I have created the appropriate directory structure
> on the cd ie.
>
> \i386
> \$oem$\
> \$1\Drivers\SCSI
> \Textmode
>
> At least, this is the way I understand it needs to be. The OemBootFiles
> section lists every file in the textmode directory since they are necessary
> for the Smart Array 6i controller the Dl380's have. Please help, I have
> exhaustingly searched the web and can't find anything helpful.
> Obviously, setup then fails completely and blue screens at the next reboot
> when it tries to boot to the c drive.
>
>
>
> "Jared" wrote:
>
> > Alright, I appreciate ahead of time any input you can give me to this issue.
> >
> > I am currently using the compaq smart start scripting tool kit to build an
> > unattended install of Windows 2000 Server Std. Although I had numerous
> > problems with getting it to work on our Compaq DL380 G4's, I have finally
> > been able to get it to successfully begin setup. It also successfully copies
> > all files during the text mode until it reaches 100%. At that point, the
> > activity led's on the hard disks go to nearly a constant flash and the setup
> > stops. there are no stop messages or anything, it just stops at 100% and
> > stays there. Anyone have any idea what the heck could cause this.
> >
> > I have modified my unattend.txt a dozen times changing the
> > oemextendpartition, the autopartition, the filesystem sections to no avail.
> > It obviously is loading the Smart Array 6i drivers okay otherwise it would
> > fail before it began to copy files to the partition on the only volume on the
> > computer.
> >
> > Please help.