@george1421 I think I may have figured it out now.
I had to go into the BIOS and switch the Dell to Legacy boot options. I assumed it was ok because I was getting the menu to come up that shows all my fog options, normally I would never see the fog menu if it was not going to just work. For anyone whom may be looking for answers for this same issue, it was under Settings > General > Boot Sequence > Legacy in the Boot List Options box.
Thank you very much for the help George!
@george1421 I had placed the files in the wrong place before so thank you. However, the issue still persists even with the updated Kernal. Any ideas what may be going on?
@george1421 Where do I put the files? Maybe I placed them in the wrong area
Hello Guys,
I am having problems getting a Dell Precision 5510 into inventory. It uses a Thunderbolt Ethernet connector which is one oddity with this Laptop. It says there is an error has been detected! cannot find disk on system (getHardDisk.) Args Passed:
I tried updating the bzImage but it does not seem to have changed my Kernel Version in fog itself. I am running Version 1.3.0-RC-1 and bzImage 4.6.4
Thanks in advance.
Just so others know/ so you know. There are two different Domain password spots. One for if you have the new client installed and one for legacy clients. It had my password in the new one’s spot where the client on my machines is the old client. Used FOGCrypt to generate the Legacy password again and it worked like a champ.
@george1421 Got a quick one for you. What do I have to put in AD settings to make it work? The machine I added is not joining the domain automatically like it use to. Again I am sure it is a minor change like when we upgraded to 1.2.0 but I have not been successful at finding an answer.
@george1421 said in New Machine Problems:
@Andrew134 @Developers a little input on adjusting the image here?
Actually it seems like I got it working. Not exactly sure how but now my Elitedesk is up with the image. Lenovo not so much but I am beginning to believe the machine is the problem not fog Thank you everyone so much for your help! Cannot express how happy I am that this community is so helpful/ responsive to questions. If I come back around to thinking the image is the issue I will open a new topic but at this point I think it is the machine.
@george1421 said in New Machine Problems:
What version of FOG were these captured under? My bet there is something we need to adjust like partclone or the config files. That part is a bit beyond what I know, but once we get things outlined we can get the devs involved. Don’t worry this issue can be fixed.
They were captured in 1.2.0 and I have faith it can be.
Just to be clear the image is not working on both the machines I mentioned before (Lenovo and Elitedesk) both now can register and get images though.
Well I got her updated and it works… for the most part. Now my images do not work once they have been deployed. This was the image I was trying to use is there anything that jumps out at you just from this page?
Alright so I have to throw in the towel. Still can’t get the Lenovo to re-image no matter what settings I change and we just got our new machines in and they won’t work either. They are HP Elitedesk 800 G2 and searched for the model in Fogproject forms and all I have found is trunk being the end all answer.
My question now is can I do an in place upgrade to Trunk or do I need to build a new server? Does the data port over okay from 1.2.0 to Trunk?
@george1421 said in New Machine Problems:
I just checked the Lenovo Thinkpad T460s and it has an intel nic which should be supported by the FOS engine (linux kernel supplied by bzImage).
Are these systems in legacy (bios) mode or uefi?
I switched off uefi on the HP and it is now reimaging like a champ 
However the Lenovo is still giving me issues, I turned it to Legacy and it still says network failed. If I change it to uefi it says starting PXE over IPv4, looks like it finds the fog server but then pops up PXE over IPv6 and hangs for a while before returning to the boot menu.
@Wayne-Workman Sadly it is still doing the blinking. This is what I got from doing an ls -l
@george1421 put these files in place and now reimaging in fog is not working. I had this issue with the Kernel I made as well. All I get when doing reimaging on a different machine is a strobing underscore. Did run compatibly check on both of the laptops and got the network failed again.
Hello all,
I have two laptops my school district purchased that both would not register with fog. They will boot into the fog menu but when I tell it to register them it brings up that it can not add them to inventory. So I launched the menu again and ran the Fog Compatibility Test. It comes back with Network…[Failed]
The Computer models are:
Lenovo Thinkpad T460s
HP Probook 430 G3
My question is is there a way to add a driver manually to Fog’s Kernel where I can get these up and working? Or maybe a BIOS setting I should look out for? I am running Fog version 1.2.0 at this time. I know I will be told to upgrade to trunk but at this point I really cant afford to take the time to do so. I built an updated kernel yesterday hoping it would help but alas it did not.
Thanks in advance!
I ended up just adding them to groups and changing them using the group active directory section. Thanks again for all you guy’s help!
That seems to have done it thanks you guys.
While I am asking questions, in .32 the domain username had to be in domain\username format, however in 1.2 it was updated to just need the username is there an easy way to update all the hosts or should I just change them when I reimage those machines?
@Sebastian-Roth I keep getting this error message when I attempt to run the the last command.
ERROR 1054 (42S22): Unknown column ‘modules.default’ in ‘where clause’
Any ideas?
@Sebastian-Roth You may be on to something. I ran the command with a old host and then one I re-added and got this.
0_1459262584358_Modules_status.txt
Any ideas on how to fix this? Or should we try again with the old database? We still have the old fog server in place where I can check for these records as well.
Update: went to old server and the modules table does not exist in the database.