Truely excelent appliance. We deploy too few to set up our own server, but enough that this saves us bunches of time.

useful to play around with...but is it going to be useful in the real world ?

Windows 2000 problem
------------------------------
* Remote installs of windows are currently only tested in other virtual machines (this is due to the fact that the virtual machine network card is detected correctly) I'm still trying to find a good solution to make all drivers included with the windows distributions available throug the UDA.

* You can see what happens in the logfile of the tftp daemon. It is /var/log/messages

* Please make sure that the ISO file is mounted correctly and that it is accessible through samba from your host operating system. \\<UDA-IP-Address>\REMINST (when prompted for username and password try 'guest' with no password.

Windows XP professional problem
-------------------------------------------
* The NTDETECT fails is probably because the virtual machine tries to get the kernel files from a different location. Make sure the DHCP daemon is configured correctly for your network. (check /var/log/messages for DHCP logging) Also edit the configuration file of the template and make sure the IP adress mentioned in it (twice) is the IP adress of the UDA

* Also check the tftpd log (/var/log/messages) and the logfile of the binlserver (/var/log/binlsvr.log) (this service responds to requests about which network driver is needed for the network card ID of the client to setup.

* Make sure the template boot files are generated correctly
-> /var/public/tftproot/pxelinux.0<template>.sif
-> /var/public/tftproot/pxelinux.0ntd<template>.com
-> /var/public/tftproot/<template>.0
-> /var/public/tftproot/<template>

Please feel free to ask more questions and report problems.

Well I've just tried to install windows XP pro and 2000 pro but no way !
I used the VM image as you leave it. I changed my network settings with an IP address like 10.0.0.x but it doesn't work with any OS.
I disabled every devices except HDD and Network card, but I've got the same results.
Well I don't know what to do ... It seems like network doesn't work (no activities when I look at the VM icon). However, the DHCP works fine. I tried with a "real" computer and I've got the same result.

I was looking at /var/log/messages but there are no errors.

Maybe I'm cursed !? lol

Can it be because I used French versions ?! Well I think not ....

Message was edited by:
Frantic

Hi there,

I'm trying to deploy Win XP Pro to a laptop with no cdrom drive or fdd. Toshiba, in all their wisdom, replaced my HD and handed it back blank and I can't be bothered taking it back.

Soooo..

I've not changed any default settings. I've set my windows server PC to have an IP of 10.0.0.10/255.0.0.0.

I've logged into the web interface as admin.

I've added my mount point, 10.0.0.10/winxp
I've clicked mount, and it's successfully mounted

I click on OS
I click configure next to 'winxp'
It comes up with share name 'winxp'
The ISO drop down is always blank, but if I look at /var/public/smbmount/winxp on the console, sure enough the drive is mounted and the ISO, winxp.iso is clearly in there. I have full write permissions (verified by 'touch').

I think "stuff it", and mount the ISO by hand -
mount -t iso9660 -o loop /var/public/smbmount/winxp/winxp.iso /var/public/tftproot/WINXP
It successfully mounts.

I save everything, and boot the laptop. It comes up with:

For help press <F1>

Current Templates:

ID Description
+-----+-------------------------------------------------------+
winxp Windows XP
boot:

I type in 'winxp' - get back "Could not find kernel image: winxp"
I type in 'WINXP' - get back "Invalid or corrupt kernel image."

I'm stuck. Any advice you can give me please? Is this because I manually mounted the ISO? Why can't it see the ISO listed?

Any help you can give me is appreciated, I REALLY want to get this laptop working again..

Thanks
-p

Hi pulse,

First of all: the version that was release initially doesn't support another physical machine (read: your laptop) since it can handle only VMware specific network cards. The good news is: I think I have a working version at home that will support other NIC's as well. As soon as I've tested it I will release it... (I hope before august 1st)

Now for you specific problem:
I think I've had the same problem some time ago, and this is due to a bug in the script. It shows all but one iso file in the shared directory. (and since you probably you only have one iso file in that directory, it shows none) You can test it the following way: touch a new file bogus.iso in the shared directory.

When you now go to the configure option again, you should see one iso file (since you now have two). you will probably see the winxp.iso file in there now... (if you see only the bogus.iso try making a second copy of your winxp.iso file in the same directory (with a different name of course), it will show you at least one then...)

If this works for you you can go ahead and fix the script:
/var/public/cgi-bin/uda.pl
Search for the word javascript
A few lines below it it reads:

for ($i=0;$i<$#allisos;$i++)

change it to (insert an '=' symbol)

for ($i=0;$i<=$#allisos;$i++)

When the configure option has run successfully (it mounts the iso and imports the generic bootfiles for winxp), the create template (copying and modifying the bootfiles slightly for the template you create) will also run better...

Good luck and let me know if it worked!

I tried cutting out the middle man, I edited /var/public/conf/os.conf to include my ISO filename manually. It showed it in the OS screen, I clicked mount and it mounted successfully.

Job done, I thought.

Went to create a template, and got the same output as above, with startrom failing. It still hasn't created any template files.

D'oh!