Windows 2003 DL360 - Scripted install

[Donald Schofield_1]

I have created an installation using the smart start scripting tool kit. The script does not run any of the array, or lo config etc.

The scripted install runs using “statemgr” and “reboot” out of HP SS toolkit.

The windows server 2003 installation works perfect on all existing DL360 G3 -380 G3 servers which have had a previous version of windows server via the standard smart start cd installed. To test I have been trashing the raid logical volume and building from scratch. The scripted install works using $OEM$ drivers and winnt /s:s:\i386 /u:c:\unattend.txt etc etc

The problem I am having is with a new DL360 out of the Box.
The installation partitions the drives using ranish partition manager (Due to Hp script tool 4gig limit)and reboots the server using hp reboot

The script continues to runs

####################################
copy a:\unattend.txt c:\
c:
md SP
a:\xcopy s:\sp c:\sp /s
echo Setting State Information...
s:\cpq\statemgr /w Phase 5

:State5
s:\cpq\statemgr /w Phase 6
echo Starting operating system installation...
if not exist c:\unattend.txt goto InstErr
s:
cd \i386
winnt /s:s:\i386 /u:c:\unattend.txt

####################################

Once server reboots, It cannot boot to the active partition. I can boot via dos boot disk and access ok. I have checked to make sure the partition is active and boot files etc.

1.The installation previously worked on servers which have been built using smart start cd.

2.I built the “new” server using standard smart start cd. (Worked without any problems) then deleted raid logical vol – re created. I then started my scripted installation (reset server install phase to 0 etc) which worked without any problems (Full installation of windows 2003)

Q.Does the smart start CD make some form of change to system ROM/Bios etc when run for the first time??

Thanks for reply’s

[snolet]

Does your RAID controller is set as boot controller ?

[Steven Clementi · Accepted solution]

If it is the only array controller, USUALLY it will set automatically as boot device. I think the problem lies within the LUN creation though. Are you automatically creating the the Boot Lun? or manually? Smartstart will create the LUN and set it so that it can boot when doing a SS install.


I use RDP and one of the things I have seen in the scripted Installation is that the srcipt runs "setactiv.bat" (or maybe .exe), eitherway, it is a Smart Start Scripting Utility tool that sets a newly created logical drive "active".. or "Bootable". After the server reboots, the install files get copied and Windows Install runs no problems.


Steven

[Donald Schofield_1]

Thank-you Steven, I will look into the Scripting Utility tool that sets a newly created logical drive active.

Cheers - Don