For now, I have created a fog AD user that has rights to join the domain. the only issue with that is the helpdesk tech needs to have one of the domain admins remove the PC from AD if it’s preexisting.
@chadman00 While I don’t like to jump right into capturing network traffic, I think its going to be the easiest way to understand if you have the filters setup right with dhcp.
Take that pcap and look at it with wireshark. Looks at the OFFER response from your dhcp server. Make sure the boot file name is correct. If you are lost looking at the pcap upload it to a google drive and share it as public and post the link here and one of us will look at it to see if your dhcp server is responding correctly.
The persistent groups plugin is most likely still working.
First, understand how it works.
It’s a simple trigger that’s generated but the trigger gets it’s template from a default host assigned to that group.
The template host name must be the same of the group’s name. In that host, you define your wanted group settings. Then, when you add a “real” host to the group, it will obtain the information in that group.
Ticket can be closed for me.
I’ve captured a completely new image, before doing so, I’ve shrunk the disk, just to make sure.
Deployment is now working as expected for me.
Thanks for your assistance.
@Tom-Elliott I just had a look trough the code and added debug statements. Looks like the $foglang array is being initialized with string values before language is being set (setlocale). Have you got an idea when language support fully worked? I mean it does work for many of the texts but it doesn’t for $foglang texts.
I am wondering if we should move the setlocale stuff from ProcessLogin to FOGPageManager. What do you think?
We need a bit more information to know where to start
What version of FOG are you using
What version of the FOS kernels are you using
What target hardware are you using (manufacturer and model)
If you manually register this target computer, then schedule a capture or deploy (doesn’t matter) but before you schedule the task check the debug check box then schedule the task. PXE boot the target computer and after a few enter key presses you will be dropped to a linux (FOS) command prompt. At the FOS command prompt key in lsblk then take a clear picture of the results and post them here.
@jcabuco scenario 2: is your network or at least that port setup for STP? If so, can you enable rapid or fast initialization of stp, sometimes called port fast or rstp?
Upgrading the Kernel fixed this issue. I am not sure what version he upgraded to but I can now image these new computers. Thank you for your help @george1421
@dooleyrd We need the FOG log from one of the host’s failed attempts before we can tell you anything. It’s normally at C:\fog.log Please don’t snip a tiny piece from this file, but give us a whole client iteration - or the whole file.
@fenix_team Check for Apache errors that are written during an attempt to see logs via the UI. Also check free space on your fog server.
Also, just as a general rule you can re-run the fog installer when you have issues, it’s pretty good at fixing them. As always, I recommend a snapshot/backup before making changes.
