DNS/DHCP setup for deploying new computers?

uncle_scrooge
Beiträge: 571
Registriert: 21 Feb 2012, 12:03
Wohnort: Mainz

Re: DNS/DHCP setup for deploying new computers?

Beitragvon uncle_scrooge » 08 Nov 2017, 18:24

Change
backend_.* :file, opsipxeconfd, dhcpd, mysql
host_.* :file, opsipxeconfd, dhcpd
to
backend_.* :file, opsipxeconfd, mysql
host_.* :file, opsipxeconfd

Restart opsiconfd and opsipxeconfd.
Try again.

Benutzeravatar
n.wenselowski
uib-Team
Beiträge: 3120
Registriert: 04 Apr 2013, 12:15

Re: DNS/DHCP setup for deploying new computers?

Beitragvon n.wenselowski » 09 Nov 2017, 11:26

uncle_scrooge hat geschrieben:Booting from CD/ISO-image always leaves the information for 'config server' empty. Neither the CD nor a DHCP server knows anything about it.
So the input mask is always displayed.

Booting the bootcd image from within the PXE menu is a different beast.
As you can see in the append line
append initrd=miniroot-x64.bz2 video=vesa:ywrap,mtrr vga=791 quiet splash --no-log console=tty1 console=ttyS0 service=https://192.100.100.223:4447/rpc
the config server is given as a parameter. If a DHCP server provides all further needed information, the initial input mask is not displayed.
Omitting 'service=https://192.100.100.223:4447/rpc' gets you to the same behaviour as booting from CD/ISO.

There should be another input mask where I would be able to change the default client name 'opsi-client'.

I think we should take this into another thread. Could you please post this in the suggestions?
opsi development - uib gmbh
For productive opsi installations we recommend support contracts.

ttblum
Beiträge: 91
Registriert: 23 Jun 2017, 14:18
Wohnort: Cleveland, Ohio USA

Re: DNS/DHCP setup for deploying new computers?

Beitragvon ttblum » 16 Nov 2017, 17:19

Ok, this worked:

Code: Alles auswählen

Change
backend_.* :file, opsipxeconfd, dhcpd, mysql
host_.* :file, opsipxeconfd, dhcpd
to
backend_.* :file, opsipxeconfd, mysql
host_.* :file, opsipxeconfd

Restart opsiconfd and opsipxeconfd.
Try again.


Thank you