@clickwir said in Don't want host registration.:

We aren’t looking for a way to manage multiple images of each OS on each server. All we want is to PXE boot a server, get a list of OS’s and start the install. The changes to a server between each OS install are significant enough that an image won’t work, most of the time.

Why would you use FOG for that? Just setup a DHCP and TFTP service on a server and you’re done… Maybe add apache/nginx and NFS to also server files through HTTP and NFS. All fairly easy to setup by hand and no need to have all the PHP/MySQL/FTP foo that would come with a full FOG install.

@jodantiger Well you better tell me how this partition layout was created. How would I know…

Maybe try mounting it while you are in debug mode

mkdir /mnt/sda1
mount -t vfat /dev/sda1 /mnt/sda1
ls -al /mnt/sda1
umount /mnt/sda1

If vfat does not work then try ntfs instead. Take a picture and post here.

@JJ-Fullmer As of now - that is current RC version - you should be able to use a single USB NIC with any number of clients as we already prefer UUID as a key to recognize clients. You can see this when you change one client’s MAC either on the machine (when it’s simple as in a VM) or in the web UI. The client should still be recognized when booted to the FOG menu. Give it a go.

That said we still have not testen this feature for all occations and I am not sure if we have it all right to meet your situation. So please try and let us know.

@Maorui2k I am not saying it’s impossible to figure out but doing this in the forums one post every couple of days forth and back won’t get us anywhere. If you are really keen to get this solved then send over a machine so I can test and I’ll see what I can do. Just not sure if it’s worth sending it around the world as I am located in Germany.

You could still stick to test different linux distros like all kinds of live linux CDs (system rescue CD, …) as well as installed distros and see which ones work and which have the issue. Maybe you can figure out what they all have in common.

@jodantiger Please schedule a debug task and when you get to the shell run fdisk -l /dev/sda; blkid. Take a picture of the output and post here.

@martyc81 Do you use sysprep by intent? Do you know how it works?

@techadmin said in PXE connection Using Windows 2008 as DHCP Server:

If I clone one box using this dongle and I go and use the same dongle to push images to other devices is this going to be a problem?

We’ve been working on identifying machines by SysUUID (see here) instead of the MAC address. Though this feature is still new and I am not exactly sure if it’ll work in all cases. Give it a go and see how it works.

Next I moved the Clonzilla image over to the FOG server now what do I need to do to compress it so that FOG can reuse t?

What George meant is that you better deploy the Clonezilla image(s) to a machine (using Clonezilla) and capture a new FOG image from that. It saves you a lot of work (converting and generating FOG metadata like partition tables and more) and you’ll have a nicely compressed image right away.

This looks really strange. There is the major part of the URL missing in the output. Should be “http://x.x.x.x/fog/index.php”. When creating the boot USB key make sure you have the web=http://$myfogip/fog/ parameter set!!

All that said I’d also recommend what George already said. Find that onboard NIC chip and use this. USB NIC PXE boot might work but is quite often a lot of hassle to get to work. See that has_usb_nic=1 kernel parameter is also just an ugly workaround but we still need this…

Either image type has been set to raw (by hand?) in the web UI. Please check the image settings there. If not then I think the upload scripts fail to recognize the filesystem on disk. Can you please schedule a debug (like scheduling a normal job but just before clicking the button there is a checkbox for debug) upload job next and when you get to the shell run the following command, take a picture and post here: blkid

@imagingmaster21 From the first picture you posted in the initial request it looks like you are using image type “Single disk - Multiple partitions” which is non-resizable. Sou you cannot deploy this image to a smaller disk! If you change the image type from non-resizable to resizable you have to re-upload/capture the image before deploying it!

Maybe the source disk is damaged???