@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?
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.
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)
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.
@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.
Made some changes to my snapin deployment process and was trying to delete old snapins out from the GUI, but it didn’t. I get the message where it says that the Group Information Updated at the top, but in the webGUI it’s still showing. The only way I was able to get it out initially was to go in and blow away all my snapins. I did it by doing…
truncate snapinGroupAssoc;
truncate snapinAssoc;
truncate snapinJobs;
truncate snapinTasks;
truncate snapins;
I know this is WAAAAAAAAAAY overkill, but it was the only way that I could wipe it away. Does anyone have any ideas?
@Tom-Elliott
That’s the thing though… They could talk through the server because I could mount a shared drive and do all other things using that same previous setup. Imaging worked fine. It’s freaking weird
@Tom-Elliott
I just tried something that seems to work for now. I have swapped out the switch they are all plugged into in reference to the lines from the log that say
7/6/2017 10:05 AM Middleware::Communication ERROR: Could not contact FOG server
7/6/2017 10:05 AM Middleware::Communication ERROR: Unable to connect to the remote server
The clients have so far checked in OK. I’ll go back and revisit the other machines that were having issues and reply back to let you know what’s going on. Hopefully it’s not truly a switch issue so that I don’t look like a friggin idiot.
@Tom-Elliott
Follow up. I’m using the same image on multiple like model laptops, most work without issue. The ones that never seem to process the snapin tasks are few and far between. In the most recent multicast session, I did 4 identical ones. 3 pushed the snapin tasks without issue.
@Tom-Elliott
Gimme a sec to grab the logs from the client. Which logs are you needing from the server?
EDIT:
Here is a link to the logs from the problem client
fog.log
Some clients aren’t checking in on snapin tasks. They stay in queued status. I’ve rebooted the system and client. They never seem to process those tasks. Thoughts on how to rectify this?
So it’s a longshot, but I’m trying to track down how to enable an addon in IE 11 automatically so that I don’t get the prompt at the bottom of the window asking if I want to enable an addon. Can anyone tell me how I might could do that? I am thinking I have to do some reg tweaking, but I am not sure how that will all pan out. Thanks,
@george1421 said in UEFI Screen Size:
vga=792
That seems to work as expected. I will do some more extensive testing of it this afternoon if possible and report back.
Just got a machine to boot to UEFI and start an imaging task, but the size of everything is EXTREMELY TINY. Does anyone know how to make it larger? Granted it’s a 4K capable monitor, but still… freaking hard to read. Thanks in advance.
@Quazz
The device is a Lenovo X1 Yoga Gen 2.
There are no other devices on the subnet. I have the server physically and logically separated from all other networks/devices in my scheme. I will disable secure boot and report back.
EDIT: Secure boot disabled is letting me boot to the FOG menu now. I just need to change the MENU EXIT TYPE I think. When I chose the Boot From Hard Disk option, I got a “Chainloading” failure. I think once I get that straightened out, it will work.
EDIT 2: I changed the option FOG_EFI_BOOT_EXIT_TYPE to REFIND_EFI and it was able to boot successfully from the FOG Menu.