Scripted Install Not Working

[LyleMagdalinski]

I am attempting to automate the installation and configuration of ESX 3 using a KickStart script.

I have enabled the WebAccess-based KS script generator and created a sample KS.CFG file.

The server I am testing this script file with is an HP Proliant BL460c -- therefore no local CD-ROM or floppy drive. I have used iLO Virtual Media to mount the ESX .ISO and KS.CFG .flp images on the server.

I boot the server and at the ESX mode selection page enter -

'esx method=cdrom ks=floppy'

However, ESX doesn't seem to read the KS script. No error messages are displayed, but none of the customizations I configured are enabled. Basically, the installation runs as if no customizations have been specified,.

I have also tried upload the KS.CFG file up to a MS IIS 6.0 server and specifying it on the ESX mode selection page -

'esx method=cdrom ks=http://servername:8080/ks.cfg'

Same result. No errors, but no customizatons.

I've checked the IIS log files and the HTTP gets are successful (ie STATUS=200).

What am I missing here?

[Texiwill]

Hello,

Could you post your ks.cfg file? I think you may have some lines in it preventing its usage.

I have successfully used both methods and have no issues.... Can you tell me the first screen you have to enter something in on after you enter your boot line? It could be that it is confused on networking and is just asking for which adapter and then will continue the scripted install after the information is provided. Change your boot line to be:

esx text ks=http://servername:8080/ks.cfg method=cdrom ksdevice=eth0

One thing you may want to do is place a copy of your ISO/CDROM contents on your web server, that way you can install without requiring to hook up the virtual cdrom.

Best regards,

Edward

[LyleMagdalinski]

Thanks Texiwill,

Here's my install file. Nothing too fancy... mostly defaults.

I've tried using the command line you have provided. By specifying ksdevice=eth0, I am no longer being prompted for the adapter, as before.

The first screen I now see is 'Choose Language'. Then 'Choose Keyboard', followed by 'Test Media'. Then the 'ESX 3 Installer Wizard' begins... I stop when it asks me to accept the license agreement.

=================================================

\# Auto-Generated Scripted Install Configuration file.

\# This file is used for VMware ESX Server Scripted Install Deployment

\# Installation Method

cdrom

\# root Password

rootpw --iscrypted $1$ucyVzrfI$C/Fb1Mr4Dx4XFY8Nkbuiz/

\# Authconfig

auth --enableshadow --enablemd5

\# BootLoader ( The user has to use grub by default )

bootloader --location=mbr

\# Timezone

timezone America/Edmonton

\# X windowing System

skipx

\# Install or Upgrade

install

\# Text Mode

text

\# Network install type

network --bootproto dhcp --addvmportgroup=1 --vlanid=0

\# Language

lang en_US

\# Langauge Support

langsupport --default en_US

\# Keyboard

keyboard us

\# Mouse

mouse none

\# Reboot after install ?

reboot

\# Firewall settings

firewall --disabled

\# Clear Partitions

clearpart --all --initlabel --drives=sda

\# Partitioning

part /boot --fstype ext3 --size 102 --ondisk sda

part / --fstype ext3 --size 4997 --ondisk sda

part swap --size 544 --ondisk sda

part None --fstype vmfs3 --size 10000 --grow --ondisk sda

part None --fstype vmkcore --size 94 --ondisk sda

part /var/log --fstype ext3 --size 1992 --ondisk sda

\# VMware Specific Commands

vmaccepteula

vmlicense --mode=server --server=27000@MYSERVERNAME.COM --edition=esxFull

%packages

@base

%post

%vmlicense_text

[Texiwill]

Hello,

A few things....

1) Do not post your passwords even encrypted as they can be broken using rainbow tables in a matter of hours...... Depending on the tables and speed of the machine involved....

2) It sounds like it can not find your ks file at all... Check your Web server error logs and the permission of the ks.cfg file. Is the file named 'KS.CFG' or 'ks.cfg' on the server? It is just not finding it and case is important on the boot command line.

Best regards,

Edward

[LyleMagdalinski]

No worries. That's just a dummy password.

Discovered that the ESX Installer was not liking the non-standard 8080 port in the KS=HTTP:// command. I instead used FTP and the Installer is now processing the script file.

[Texiwill]

Hello,

Really.... Interesting, I will have to try with a non-standard port.. It should work if the port is specified.... Hrm.

Glad you got it to work using ftp.

Best regards,

Edward

[admin]

Hello,

1. I got problem to make the installation on a non standard port so I decide to get back on the port 80 and everything work well.

2. To solve your remote installation problem you can first try to make a "text" installation... that will give you the chance to manually file the HTTP parameters and know where the process failed.

3. Your IIS must be configure to accept "anonymous" connection

4. Add the installation method in the kickstart file and try this command line : text ks=http://servername/ks.cfg ksdevice=eth0

[tsugliani]

Using text install, you should check all consoles to see in detail what the pb is.

Using altF1/F2/F3/F4/F5/F6 to switch console, i think installer (anaconda output) is on VT 3 or 4, so check them using altF3, alt+F4 and try to find any usefull message.

After that we could help you more precisely i think.