@BardWood Sorry, no change there. I don’t see any vendor class identification in the PCAP. I have searched the web up and down to see if others report similar issues but couldn’t find anything yet.

I really wonder if there is some kind of intermediate switch/router/firewall modifying the DHCP packets?!? Have you had FOG server and Mac client on the same switch yet?

I’m not sure if I should delete the information in the /images/dev/ or if I just need to change a setting somewhere.

@vince-villarreal what feature are you referring to? An image will deploy to a machine based on the storage nodes within a storage group. Assuming both storage nodes are in the same group, it uses a rudimentary load based system to determine which node to deploy the image from.

What version of fog are you using?

Everything seems to work fine until I go to use it, the web interface works no issue but the moment I go to image a pc it fails to pxe then I can’t get back on the web ui giving me err_connection_timed_out.

Ok, config for SELinux has been changed, did a reboot for testing, looking good so far.

Even if I still do not know, how the SELinux got enabled at all, it looks like the issue is solved.

Thank you very much to all of you guys who helped with the issue.

Cheers Nuit

@joe-schmitt Yes. Kaspersky starts when the snap-in finishes.

Sometimes the FOG Client will crash on other snap-ins, but setting the service to automatically restart fixes that issue. This is the only snap-in that does not always reboot after it is completed. I’ll play around with it, maybe adding a wait-time after Kaspersky is installed to let it do whatever it needs to will help.

Cool, I waited about an hour now and data has been transferring to the images folder.

Looks like it is working! I have another question, but will post it as a new topic

How many users do you have on the FOG system?

It’s possible PHP ran out of memory trying to process them all. (you can change the php memory value in the FOG Settings)

edit: Might be a similar situation to https://forums.fogproject.org/topic/11713/503-service-unavailable-error/61

I just found this thread: https://forums.fogproject.org/topic/11713/503-service-unavailable-error/40 I’m going to try some of that stuff and see what happens.

Access was trying to be achieved via hostname. The hostname was routing to a different subnet. Just edited the apache config to look at the server name of the host initially trying to be used, updated the fogsettings file to reflect so future updates don’t break this functionality.

@joshuaian What exactly was the date that it was passing. It wouldn’t matter if it was: 2018-05-13 but if the file was 2018/05/03 then it may have issues as the / represent directory separators in linux.

@cstfoguser does the image have an assigned storage group? Can you make sure it does? Go to the image-> edit -> storage groups. Ensure it’s got an assigned group, click the update/add as needed to ensure it does.

@george1421

Also, something to note, I had another machine I was testing this on and if you do not do the disk cleanup and remove the old windows installations the new inits work just fine. It appears the cleanup messes something up for some reason.

I’ve got a new issue just only with the AD join function… Here in the fog log :

03/05/2018 20:49 HostnameChanger Logon failure: unknown username or bad password, code = 1326

I havn’t change anything about the acount for joining the domain… Is there a new way to configure that ?

EDIT: a server update has desactivated the fog acount (for modifying the password)… Problem solved

@aur3l FOG Settings -> FOG QUICK REGISTRATION tab, config the “QUICKREG GROUP ASSOC” like “Default Group”

But first you need to create a group called “Default Group” (The name of this goup can be other … be free)

Thank you for these examples.
I created the file /var/www/fog/lib/hooks/mobileusernologin.hook.php and pasted your first code, then changed the userLogginIn function with your 2 other codes (and replacing “username1” by “fog”), but I didn’t see any difference in each case: when logging to http://…/fog/management/index.php whith either “fog” account or a “test” account, I still see all the menus.
What am I doing wrong ?

@kagashe check this thread. https://forums.fogproject.org/topic/5300/cant-upload-snapins-anymore

maybe it has something to do with the configuration of your php.ini file. post_max_size upload_max_filesize

what does apache error.log say?

@tom-elliott said in Data missing from the database after host is imaged.:

Fixed in working.

Basically what was happening was the other1 field is used to send emails. That part still can happen (as any value that’s not an email will just not receive an email), but it was clearing the field after it sent the email out.

I just commented out the line as I cannot remember exactly why I was clearing it to begin with.

Thanks Tom!

@imagingmaster21 said in Snapins Not Deploying:

I deleted the snapins and readded them and seems to be working with Chrome.

What do you mean by this? Working with Chrome as in the MSI is being deployed, or working with Chrome when you use Chrome to create the snapin?

So with the ‘manage-bde -off C:’ command, are people then turning that back on once the image is created/deployed? Or given Bitlocker isn’t on, not bothering?

I suppose it’s made me think I should potentially look at turning bitlocker on for some staff members which will probably just be a manual process, but just wondering if I should then be turning the above command on when I do it.