You are on page 1of 4

I was poking around in the Podnutz lounge today, and a couple folks remembered that I was talking about

trying to set up PXE boot yesterday, and when I told them I had met with extreme success they asked me to share my findings. So...here's that post. A little background on me: I don't have any certifications in the IT world, but I am very cocky about my abilities, just like the rest of us. My primary strength is that I am extremely stubborn, and once I set my mind to something, I WILL make it work. I don't have a shop; I operate out of a spare bedroom in my home. My little business largely just provides me with some disposable income to spend on my personal hobbies---tech and the outdoors. My equipment looks like this:  My main rig is just an AMD Phenom Black at something like 3.4Ghz with 10gbs of 10666. It used to have more, but Geil sticks seem to like to burn out in this rig. This is the server rig. I used VirtualBox.  My router (this is important) is an Asus RT-N16. This is important, because its gigabit AND it supports DDWRT Mega or (my preference) the big build of Tomato. If you're not familiar with either DDWRT or Tomato, I suggest you stop reading now and go learn what you've been missing. Mine sets up QoS, port forwarding for all the server apps, DNSMasq for the PXE server, and keeps my dynamicIP service alive for my one-click-vnc and FTP servers. Having a DDWRT or Tomato based router makes this process about 500x simpler because you won't need a DNS server. (I also suggest setting your static DNS on the router to OpenDNS settings, but that's really personal preference.)  My server is an HP N40L that I beefed up to 8gbs of ram. It's got a small ~250Gb internal and a 1.5Tb external attached. I'll add more someday and switch it over to unRaid. It runs Windows Server 2008; and its always-on services are Mumble, TeamSpeak, Newznab+, Sickbeard, Couchpotato, VNC, uTorrent, and a whole bunch of SMB shares. I did not use this server for my PXE server.   Just like everyone on the forum, I've got a random assortment of laptops, mobile devices, etc. floating around. My entire home (it's 90 years old) is wired gigabit, making use of one additional gigabit switch. The only wireless devices are the android bits, the laptops, and the roku. The jailbroken ATV2 is wired, as is the WDTV Live.

Why I wanted to PXE boot:  My office is small, and I've got several spindles sitting around with various copies of whatever. I've got several usb3 dongles for sata and IDE drives, and several flash drives. Keeping them all together is no fun. Most people use PXE to push preconfigured images straight onto machines to save time. This isn't really my intention at this point, I WANT TO USE ISOS.

someone asked about how to push an image to 19 machines. not DDWRT.. it autodetected everything for me except for the address of my DNS server (192.168.technibble. Remember.php?t=34477 Now.. It would probably be sensible now to see if you can connect to it. but there are SO MANY APPS out right now that I can't begin to keep them straight sometimes. Almost all the defaults are right.tar.com/forums/showthread. This is important business.doc The other links are correct as of this posting.O. I suggested the Trinity Rescue Disk. . I installed some of the included tools as per the guide. and then it froze.1. but mostly I was interested in FOG. guide link was wrong yesterday. When you get to CONFIGURING YOUR DHCP SERVER. I have Tomato. Step 1 contains a bad link. Thankfully. I started setting up PXE via my server box as per FoolishIT's blog post. So yesterday. Anyway. because I don't (and don't want to) run my network as a domain with active directories because of all the media sharing going on.History A week or so ago.. I said yes." section link supplies what you need for Tomato as well. So now your PXE server is UP and FOG is installed. they directed the OP to this post by user "smashedbotatos": http://www. Thankfully.com/downloads/installer/pdinstaller. This method obviates the need for WDS or any windows server functionality. That stopped before it started. It Begins. this is a great tutorial. and then someone else recommended PXE-Dust.1 for me.com/downloads/guides/PXE%20Boot%20Server%20Guide. but it's missing some key components. but they're very similar.G. the "3a. I let it sit there for a good 20 minutes. Now follow the guide until you get to the section titled "INSTALLING PXEDUST INSTALLER SCRIPT". Here is the actual guide itself: http://pxe-dust. Specifically. The correct link is: http://pxe-dust. it was fine.gz Follow the rest of that section accordingly. I don't know about you. Project" Installing FOG is pretty straight forward. As far as I can remember. Then I took a risk and rebooted my VM. I didn't. I'd never heard of PXE-Dust. whatever your router/gateway is) When it asked me to notify the Fog group about my install. however you need to make sure you're picking them correctly as you go.. Skip on down to the "F. in some technibble forum post. So--here are those links for you.

So as you're doing something like copying over "precise. then "other information". That password is. is called "pxeadmin". Pressing up or down pops up the menu. by default. Enter this excellent post (I suggest you up it to 720p to see detail): http://fogproject. You know linux uses usergroups and passwords and ownership and permissions.2." Mine look like "/kav/kav. you've played around with it some.iso". So you're gonna upload the isos as "Fog" and edit the menu as "pxeadmin". and stick with a convention like "all lowercase. Now here's the pickle: ONLY the FOG user can add folders to the tftpboot folder. punctuation and capitalization are super important. period.iso." Security isn't especially important on this super closed network. You don't want this.ISO is different than . Whatever. Make your folder names simple too.154/ Now. because it is the best ever in all of ever. (PXE only works on WIRED NETWORKS). some big long hash. As PXE-Dust is a unique distribution. go to configuration.iso" "/regen/hddregen. or at least as far as I know. Or maybe it's "Fog". If you're using a decent FTP program like Filezilla. just watch the video. rename that betch to something like "puppy. this is trivial. and I didn't feel like looking at the onboard users and groups. Anyway. Now to test it. In cASe yOu don't know. This is pretty important. watch the video in the above forum post. Make it all lowercase now and you'll love it later.iso". . the root user. One last hint: In LinUx. I changed in it the terminal while logged in as pxeadmin: passwd fog password I'm actually not sure this step is necessary.5. .org/forum/threads/how-to-modify-the-pxe-boot-menu-to-allow-the-booting-of-isofiles. before we go any further. let's talk about users and passwords. I was flying by the seat of my pants. then "Fog settings". but you can't figure out how to add ISOs. The second user is the "fog" user. And yes.puppy. go to your boot menu. use Notepad++ for all your unformatted text editing. you have to go change it in Fog too. Use Notepad++ to edit the menu. then right or left chooses more options. One." You'll be presented with a screen. plug in a laptop or something to your network. etc. In fact. Ignore the written instructions. So log into the panel.iso".4.Now. They need to match. whether or not you do this. Yeah I coulda merged the groups but I trip over syntax sometimes. and you should have set the password to something stupid like "password. I went ahead and noodled around and edited some other settings inconsequentially and changed anything that said PASSWORD to my simple password "password. if you've logged in to your FOG install. It's important to note that your server now has at least TWO USERS. and replace the FOG_TFTP_FTP_PASSWORD and FOG_NFS_FTP_PASSWORD fields to equal whatever you changed it to above. and choose "network boot. Only the PXEADMIN user can edit the menu. keep the VM running and logged in.) Once that's done." (I win the record for most uses of password in one sentence today. Before I realized it was changeable in the FOG admin panel. and I was afraid to CHOWN and break something.

for right now though. press enter. Hiren 15. it's perfect for me. PartedMagic Currently I'm looking for something to work like Acronis. . Fill 'er up. Precise Puppy Linux threw a ramdisk error. and wait for it to transfer and load. put a unique copy of memdisk in each folder. KAV. Win7. the data was coming from my data storage on my server. Scroll through. I do fully intend to create some vanilla images and actually use PXE as it is intended soon. it can be resized. Oh. I was golden. Here's what I have on there so far: Trinity Rescue Disk. and then back to my desktop into the VM with unique IP.6. I do have Windows 7 and XP isos on my server. but then peek inside that image to scavenge individual files. I say! I also recommend you shut down the VM and increase the number of cores it can use. but once they're transferred. Everything else ran great. picking "advanced" or whatever it says. HDD Rescue. Hiren 13. It'll soar. I was booting into a Dell Mini 10 with just a single core Atom 1. This way I don't have to yank drives from laptops w/o easily accessible bays. By default the VM is 40Gb. Using a VM means that to FTP to the images. decrease its processor affinity. it's for your own reference while editing  MENU MASTER PASSWD password   <‐‐‐ DO NOT CHANGE THIS  kernel fog/dell/memdisk   <‐‐‐‐YES.iso  MENU LABEL Dell Diagnostics    <‐‐‐ This is what shows up in the menu  TEXT HELP  Dell(TM) Diagnostic software   <‐‐‐ This is what shows up beneath the menu when highlighted  ENDTEXT  I realize this is a quick and dirty write-up and probably contains errors. :) The normal PXE-Dust menus are available by scrolling UP or DOWN. and some hints about editing the menu: LABEL Dell Diagnostics   <‐‐‐THIS IS ARBITRARY. but I'll troubleshoot that later. WinXP. This was slowing me down. and dramatically increase the amount of RAM it's allocated. Falcon4Rescue. to my desktop.  append iso initrd=fog/dell/delldiags.All the FOG menu options are available from UP then RIGHT. although all the stuff in the original guide is available right there. and then hitting right. through my router.iso raw       <‐‐‐‐only change /dell/delldiags. that will let me image a drive over the network. I probably won't use much of this. pick one. back to my router. only from boot. You're all set. It loaded even the larger images with no problem.