Seite 1 von 2
Bug in unattend.xml / Win7-64
Verfasst: 31 Mär 2012, 00:16
von topse
Hi,
I have set up server and client in VBox - for getting started and developing packages.
Automatic Installation of Win7-64 stops with an error, something with "error in unattend.xml in paragraph specialized". I found the following line to be the problem:
Code: Alles auswählen
<settings pass="specialize">
(...)
<ComputerName>#@pcname*#</ComputerName>
When I substitute "#@pcname*#" with a "real" Computername - then it works fine. Does anyone have an idea, what the problem is? Automatic substitution of the variable fails??
Thanks and Best Regards,
Tobias
Re: Bug in unattend.xml / Win7-64
Verfasst: 02 Apr 2012, 18:09
von d.oertel
Hi,
in any way you did not give the name of the client to opsi.
I assume that you missed the form 'Configuration incomplete'
see here:
http://download.uib.de/opsi_stable/doc/ ... ent-bootcd
If I'm right, it isn't a bug.
If I am not right, you should give the log of the boot image.
regards
d.oertel
Re: Bug in unattend.xml / Win7-64
Verfasst: 04 Apr 2012, 19:51
von topse
Sorry - I don't know, if I did not get you correct.
I am using the graphical opsi config editor. When I "create a new opsi client" then I am asked for a name. And for the given client, there is a valid name. I was assuming that this name I give here together with the MAC-Address would be the identification and name-giving for the client from opsi's point of view?
Do you mean something else?
Thanks and Best Regards,
Tobias
Re: Bug in unattend.xml / Win7-64
Verfasst: 05 Apr 2012, 11:19
von d.oertel
Hi,
it depends on how you are starting the bootimage.
If you are setting the netboot product to setup, the pcname will be passed to the bootimage.
If you are using the opsi-client bootcd or the pxe-menu there is no way for the bootmiage to fetch these information.
see also
http://download.uib.de/opsi_stable/doc/ ... s-hwinvent
regards
d.oertel
Re: Bug in unattend.xml / Win7-64
Verfasst: 07 Apr 2012, 20:38
von topse
I am using the netboot for Win7-64 Prof. Installation.
Re: Bug in unattend.xml / Win7-64
Verfasst: 11 Apr 2012, 19:57
von d.oertel
Hi,
please set the action request setup for your netboot product. Then go at the server to
/tftpboot/linux/pxelinux.cfg
there should be a file named 01-<mac of the client>
give the command
cat 01-<mac of the client>
and post the oputput
regards
d.oertel
Re: Bug in unattend.xml / Win7-64
Verfasst: 16 Apr 2012, 20:55
von topse
OK - I will bring the logfile, but I fear I will not be able to do so before weekend! (Sorry :-/)
Best Regards,
Tobias
Re: Bug in unattend.xml / Win7-64
Verfasst: 24 Apr 2012, 22:41
von topse
This is what I got:
Code: Alles auswählen
default opsi-install
label opsi-install
kernel install
append dn=fritz.box product=win7-x64 pckey=8f45d27a5c00dbb931bf0124c1c8440f service=https://192.168.178.26:4447/rpc vga=791 quiet initrd=miniroot.bz2 splash video=vesa:ywrap,mtrr hn=vbox-opsi-client
Does this mean anything helpful regarding my problem?
Best Regards,
Tobias
Re: Bug in unattend.xml / Win7-64
Verfasst: 25 Apr 2012, 12:58
von d.oertel
Hi,
looks ok.
So the bootimage get the hostname vbox-opsi-client and the domainname fritz.box.
Now you should look at the logfile of the bootimage
/var/log/opsi/bootimage
search there for a entry
pcname=
Is there any and how is the complete line ?
regards
d.oertel
Re: Bug in unattend.xml / Win7-64
Verfasst: 26 Apr 2012, 06:27
von topse
Looks good:
Code: Alles auswählen
opsiserver:/var/log/opsi/bootimage$ cat vbox-opsi-client.fritz.box.log | grep pcname
[7] [Apr 24 22:15:41] >>> pcname=vbox-opsi-client (Posix.py|741)
[7] [Apr 24 22:15:41] >>> pcname=vbox-opsi-client (Posix.py|741)
But still does not work...
Best Regards,
Tobias