@SlimJim said in Multiple TFTP servers on SVN:

What ports need to be open on either side for full communication between the Main Site and Storage node?

http - 80
https - 443
tftp - 69
ftp sometimes 20, 21, 22, or all three.
mysql - 3306
nfs 111, 2048, 2049, potentially 1110 and 4045. You’ll just have to try these first.

138, 139, and 445 are also listed in the wiki but I don’t know what for. Try it without them first.

To use multicast, you will need ports 49152 through 65532.

If you’re going to run DHCP from the fog servers, those UDP and TCP ports will need opened too.

I’m going to attempt this by using all nat’s and firewall rules and eventually I would like to move my main fog server into aws or some similar cloud service.

Good luck. One thing about AWS is they don’t care about your data nearly as much as you do, and their service is not this perfect holy grail as it’s made out to be mostly because of cost. It’s pretty good yeah, but if you google search about moving to AWS you’ll mostly find stuff about how to get out of AWS.

More information needed. What version of FOG are you running? The clients that “suddenly” freeze: Are they in a multicast tasking?

What OS is the Server?

Partclone leads me to think you’re somewhat newer, but I cannot help without this information.

That said, as @Quazz stated, maybe these devices have bad NICs or bad firmware on the NICs that trip for no apparent reason? As @Wayne-Workman suggested, due to the “random” point of the freezes please reseat your RAM on these problem systems just to see if this helps anything.

Factoid about FOG 1.3.0 DHCP, it would have given the surface pro 4 the correct boot file out-of-box.

You can configure your Windows DHCP box to do the same if it’s 2012 or later.

@Thewafflication Good work. You may think about taking your laptop off of the network so you can run DHCP on your virtualized fog server. 🙂

Hi All.

Thank you for the reply. I take a look at our DHCP again and uncheck line 60 (PXEClient) under the server scope and everything seems to be working now. I managed to successfully boot into fog and register the client.

Thank you once again.

@Wayne-Workman said in Using dumb switch to troubleshoot imaging, network related:

@Mastriani So, you put in another NIC, configured it, disabled the others, and the issue is solved?

Currently capturing a 40Gb image, total time less than 17 mins.

Yesterday, updated 2 labs of 30 machines each, in 2:45:00, from start to finish.

The Trunk version is smooth, intuitively easy, and scorching fast. All is well for a small rural district in SE Tennessee!

Well, except that it is SE Tennessee.

While its a bit of a moot point now. There is a tutorial on pxe booting the MDT wim image: https://forums.fogproject.org/topic/6284/booting-mdt-2013-litetouch-with-fog/6

@Tom-Elliott Thank you for the excellent detailed information. From that info I’ve been able to come up with a workable solution. Its not complete, but is workable. if we were to update the hostinfo.php script to pull in the extra info the kernel call could be simpler by 3 variables. But that is a discussion for another time since this grub line will work, it will just take the OP a little leg work to collect all of the info.

Here is the menu entry that works on my server.

menuentry "1b. FOG Quick Image Deploy Win10Ent" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=$myfogip/fog/ storage=$myfogip:/images/ storageip=$myfogip boottype=usb consoleblank=0 rootfstype=ext4 imgPartitionType=all chkdsk=0 capone=1 type=down imgid=19 img=WIN10ENTX64 imgType=n osid=9 echo loading the virtual hard drive initrd $myinits echo booting kernel... }

The fields that will change per image are these imgid=19 img=WIN10ENTX64 imgType=n osid=9
All of this information can be collected from the FOG Web GUI image page. If you go to the FOG web gui and select an image in question.

imgid = look at the browser address URL the id value from url is the imgid value img = the value in the Image Name field imgType = Image Type (calculated from Tom’s table. In the example above imgType of n == resizable) osid = Operating System (the osid value is the number in the parentheses in my case the list box says Windows 10 (9))

That should do it. Just update those 4 fields for each new menu entry matching the image type you want to push.

For reference this grub.conf file is located on the FOS USB boot drive in the following directory ../boot/grub

Both search boxes work the same, but the column search box only searches the results already displayed. If the main search is displaying everything when you type “3132”, this means that number is in all hosts somewhere. It could be a bios version, chassis version, bios date, no idea. Open up the inventory of one of these hosts and use Ctrl+F to search for 3132 and see what it finds.

@x23piracy

Download gpt-fdisk (gdisk) for Windows. Copy the binary to a known location. Boot into Windows Recovery Environment. If you don’t have one, download Windows10ISO from: https://www.microsoft.com/en-in/softw… Create a bootable USB by following https://www.youtube.com/watch?v=Q8gQu… or by burning the ISO to a DVD. Shutdown Windows and boot using this media (Legacy or UEFI Mode). Get to the command prompt. Either by pressing Shift+F10 or by navigating to it. Go to diskpart and find out the disk identifier for your Windows installation.
diskpart
list disk
sel disk X
list par Navigate to the location where gdisk binary is kept and type:
gdisk -l X: (Replace X with the disk number)
This will list out the partitions available in the disk. Make sure this is the one your want to convert. Now, convert the partition table from MBR to GPT.
gdisk X:
Type w to write changes. Press Y whenever prompted. Type the following commands:
diskpart
sel disk X (Replace X with the disk number)
list par Now we make some space for our EFI partition Note the partition number of the partition which you want to shrink

sel par X (Replace X with the partition number)

You may delete the System Reserved partition and replace it with the EFI partition. To do that, type: sel par X (Replace X with the System Reserved Partition) del par override The shrink command is not required if you do the above two commands. I’ll just go ahead and shrink. 500MB extra doesn’t matter to me 😄

shrink desired = 200 minimum = 200

The following commands are common:

create par efi
format fs = fat32 quick # Format this with fat32 file system
assign letter = Z:
exit

@x23piracy said in Restored MBR Image over UEFI PXE doesn't boot:

Sure, that works but i want a working state whatever pxe was initiated from (legacy or uefi). What are the differences or the requirements to boot between legacy or uefi partition layout or bootmanager settings?

There are a lot of differences - and taking an image in one mode and deploying it in another mode will never go well.

If you want your final product to be in UEFI mode, then that image needs built on a computer that’s already in UEFI mode.

If you want your final product to be in Legacy mode, then that image needs built on a computer that’s already in Legacy mode.

@x23piracy said in [SOLVED] UEFI PXE Boot how to do it?:

Is there an overview about the efi files, what they support and so on?

Yes:
https://wiki.fogproject.org/wiki/index.php?title=Filename_Information

@george1421 Yeah, our names have one letter in front of the SN. Easy to get them mixed up.

Maybe it’s best to call it a day on it and just accept that I’ve got a good imaging solution limited by third party software.

Next job I’ll get it perfect. 🙂

@devsamit Alright. We can help you sort this out. First, I congratulate you on trying to setup FOG yourself, and I congratulate you again about seeking help here. That said, I would recommend you install (not upgrade) Ubuntu 16.04 on the laptop, and then install FOG 1.3.0 Release Candidate onto it. There are many reasons for this that I’d be glad to explain, but it’s quite a long list of reasons.

So, install Ubuntu 16.04 (not upgrade). Then install FOG 1.3.0 RC via these instructions: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk You can adjust your existing DHCP server to give DHCP option 066 and 067. 066 is the FOG Server’s IP address. 067 should be undionly.kkpxe There is documentation on this process here: https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG

These steps if done without delay might take an hour.

@utopia Thanks for your ‘essay’ (reply). I tried the other way around not very long ago (a ConeZilla image to FOG) but that did not work out very well and I ended up restoring the CZ image to a device and capturing in with FOG so I don’t think that FOG and CZ are interoparable yet.

I will likely use your method to provision our engineer at the location, thank you.

We need more information. What model of computer you’re trying to use matters a whole lot. The version of fog that you’re using means even more. What steps are you following for the USB Stick, exactly?

We can’t help you unless we know a whole lot more details.

@Wayne-Workman In my test envirement I am running the RC versions on Ubuntu 16.x. When I setup the new servers they will all be fresh installs as well.

Forum clean up: moving topic to Technical Help -> General Problems.