Solved. See here.
Basically I changed the php version to 7.3 (which took a lot of effort…)

@seribe I am sorry but the stack of things to do is huge and I haven’t found the time to look into this as I need to focus on the core code. The plugin code was developed (and is kind of maintained) by @Fernando-Gietz. He might find some time to look into this.

@lakk said in Host Management - "No Data" instead of date - FOG 1.5.7:

but when i open the “host management”, its is written “No Data” instead of a date when the image was captured:

Now that I have tested myself and read through this again I see what I have been missing here last time. The column Imaged is only being filed with a timestamp when a host is being deployed (imaged) but not when captured from it! This has not changed in the past and I don’t think your Vbox settings change has anything to do with this.

Now to your second point about the dashboard display. When I do a deploy I see:

Free: 9 Queued: 0 Active: 1

So working all fine from my point of view. Unfortunately the pictures you posted are not accessible anymore and so I can’t be sure I really get what you mean.

I’ll mark this topic as solved because the first question is being answered. Please open a new topic with screenshots about your other question. We try to keep things separate to make it easier for other people to follow and find help in the forums.

@3mu said in FOGSnapinReplicator.service failing on fresh install:

php[9501]: Could not open input file: env

I totally missed this part in the log when looking through this some time ago. Have been way too busy with other things at that time and obviously missed this. This issue has been fixed a while ago and I cannot imagine this to be the case in the release candidate versions or dev-branch anymore. I just did a test install using dev-branch on Ubuntu 18.04 and I don’t see the messages as stated above.

From my point of view this has nothing to do with specifying a router or not!

@bishopga Check out the BIOS settings to see if the disk controller is set to AHCI or RAID? FOG (Linux) is not able to handle the controller in RAID mode…

The answer lies in the configuration of the routers. They must be able to route client requests from the client’s network to the DHCP server’s network. One of these simple rules of the router is " IP helper."This simply tells the router to redirect DHCP requests to the known IP address of the DHP server. I used to always use a VPN or proxy server, but this slowed down my connection and my computer. There are some VPNs that are worse than google chrome, it was mostly because I was spending time on Pirate Bay and it was blocked a lot. You can use one of PirateBay proxies to access it always with no problem.

@george1421 said in Getting Kernel Panics after upgrade to 1.5.9-RC2:

I’m kind of curious if the installer looks specifically for 127000 and will only increase it if it matches. I’m surprised that 250000 remained after the upgrade to the latest release.

I have not had a look at the code for this yet but it might be the case…

george1421, you are a bad mofo! I’ll try this out later today and report back with the results.

Thanks brotha!

@george1421 Hi folks - so sorry huge influx of users back today, had to get on with other bits.

All three of your points correct though George yes. Although I’d add in on point 2 that it won’t WoL until power is unplugged for about 20 secs and also, following that, the PC is then booted to BIOS for a few seconds or paused at the polling for DHCP part of POST, and then shut down again. That will “prime it” for WoL and WoL will work thereafter until Windows is booted, then it won’t until you repeat the above “priming” process.

Thanks again everyone.

At this stage it’s not looking like a FOG problem strictly, so if you’re getting sick of it it’d be fair to say it’s outside you folks’ remit but I do appreciate the help muchly.

Hello,

This thread is very well referenced by search engines so I complete it with my experience.

I installed a new storage node on my FOG (Debian 8 + 1.5.7) setup (before : web server / central node + two storage nodes, after : web server / central node) + three storage nodes).

During the installation, I failed on question “What is the IP address or hostname of the FOG server running the fog database?”. The default value is the storage node itself. The mysql command given by Wayne Workman worked from my new storage node, the problem was on FOG side.

I understood my mistake. So, I modified “snmysqlhost” in /opt/fog/.fogsettings with the address of the FOG web server / central node.
I restarted the FOG services (systemctl restart FOGSnapinHash FOGImageReplicator FOGImageReplicator FOGImageSize FOGTaskScheduler FOGSnapinReplicator FOGPingHosts FOGMulticastManager).
The problem was still here.
I rebooted the server.
The problem was still here.

I executed installfog.sh a second time on my new storage node. It detected the existing installation. It did some stuff and… the new storage node works fine.

Regards.

@DJslimD1k the mysql value is still pretty high. Higher than I might expect. But switching from isam to innodb helps because isam uses table locking on update and innodb uses row locking. With a lot of clients polling that table locking method becomes a road block.

I didn’t look back in the tread, but didn’t your fog server have 10 vCPUs? If so I would drop those back to 4 and see where performance settles out to. Overcommiting on vCPU is worse then not providing enough vCPUs to handle the load.

Having that many php-fpm workers just means that your server is busy with requests. There is some performance tuning you can do with the php-fpm settings on a busy network by switching from dynamic to allocation to static allocation.

@Piplup said in Need urgent help on joining a domain automatically after installation:

Thank you, but Christ, that’s a lot.

Its not bad if you build it up, start with the basics and add on.

I’d create an InstallUser for the AD with limited rights, which will be automatically joined to the Domain via a fixed entry in the “unattend.xml”. (?) Software will already come preinstalled with the image. From there on, the User manually Signs Out and Signs In via his given AD credentials.

Yes that is how we do it. Here is an example of an sanitized version of our unattend.xml. https://forums.fogproject.org/post/87392 The point of the tutorial link I provided before was to show you if you have text in your unattend.xml file you can “tweak” it at deploy time. Its really NOT that hard. The bit I didn’t show you was the complete working model: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed This is the full working postinstall script it does more than what you need at the moment. The script you are interested in is fog.updateunattend

Doesn’t an Active Directory Domain join require Administrator privileges from the Domain Controller in the first place? Wouldn’t I just create a security vulnerability…? If you have experience in this, please share your advice.

Yes and no. Yes you need an elevated account but you can restrict that account to only add computer to ou. Its been a while since I set that up but I know with advanced acls you can restrict that account to only the task at hand. Also if you use the WAIK toolkit you can encrypt the password in the unattend.xml file so it can’t be hacked easily. Lastly in your setupcomplete.cmd batch file, you will have that nuke any unattend.xml file or another other setup files that are used during OOBE/WinSetup.

@Sebastian-Roth Thank you for your feedback! I found the solution the dnsmasq file had just the ip of the server in dhcp-range without the subnet. So I adjusted the line dhcp-range=192.168.0.23,proxy to dhcp-range=192.168.0.23,proxy,255.255.254

Thanks for the feedback, sorry for my late response.

@ethanxp2 said in FOG Issues with HP EliteBook 735 G6:

This morning at 10am, for some reason, you can no longer deploy to any of these laptops.

Dell Latitudes seem to image okay, HP 735 are a no go.

and it won’t pxe boot again until you reset the BIOS.

get stuck where they try and PXE boot … Initializing PXE boot

The relevant and somewhat bits I see.

Someone random thoughts…
So is it time of day based, where if you reset the clock on the FOG server and pxe booting computers every things works?

FOG is still imaging because the Dells work. So we can probably rule out the FOG server.

What does resetting the BIOS have any impact here. FOG doesn’t touch the bios on any brand computer. It simply doesn’t have the capabilities.

Is it Initializing ipxe devices… where it gets stuck? Having clear screen shots of the errors is helpful in setting the context of the problem.

We are at the iPXE stage of booting so the issue isn’t with the FOG server or the FOS Linux cloning engine (kernel) so these can be ruled out for now

Specific questions…

Has the firmware (bios) been updated on these computers to the latest release?

What happens when you reset the firmware back to factor defaults?

What version of FOG are you running?

Are these computers running in bios (legacy) or uefi mode? Since they seem pretty new they may be uefi only.

It is already solved forgot to turn on the plugin.

@george1421

I did it !!

So I basically made a Frankenstein’s monster version of my image.

As I’ve stated in my last comment, I had an issue where the windows drive did not have the same partition number.

I created a new legacy windows 10 VM, with a smaller C Drive than I created the very first time I worked on that image. I converted that installation into UEFI.
So now my newly installed win10 and my oversized image have the exact same disk structure.

I deployed the partition containing all my data onto the new VM, and I had an issue where the UEFI boot was broken.

I used the tools in the installation media to repair the EFI partition. I used diskpart to assign a letter to the EFI partition, exited diskpart and ran this command :

bcdboot C:\Windows fr-fr /s B: /f

Windows booted.
Now I’m capturing the image and I’ll deploy it to make sure it’s working fine
Thanks for all the help and ideas!!

Regards,
Dan

@AxeMeAQuestion22 said in Kernel Update Issues:

Host: 172.16.20.19, Username: fogproject

Are you able to login to your FOG server via FTP using these hostname and IP?

@Sebastian-Roth Thank you so much! You save my life (almoste 😉 ) It was about ipxe.efi, I have change to realtek.efi in DHCP and now it work fine. Nice work thank you ^_^

@george1421 When the user gets the computer, it boots into Windows. But, it doesn’t just boot directly into Windows. It will go through a setup process before it hits the login screen with no user input required, just a network connection (preferably on our network for domain join). This process includes adding the machine to the domain, creating local user accounts, etc. Once the user logs in, a few other programs will load. But, for all intents and purposes, the machine is ready to go when the user gets to the log in screen.

So, my thinking is similar to yours in that I should be able to run FOG to capture what is there before it does any of the initial set up and use that on every machine without worrying about service tags. Admittedly, I’m not completely in the know on the Dell boot process with our image since I’ve not worked on that part of the imaging and will need to talk to the people who do. But, again, like you said, it seems like it shouldn’t capture that service tag until it goes through OOBE/Winsetup, thus getting it before booting the first time should work.

I’ll talk to the head of that team on Monday and keep you updated.