New Machine Problems
-
@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.
-
@Andrew134 for uefi mode 1.3.0 works a bit better since it has the updated iPXE drivers too. Also with uefi mode you need to ensure that secure boot is disabled in the firmware.
On the lenovo, if you can switch to legacy mode please do that, then pxe boot into the fog menu. Your dhcp server will need to be sure you are sending undionly.kpxe to these systems. Once you get into the FOG iPXE menu select the compatibility test menu and ensure that both the hard drive and network adapters are supported.
-
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?
-
@Andrew134 upgrading is supported. http://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk
-
@Andrew134 said in New Machine Problems:
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.
You have to remember that FOG 1.2.0 is almost 3 years old (SVN 2094). With 1.3.0-rc1 somewhere north of 8600 there has been a ton of changes to FOG too. Hardware has changed so much since then its hard for the system to support it. Consider Windows 7 (which is still being actively installed today). You can’t install it on the new systems that have NVMe disks without first apply 2 hot fixes it (before OOBE boots the first time). Windows 7 does not support NVMe disks or new hardware without the proper drivers. There are other examples of network cards behaving differently because some enhanced functions have been off-loaded right into the network card. There are many more examples of why its past time to retire 1.2.0, that is why the devs are working hard to get 1.3.0 released as stable very soon.
So hang in there and follow the instructions to upgrade to trunk
-
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?
-
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.
-
@Andrew134 OK so can we say there is something different in how fog 1.3.0-rc1 handles the previously captured image?
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.
-
@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.
-
@Andrew134 @Developers a little input on adjusting the image here?
-
@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.
-
@Andrew134 Which ever you decide on this hardware, you will be happy with the 100s of improvements with the 1.3.0 build over 1.2.0.
I would suggest that you go through the global fog settings and then look at the storage node settings to be sure they are now consistent with what you need.
-
@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.
-
@Andrew134 Lets see.
I don’t use fog to connect the target to AD but use the unattend.xml file instead so, I’m going to have to make some educated guesses.
You have the FOG client installed on the target computer? If so did you remember to start the fog client service and is it running?
For the target computer are you sure you have the AD credentials set in the host properties in AD. That defined user account must have domain edit rights.
Did you properly define the OU path for the target computer? -
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.
