@Wayne-Workman Agreed, but what’s not clear is that the default password in this field is not actually my password, encrypted. The management password needs to be in this field in clear text. The same applies to other config sections on the management web interface. I should have just tried it earlier.

That was it. Same headache as this OP: Point #3. Registering and uploading!

I think my issue is in Storage Node / DefaultMember / Management Password. I updated that to match all other configs and now I get actual log choices. Trying to upload now.

@Wayne-Workman There’s nothing to expand. Below the pause button it says ‘invalid folder’ and nothing else.

@Wayne-Workman Interesting. Navigating to fog Configuration / Log Viewer straight away says there’s an error with the Fog “ftp_login(): Login incorrect.”

In my Fog Configuration / TFTP Server, the username and password are correct, as are the fog config files on the server.

@Wayne-Workman Logging in to ftp://<IP> works fine, I can read and write. Do I need to test at the specific image directory?

I’m getting the Trunk-specific database error when uploading an image (same as referenced in the WIKI here. I’ve checked all four locations for the correct username/password combination and it’s correct. I’ve checked the filesystem of the new FOG server that Sebastian walked me through, and it’s the correct EXT4. Username ‘Root’ has seems to have the proper system access to the image directory that it needs based on the result of the ls -laR /images command.

@Sebastian-Roth I would like to thank Sebastian for his time in helping me diagnose this issue. We spent a substantial amount of time working through the issue and I learned a lot through the process! We are working through uploading images for these two machines as I type and all appears to be going well now that I’m on the Trunk version.

@george1421 I’m on it now, booted to 14.04.4 live USB

@george1421 OK - I have to deploy these laptops this week but I will try to hold one back for now.

@Scott-Adams It is UEFI capable, but I’ve disabled it and using classic bios. It actually comes from the factory that way too since it was pre-loaded with a Win7Pro lic.

@george1421 Sorry - I was in audit mode and booted it up long enough to grab the requested information.

Following the thread it looks like I’m out of luck for the Latitudes? Can you explain what it means that the NIC is an orphan? Does it literally mean it’s not part of a NIC family with common drivers?

@Sebastian-Roth I started to type them out and realized it would be more efficient to post the images.

@Wayne-Workman
I’m not sure how to answer #1?
#2 - no
#3 - BIOS (classic)
#4 - BIOS (classic)

Previous Thread

On my previous thread I laid out the details:
Running FOG 1.2 on Ubuntu 12.04LTS. This server has worked flawlessly for several hundred machines until this new batch of Dells. The BIOS is so current it’s not even listed on the Dell website. We also tried rolling back to an older version of BIOS, no difference. I’ve run updates on the FOG server to ensure that all the requisite software is current (MAP). The only update I haven’t performed is on Ubuntu itself and I don’t intend to do that.

I’ve attempted compiling my own Linux kernel with the current 4.4.1 and adding in my own modules. I was successful except for the last part and am out of time to try to learn compiling in order to solve my own problem.

So I’m back. I have Dell XPS8900s and Dell Latitude laptops (NIC Realtek PCIe GBE Family Controller RTL8167). In the last thread, mods assumed that it was the NIC given the errors I was receiving when trying to PXE these machines.

I’ve also tried a known working USB NIC that is compatible with Linux to bypass the onboard NIC when registering with FOG.

Any new suggestions?

@Wayne-Workman So should I start down the path of creating my own kernel to include drivers for these machines should I find that no pre-built kernel exists? Or am I missing something easier here?

@Wayne-Workman I figured as much, but how do I tell if that’s the ‘current’ kernel without being able to log into the FOG portal listed in an earlier response from Tom? And if it is the current or a more current kernel than the one I listed at the start of this thread, it isn’t resolving the original issue either.

@Wayne-Workman The result of that command is “4.3.2”

@Wayne-Workman Ah - I see where you are referencing now. I will dig out a machine that I know will register, get it registered, then run the debug. Thanks!

@Wayne-Workman By host I assume you mean a destination machine, in my case one of these troublesome XPS desktops. I don’t see an option for that in the FOG PXE menu, so I googled and found the old wiki referencing the instructions for FOG .3. This indicates a Linux host and is for XP. Where can I find updated instructions for ‘debug mode’?