HP Compaq 6200 Pro
Intel 82579LM Gigabyte Network Connection
undionly.kpxe
FOG 1.2.0
03-16-2016
Single Disk - Resizable

Note on 6200 - I’ve occasionally run into issues with SD - R where after imaging, Explorer reports the shrunken size of the partition but Disk Management show the partitions being the right size (first part being 100 to 350mb and the second part the rest of the disk) To remedy this go to DISKPART, select the miss-sized partition and run EXTEND FILESYSTEM.

HP DC7700
Broadcom NetXtreme Gigabit Ethernet
undionly.kpxe
FOG 1.2.0
03-18-2016
Single Disk - Resizable

Note on 6200 and DC7700 - Also as is noted here, HP adds partitions that make using Single Disk - Resizable fail out. The partition is also created when making update to the BIOS. Unlike what the article listed says however, you can delete the partition using DISKPART.

Cloned the Storage Node using VirtualBox’s cloning feature. Changed the TCP/IP info and plugged in the same password into the main FOG and it worked. Storage Node was added and I could see it in the Dashboard (well I get the failed to connect error, but I can click on the link and get the info on the Node.) There was a power outage that corrupted the VHD for the clone, so I’ll try cloning it again and see if it serves image download requests

I have a Storage Node VM that works correctly, takes replications and spits out images as needed.
My questions: If I use the cloning feature of the hypervisor and make sure that things like hostname and TCP/IP stuff is changed, can I add the newly cloned Storage Node to the main FOG server using the same credentials as the “parent” Storage Node or is there some unique ID that must be respected.

The SN is on Ubuntu 14.04 LTS and the main server is on Ubuntu 15.10

@Wayne-Workman I have a 2008r2 Domain controler that acts as the DHCP server as well and I have options 66 and 67 set as it shows on guide. My FOG is on Ubuntu 15.04. When my workstations go into network boot, they send out discovery packets but don’t get any packets in response. Looking into it, I found that DHCP option 60 needs to be enabled. I was going to test it on my server here before editing the wiki and to be honest, I didn’t expect such a quick response. I’ll make a post in the correct area of the forum if I need anything farther.

@iyoung said:

@Wayne-Workman This article only mentions option 66 and 67, but on Windows Server you also need to enable option 60 through netsh to turn on the PXEClient.

And the User Guide as well.

@Wayne-Workman This article only mentions option 66 and 67, but on Windows Server you also need to enable option 60 through netsh to turn on the PXEClient.

HI,

I am requesting access to the Wiki to change the steps on how to step up Windows DHCP to work with FOG. I am also testing FOG on the latest versions of Debian, Ubuntu and Fedora to see which I like best and I will report here on my finds, when I have free time(hehe) to do so.