Clonezilla / Discussion / Clonezilla server edition: Clonezilla <> DHCP server on windows 2003

Karly De Baere - 2009-05-26

we have a network with 1 DHCP server on a windows 2003 server.

When clients boot they need their DHCP settings ONLY from this windows 2003 server!

What do we need to disable /uninstall on the clonezilla server.
What doe we need to change on the windows 2003 server?

Now we have added DHCP option 66 & 67 in the windows server referring to the clonezilla, but after PXE menu nothing works .. we did allready the mknic-nbi --check-server-name n un the clonezilla server.

Also on the clonezilla we uncommented the allow members of "DRBL-Client" in the dhcpd.conf file.

But clients still receive DHCP offerings from the Clonezilla server what do we need to adjust to make sure that clonezille only does some dhcp stuff when a PXE clients needs it during imaging activities ?

Thx

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Steven Shiau - 2009-05-27
  
  Did you merge the config files to your Windows DHCP service and turn off the dhcp service on your Clonezilla SE ?
  
  Steven.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Karly De Baere - 2009-05-27
  
  OK Now I get the picture.
  
  "Merging" in this context mean:
  
  - open the dhcpd.conf file
  - note all macadres reservations with their corresponding IP-adres
  - remove the DHCP server (apt-get remove dhcp3-server)
  - open the dhcp-server on a real OS (windows server 2003 :-) )
  - add EXACT the same reservation (mac - ip address) for al hosts
  - add DHCP-Option 66 (fill in ip-address of Clonezilla server)
  - add DHCP-Option 67 (fill in: pxelinux.0)
  
  Now The PXE client will take IP-address from Windows Server 2003 DHCp server together with PXE options ..
  
  Thx for the hint with the word "merging" :-)
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- kurtvwa - 2009-05-29
  
  I tried this solution but it doesn't work 100% in my environment.
  
  I notice that with this procedure my PXE client does receive an IP adress , but later in the PXE boot it hangs with the error that it does not receive an IP adress from the DRBL server.
  
  So it seems to me .. that with implementing this solution , my PXE client does receive an IP adress from the windows Server, BUT later in the pxe boot it still truys to receive an IP adress from the DRBL server, wich fails because the implementation is that way that the DHCP server is removed from the DRBL server.
  
  Can you tell me why my clients still try to receive an IP from the DRBL server and can not connect with the DRBL server with the IP adress that it received from the Win server?
  In a try to solve it I did a drblpush without fix Ip'sfor the clients but it does not make any difference.
  Below my drbl debug file (without fix ip's .. but like I told , this doesn't make a difference for this problem)
  
  To report the bug, fill the contents in the following table, then send it to DRBL mailing list or post it on the DRBL forum."
  -------CUT BEGIN HERE--------------------------------------------
  Description of problem:
  
  How reproducible:
  
  Steps to Reproduce:
  
  Actual results:
  
  Expected results:
  
  Some info about the DRBL environment (PLEASE DO NOT EDIT THEM!):
  
  OS version: Ubuntu 9.04
  Server arch: i686
  Server CPU: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
  Server memory size: 509504 kB
  Server Kernel version: 2.6.28-11-generic
  Installed DRBL-related packages: drbl-1.9.4-27 clonezilla-2.3.3-24 mkswap-uuid-0.1.1-1 drbl-partimage-0.6.7-1drbl drbl-ntfsprogs-2.0.0-4 partclone-0.1.0-10 drbl-chntpw-0.0.20040818-7 drbl-lzop-1.02-0.8drbl pigz-2.1.4-1drbl pbzip2-1.0.5-1drbl mkpxeinitrd-net-1.2-40 udpcast-20081213-1drbl drbl-etherboot-5.4.3-2 gpxe-0.9.7-1drbl freedos-1.0-11drbl
  Client kernel version: 2.6.28-11-generic
  Client kernel arch: i586
  NICs with private IP address in server: eth0 eth1 eth2
  Private IP address in server: 192.168.1.1 192.168.2.1 192.168.10.11
  Total client no: 100
  Client IP address: 192.168.1.10 192.168.1.11 192.168.1.12 192.168.1.13 192.168.1.14 192.168.1.15 192.168.1.16 192.168.1.17 192.168.1.18 192.168.1.19 192.168.1.20 192.168.1.21 192.168.1.22 192.168.1.23 192.168.1.24 192.168.1.25 192.168.1.26 192.168.1.27 192.168.1.28 192.168.1.29 192.168.1.30 192.168.1.31 192.168.1.32 192.168.1.33 192.168.1.34 192.168.1.35 192.168.1.36 192.168.1.37 192.168.1.38 192.168.1.39 192.168.1.40 192.168.1.41 192.168.1.42 192.168.1.43 192.168.1.44 192.168.1.45 192.168.1.46 192.168.1.47 192.168.1.48 192.168.1.49 192.168.1.50 192.168.1.51 192.168.1.52 192.168.1.53 192.168.1.54 192.168.1.55 192.168.1.56 192.168.1.57 192.168.1.58 192.168.1.59 192.168.2.10 192.168.2.11 192.168.2.12 192.168.2.13 192.168.2.14 192.168.2.15 192.168.2.16 192.168.2.17 192.168.2.18 192.168.2.19 192.168.2.20 192.168.2.21 192.168.2.22 192.168.2.23 192.168.2.24 192.168.2.25 192.168.2.26 192.168.2.27 192.168.2.28 192.168.2.29 192.168.2.30 192.168.2.31 192.168.2.32 192.168.2.33 192.168.2.34 192.168.2.35 192.168.2.36 192.168.2.37 192.168.2.38 192.168.2.39 192.168.2.40 192.168.2.41 192.168.2.42 192.168.2.43 192.168.2.44 192.168.2.45 192.168.2.46 192.168.2.47 192.168.2.48 192.168.2.49 192.168.2.50 192.168.2.51 192.168.2.52 192.168.2.53 192.168.2.54 192.168.2.55 192.168.2.56 192.168.2.57 192.168.2.58 192.168.2.59
  ===
  -------CUT END
  
  Thanks,
  
  Kurtvwa
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Steven Shiau - 2009-05-30
    
    Kaoft,
    Thanks for sharing that.
    
    Krtvwa,
    Did you run
    /opt/drbl/sbin/mknic-nbi -c n
    to disable client requesting IP address from DRBL server ?
    
    Steven.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Karly De Baere - 2009-05-30
  
  Kurt,
  
  like Steven suggested I also did that command after the removal command of the dhcp-server.
  
  So the procedure for using a Windows DHCP Server as only DHCp server together with Clonezilla is:
  Linux-machine with Clonezilla:
  - open the dhcpd.conf file
  - note all macadres reservations with their corresponding IP-adres
  - remove the DHCP server (apt-get remove dhcp3-server)
  - disable client requesting IP address from DRBL server: /opt/drbl/sbin/mknic-nbi -c n
  
  Windows Server:
  - open the dhcp-server on a real OS (windows server 2003 :-) )
  - add EXACT the same reservation (mac - ip address) for al hosts
  - add DHCP-Option 66 (fill in ip-address of Clonezilla server)
  - add DHCP-Option 67 (fill in: pxelinux.0)
  
  Now the PXE client will take IP-address from Windows Server 2003 DHCp server together with PXE options ..
  
  Procedure when new client-pc's join the network:
  - add them to the correct macadr-ethX.txt file (replace X with the correct interface-nr.)
  - run /opt/drbl/sbin/drbl-3n-conf generate
  - add EXACT the same reservations (mac - ip address) in the Windows DHCP Server
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Steven Shiau - 2009-05-31
    
    Karly,
    Thanks for sharing that. I have updated the FAQ/Q&A to link this:
    http://drbl.sourceforge.net/faq/fine-print.php?path=./2_System/37_coexist_with_existing_dhcp.faq#37_coexist_with_existing_dhcp.faq
    
    Thanks again.
    
    Steven.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

ryan currah - 2012-01-11

Hey All,

I'm trying to do the exact same setup ask describe here with a Windows 2003 DHCP server. But I do not want to use a pre-described list of PC's and mac addresses. So I skip the step ' add EXACT the same reservation (mac - ip address) for al hosts'. Or should I add to my Windows 2003 DHCP server the private IP range that I specified for eth0:0?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2012-01-17

I am not familiar with the DHCP service on MS Windows.
Anyone on this forum could share his/her experience?

Steven.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

tarzan - 2012-01-22

Hi
I dont know if this gonna help in someway but this is what i have done in my environment. i am running both clonezilla and another dhcp in our network. i gave clonezilla only 40 IPs (10-50) and enabled the allow only DRBL client section on clonezilla dhcp config file. on the other dhcp we gave the rest of IPs (51-254) and we copied the Allow DRBL client from clonezilla and changed ALLOW to DENY. we dont usually clone or install more than 32 computers at a time so this solution is working for us. by the way the other dhcp server is linux also but may be this solution can be implemented on windows too.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2012-01-24

Got it. Thanks for sharing that.

Steven.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

kernel - 2015-10-12

any chance that this can be elaborated a bit and updated to fit DHCP in newer versions of windows server?
especially i would be very interested in skipping the MAC registration all together
thanks in advance for your help!

Last edit: kernel 2015-10-12

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickwir - 2017-10-03

Agree, this seems to be old info and needs some newer info for people that are trying to drop a Clonezilla server into an existing envrionment.

We will soon have a corproate DHCP server that we will not have access to. I need this to work without anything other than supplying a PXE boot server IP and file name. How?

Also, we have no need for MAC registration or having the Clonezilla server "remember" clients in any way other than we make an image of an OS and need to deploy it to where we want.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2017-10-11

Just some info here. Clonezilla live now has a "lite server" mode which can let you relay the DHCP request to existing DHCP service:
http://clonezilla.org/show-live-doc-content.php?topic=clonezilla-live/doc/11_lite_server
Not sure if it works with the DHCP service from MS Windows or not, but still you can give it a try.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

IMMANUEL - 2017-12-05

Steven, could you pls help me to use my exising Windows 2012R2 DHCP in a easiest way. I have been trying to configure it for a long time but it was unsuccessful.

DRBL latest version instlled on Ubuntu 16.04
DHCP Server and WDS + Pxelinux running on Windows 2012R2

Last edit: IMMANUEL 2017-12-05

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2018-01-03

@IMMANUEL,
Is that possible you can use Clonezila lite server? As mentioned in my previous post? If so, any problem?

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

IMMANUEL - 2018-06-28

I want to do with dedicated Clonezilla Server Edition,

I am trying to achieve solution3 from this link https://drbl.org/faq/fine-print.php?path=./2_System/37_coexist_with_existing_dhcp.faq. but unfortunately, for pxe boot it is taking IP from Clonezilla DHCP server after that it is taking IP from Windows DHCP server and failed to start clonezilla.
Can any one pls help me who is using Clonezilla server edition using windows 2012 DHCP Server.

Thanks in advance.

Last edit: IMMANUEL 2018-06-28

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2018-08-09

In that case, you have to install dnsmasq then configure it to relay the requests to the existing PXE services. Check dnsmasq doc for more details.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mani Bharathi - 2019-02-09

Hi,

I have existing windows dhcp server so, i need to configure clonezilla with this. but, i have done all the things but it not works. (Option 66,67 added, dhcp server removed from clonezilla) pls help me to done.

Thanks!

😄
1

Last edit: Mani Bharathi 2019-02-09

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2019-02-10

This is a very old thread. Please new a thread, and describe your question and steps in detail.
As I mentioned, the Clonezilla lite server can use dnsmasq to relay the service, maybe you can check that:
https://clonezilla.org/show-live-doc-content.php?topic=clonezilla-live/doc/11_lite_server

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mani Bharathi - 2019-04-04

Thanks for your reply. i like only clonezilla SE.

I have configured clonezilla SE in ubuntu 18.04 with single network interface card. (FYI, we have many inter vlan configuration.) Here i am using dynamic ip for clonezilla.(192.168.8.90 - 8th VLAN) and i have a existing windows DHCP server with arround 18 scopes and it all configured with vlans (like 192.168.0.0, 192.168.1.0, 192.168.8.0 ....) i have merged clonezilla dhcp with my existing windows DHCP server (https://drbl.org/faq/fine-print.php?path=./2_System/37_coexist_with_existing_dhcp.faq). Now the pxe client boot up with windows dhcp IP but, next step pxe client does not get clonezilla IP. if the client network configured with 8th vlan it's working fine. How can i configure the clonezilla for multiple range. Please help me on this.

''' enp6s7 Link encap:Ethernet
inet addr:192.168.8.90 Bcast:192.168.8.255 Mask:255.255.255.0
inet6 addr: fe80::214:22ff:fe22:9621/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:14180265 errors:0 dropped:147 overruns:0 frame:0
TX packets:13224427 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5580088907 (5.5 GB) TX bytes:24655047267 (24.6 GB) '''

Last edit: Mani Bharathi 2019-04-05

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2019-05-05

"Now the pxe client boot up with windows dhcp IP but, next step pxe client does not get clonezilla IP. if the client network configured with 8th vlan it's working fine. " -> I do not have any experience about WIndows DHCP service. Therefore I do not know how to help you.
If anyone on the forum has similar experience, please share that. Thanks.

Steven

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Clonezilla <> DHCP server on windows 2003

A partition and disk imaging/cloning program

Forums

Help

Clonezilla <> DHCP server on windows 2003

Some info about the DRBL environment (PLEASE DO NOT EDIT THEM!):

Clonezilla <> DHCP server on windows 2003

A partition and disk imaging/cloning program

Forums

Help

Clonezilla <> DHCP server on windows 2003 document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

Some info about the DRBL environment (PLEASE DO NOT EDIT THEM!):

Clonezilla <> DHCP server on windows 2003