?
Solved

PXE and NetBoot

Posted on 2009-05-12
3
Medium Priority
?
1,384 Views
Last Modified: 2013-11-11
Okay, background info:
Our school uses PXE-capable computer running Windows XP SP3, and iMacs (some Open Firmware, some EFI) which will (supposedly) NetBoot using Apple's NetBoot server.

We use PXE for deployment at the moment with RIS and Ghost 7.0. Of course, this only works on the PCs.
We are hoping to use NetBoot/NetInstall to deploy images to the Macs.

Of course, PXE requires a DHCP server configured to reference the PXE server. We are not about to change DHCP unless we *really* have to. But then, Mac OS X Server requires it's own DHCP server on the same machine. And running two DHCP servers is not fun.

Our current idea is to add each Mac machine's MAC address to a list, setting the Windows server to reject the computers on the list and the Mac OS X server to allow only those addresses. To prevent conflicts, a range of IP addresses is reserved on the Windows DHCP server (about 50) and the Mac server is given that range to allocate IPs within. I kind of like this solution, but it's not as elegant as it could be.

If anyone has any ideas, that'd be great :) (Is there a DHCP option for NetBoot seperate from PXE?)

Thanks, Michael
0
Comment
Question by:gmichael225
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 32

Accepted Solution

by:
nappy_d earned 375 total points
ID: 24362792
I don't believe there is a need to have two DHCP servers on the same network even though you want to netboot both Macs and Windows computers.

That being said, I manage a network of 150 Windows and 70 Macs using a Windows 2003 DHCP box. I also have an xSerce running OS X that is my netboot/netinstall server.

All my network clients acquire their IP from the 2003 server for pxe /netboot when necessary.

You should not have an issue all.

Mac OS DOES NOT require a separate DHCP server.
0
 
LVL 1

Author Comment

by:gmichael225
ID: 24362983
Okay, well I've only tried this os on OS X Server 10.3, but that required DHCP to netboot. However, this was probably Apple's older protocol for network booting (I believe they moved from NetBoot to BOOTP? Or the other way around... not sure.). We have Macs of both old and newer firmware, so I don't know what problems that will raise.

Thanks though, I'll try "do it anyway".
0
 
LVL 32

Expert Comment

by:nappy_d
ID: 24363048
I run OS X 10.4.11 server. I've also run Leopard server successfully.

Hit me back with questions....
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will inform Clients about common and important expectations from the freelancers (Experts) who are looking at your Gig.
This article outlines the struggles that Macs encounter in Windows-dominated workplace environments – and what Mac users can do to improve their network connectivity and remain productive.
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

801 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question