@Sebastian-Roth @george1421
I’ve got the latest version of those tools downloaded and installed. I will attempt to get one of my images mounted in that way and let you both know how I fare.

@Tom-Elliott
As always… thank you for your hard work and dedication. It’s helped me tremendously in many aspects of my D2D work.

@Sebastian-Roth
I’ve got the module build and loaded properly and am starting the restore process to see the it from beginning to end and trying to mount the image using imagemount. Will update once I know more.

EDIT:
@george1421 @Sebastian-Roth
Ran into a slight hitch with the kernel module. Didn’t realize when I rebooted earlier this AM that I had a kernel update. Had to redownload and recompile the nbd module. Still in the testing part of getting the image restored and mounted.

OK!!! I think we have something here. So I finally figured out that part of the problem seems to be in the firewall zone as specified in the Centos 7 Setup guide. The issue I think stems from that the public zone seems to be blocking the multicast ports. I even explicitly told the firewalld daemon to add the interface em2 to the trusted zone, but it never did unless I manually specified in the NIC interface file ZONE=trusted. This seems to be a bug of sorts in that project.

I suppose that you could also specify a port range for the firewalld daemon to allow through. In my case the NIC hosting the FOG Server is segregated my other network. So in this case I don’t care to have all ports open on that interface because there is no reason to block that traffic. Keep in mind the interface em1 is still in the public zone and more locked down and restricted.

The result seems to be that I am now able get it to consistently image across at least two devices and so far it has persisted across device and server reboots. So I think we have made a good leap in that regards. I will keep checking back here for a few days to try and update if I run into issues.

Thank you all for persistently fighting with me to get this rolling. I do much appreciate all you have done for me and with me.
@Sebastian-Roth @Wayne-Workman @Tom-Elliott

@Sebastian-Roth @Wayne-Workman @Junkhacker @george1421 @x23piracy @pr1m0

Sorry to dredge up an old topic, but I went back and tried to redo the steps that I had originally done to restore an image using purely the server. While the steps I listed will work, I did originally mention it, but didn’t specifically include the steps to restore the image on the server. Here is the current working 100% steps to make this all work properly.

Without the touch command below it will error out. So otherwise this works as expected.

cd /images/IMAGENAME/
touch d1p2_extracted.img
cat d1p2.img | pigz -d -c | partclone.restore -C -s - -O d1p2_extracted.img
mount -t ntfs-3g d1p2_extracted.img /mnt

So far that seems to have sorted it. It’s no longer escaping the quotes. I will keep playing around to verify, but so far we’re good. Thanks @Tom-Elliott

@Wayne-Workman

Using one of the links, can’t remember which. I was able to get the server and client to send using the udp-sender and udp-receiver. So I know they can talk, but I had to use the command.

udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log  --ttl 32 --nopointopoint --interface em2

if I dropped the last bit off then it would still try to grab em1 instead of em2.

Would like to have a way to mount images on the servers automatically without needing to run the following commands.

apt-get install ntfs-3g partclone pigz
cd /images/IMAGENAME/
cat d1p2.img | pigz -d -c | partclone.restore -C -s - -O d1p2_extracted.img
mount -t ntfs-3g d1p2_extracted.img /mnt

@EAHarvey
One thing you might could try. I know in the past I’ve used a bootable usb that helped to boot into FOG. I am not sure if it would allow you to automate some of the things you were wanting to do to bypass that or not.

GPXE Bootable USB

Just kinda throwing that out there.

@Wayne-Workman
No, I hadn’t. The command I ran was

firewall-cmd --permanent --zone=trusted --change-interface=em2

that was specified at this RHEL Firewalld page page. This seems to be this link firewalld.zones.

So I can change mine around and try it, but I wouldn’t have managed to do that particular one myself as I’m by no means a iptables guru. I will try to apply that tomorrow to test it out and let you know.

@george1421
Yeah… I understand the whole meeting thing. Sucks to start working on something and constantly get pulled away on other less interesting things.

I’ll look at that article and see what I can do to integrate it into my processes.

Will report back when I have more information to share.

@george1421
Can you provide me a link explaining a bit more about that?
Both the boot usb, and cctk?

@george1421

It’s now uploading an image, but to make this more straightforward without having to make the bios changes every time. I will have to probably rebuild the base image without the Intel Raid mode turned on just to prevent it messing with the OS.

@george1421

lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5918] (rev 05)
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 05)
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:591d] (rev 04)
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 05)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31)
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31)
00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #2 [8086:a111] (rev f1)
00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1)
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1)
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a154] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a171] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (5) I219-LM [8086:15e3] (rev 31)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1bb8] (rev a1)
02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01)
04:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff)
05:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff)
05:01.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff)
05:02.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff)
3d:00.0 Non-Volatile memory controller [0108]: Toshiba America Info Systems Device [1179:0115] (rev 01)
lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
nvme0n1     259:0    0   477G  0 disk
|-nvme0n1p1 259:1    0   500M  0 part
|-nvme0n1p2 259:2    0   128M  0 part
|-nvme0n1p3 259:3    0 475.9G  0 part
`-nvme0n1p4 259:4    0   473M  0 part
df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       103M   88M  9.7M  91% /

I am thinking it has the skylake chipset at least from the line

00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 05)

@george1421

Here is the output of those commands.

lspci -nn
---
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5918] (rev 05)
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 05)
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:591d] (rev 04)
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 05)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31)
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31)
00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31)
00:17.0 RAID bus controller [0104]: Intel Corporation SATA Controller [RAID mode] [8086:2822] (rev 31)
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #2 [8086:a111] (rev f1)
00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1)
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a154] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a171] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (5) I219-LM [8086:15e3] (rev 31)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1bb8] (rev a1)
02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01)
04:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff)
05:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff)
05:01.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff)
05:02.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff)
---

lsblk
---

---

df -h
---
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       103M   88M  9.7M  91% /
---

EDIT:
Found this link that shows it’s at least supported in some way
look at #4

I have a fairly new laptop that I am trying to get registered with my system, but when I attempt to do a Full Host Registration, I get the following error:

I’ve tried changing the sata operation model from Intel Rapid Restore Technology to AHCI and reregistering the machine, but it just fails.

Does anyone have any thoughts on how I can get this machine working with FOG?

@Tom-Elliott
I wasn’t aware that snapins automatically showed under the groups… If that’s the case then it kinda threw me for a loop. Now to recover from my own little screw up… oh well lesson learned… don’t be a dummy

Update:
I’ve created a couple of new groups just to test and it’s automatically adding the snapin that I have on the server to each new group that I create. It’s also adding any new snapins that I create to a group automatically.

EDIT:
I went ahead and restored one of my old database dumps from when I upgraded to FOG 1.4.4. Oh well… looks like I lost a few things as in the hosts that I had registered after the fact. Dang it… Still has the autoadd snapins to groups

@msaglioc99
I would suggest using the following. It works also with Office 2k16.

Microsoft Office Silent Install

@Quazz @kmstory
I do this already… here is my menu entry.

menu DBAN Nuke Menu
item autonuke AutoNuke DoD 3-Pass
item zero AutoNuke 1-Pass Zero Wipe
item choose-disk Single Disk Selection
item return Back to top menu...
item
choose --default return --timeout 10000 target && goto ${target}
:autonuke
kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe --autonuke" silent vga=785
boot || goto failed
:zero
kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe --autonuke --method zero" silent vga=785
boot || goto failed
:choose-disk
kernel http://${fog-ip}/dban/dban.bzi nuke="dwipe" silent vga=785
boot || goto failed
:return
chain ${boot-url}/service/ipxe/boot.php?mac=${net0/mac} || prompt goto MENU

As you can probably tell, from that menu, I have the DBAN iso extracted to this folder /var/www/html/dban/

Try it out… Works wonders for me.