Hi everybody, and thanks Foreman people for a wonderful piece of kit. I've been using it successfully for a little while, and am now trying to sort out provisioning here at work to save us some time.
We are predominantly a Windows environment however, and in particular our DHCP servers are windows boxes that I have no control over. PXE is in use exclusively for our Windows imaging. Given that, I though that the foreman_bootdisk plugin would be the answer, and I'm really close to getting it all working, but any machine I try to provision has network issues and fails the build. I boot via the generic boot disk and the machine starts, gets an IP address and contacts The Foreman for build instructions (preseed, kickstart etc). After that it seems that the machine loses its IP address and subsequently fails to go any further. I think the piece I'm missing is how to make The Foreman bootdisk scenario work with an external DHCP server. I had thought I could just boot via the bootdisk and let the existing DHCP take care of the network piece, and this is exactly how I build RHEL boxes here from Satellite 5.x, but I think I've missed some config or I'm not understanding how Foreman works with external non-controlled DHCP. Apologies for the long post. Can anyone offer any guidance on how to make Foreman bootdisk and external DHCP work? More than happy to provide any details or logs that could be of use. Many thanks, Craig. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
