@alexamore90 That sounds like a job for the unattend.xml file as part of a generalized hardware agnostic build of windows, not something FOG in a post-install script would be able to accomplish.

@AlkarimJ Are the disk sizes equivalent to the original source machine that created the image?

A lot of new machines have a smaller built in (or sub ssd) that links to the main drive, but FOG would see this as its own individual drive.

(I don’t know if that describes it)

The fact that the image type os Single Disk (Not Resizable) is the reason I ask the question.

The original partition layout is LARGER than the size of the disk on this specific machine, which it should fail. There’s not enough space to put the image in the appropriate places on the drive.

@zuchowra This often happens because of either the DHCP server isn’t presenting boot options, but more often it’s because you ahve multiple things responding with what server should be used. The system has no idea which one to use, so it requests you manually enter it.

Please check your dhcp server to ensure the boot option is sending option 66/boot server name

@Enigma Are you sure it’s booting PXE and not UEFI?

In case it is UEFI, please disable secure boot on the machine.

This is actually really simple to accomplish.

In the file that you found (/var/www/fog/lib/fog/BootMenu.class.php:

Look for the four lines:
[php] else if ($_REQUEST[‘qihost’] && !$_REQUEST[‘imageID’])
$this->setTasking();
else if ($_REQUEST[‘qihost’] && $_REQUEST[‘imageID’])
$this->setTasking($_REQUEST[‘imageID’]);[/php

They are at about line numbers: 655 thru 658

Place the lines in the else statement at line 677? right after the curly brack. Remove the first else in the statement so it’ll look like:
[php] if ($_REQUEST[‘qihost’] && !$_REQUEST[‘imageID’])
$this->setTasking();
else if ($_REQUEST[‘qihost’] && $_REQUEST[‘imageID’])
$this->setTasking($_REQUEST[‘imageID’]);[/php]

This won’t, by itself, keep the system from requesting a username and password, but all you should have to do is press enter.

With that you still have to select which image (if host has image already, it defaults to point at that hosts image, but you can choose any you please.)

An even better method would be to just remove the:
[code]login[/code]
from the fog.quickimage database entry.

Replace the lines
[code]param username ${username}
param password ${password}[/code]
With something like:
[code]param username fogusername
param password fogpassword[/code]
In the fog.quickimage database entry.

This should keep it from asking about a username and password as well as allow BootMenu.class.php to remain un touched.

I’ve decided, based on the multiple people wanting to customize the main boot items directly even, to re-enable editing so you can do this from the GUI now as well. So you don’t have to edit a file and you can make your changes
as needed.

@george1421 This sounds very similar to old old equipment?

Hubs vs Switches and the Hub is literally at capacity

@DBCountMan Yes,

There’s under FOG Client Settings from the FOG Configuration page, a “Pending” option that can be disabled “globally”, among other items.

See here:
https://wiki.fogproject.org/wiki/index.php/FOG_Client#Features_overview

You’re specifically looking for Host Registration

@DBCountMan It knows nothing of GUIDs as we don’t have a nice way to know what is what and in a consistently generatable method (believe me when I say we went down that Path and while we made some progress it wasn’t exactly feasible and has since more or less fallen off the radar.)

We use the device’s mac address’ to determine which host is attempting.

So if the primary device’s name is ME and the mac is 00:00:00:00:00:00, and you add a device with mac address 00:00:00:00:00:01, it will send both macs and lookup the device. ME will be found and 01 ending will be associated as pending mac to the device.

@JackYwn Please try this:

curl -kOL https://github.com/FOGProject/fos/releases/latest/download/bzImage
curl -kOL https://github.com/FOGProject/fos/releases/latest/download/bzImage32
curl -kOL https://github.com/FOGProject/fos/releases/latest/download/init.xz
curl -kOL https://github.com/FOGProject/fos/releases/latest/download/init_32.xz
curl -kOL https://github.com/FOGProject/fog-client/releases/download/0.13.0/FOGService.msi
curl -kOL https://github.com/FOGProject/fog-client/releases/download/0.13.0/SmartInstaller.exe

@george1421 This link might help:
https://forums.fogproject.org/topic/10160/virtualbox-pxe-boot-no-configuration-methods-succeeded

it’s the use of EFI booting a PXE booting system:

It’s been a long long time, but VirtualBox back then didn’t have EFI Network booting capability, and I suspect this still may be the case.

May need to adjust the boot options to use boot classes to provide ipxe.pxe for this virtual box host. I don’t recall how to do this right now.

@Chris-Whiteley This is a table of FOG from the older “virus scan” capabilities. It was a storage point for if and what it found on machines it had scanned.

@tiefel From what I can tell you hit enter on the part it asked you to go to the browser and actually submit the database insert/update process.

It literally needs the database to run.

So you can do this automatedly doing:
./installfog.sh -y Which will set all the default options and just make your involvment less involved. Of course if you’re not wanting to be that involved, please follow the on screen prompts as they occur.

Mind you if you go through the point of the install and while ti’s installing packages, the enter’s you press will translate as proper inputs later when you may not have intended them to occur, please take care and use patience.

@rogalskij The fog client only uses outbound 443/80 TCP to communicate to the fog server. All communications are totally reliant on your fog client installation of course too (for example if you installed with https, it will only use 443. If not it should default to attempting to port 80).

Hopefully that helps?

It’s worth noting the FOG Client is a polling system so it checks in with the fog server every so many seconds/minutes, so if you put a task on the server, it’s not immediately pushed to the system in question.

@rogalskij It should not need inbound at all. I do not know why it’s not working, but maybe you can provide the machines FOG Client log?

That usually sits in C:\Program Files (x86)\FOG Client\fog.log (or relatively close)

@rogalskij So while the images were lost, the issue in this particular case seems more in line with the problem that was originally described (and fixed) with the check disk utilities.

Can you boot into windows and run check disk, scan disk/verify disk on this machine? I presume this is only happening for this particular machine and as such may just be related to it alone.

I know the chkdsk and scan and all that will take some time, but while we do have utilities that can perform these actions somewhat automated, it’s also not the ‘native’ tools and Windows would have a much better system for performing the checks than what our tools will.

@rogalskij This is very interesting as initially I thought this was on some code I wrote (not that it still couldn’t be) but appears more like maybe the percent of free disk space has been unset and your drive is literally sitting as full as if at the hotdog championships and Joey Chestnut just won for 75th time in a row.

There’s a field in fog that is supposed to ensure free space left on the disk, but where yours is failing seems to be due to paging space / minimum size.

I might suggest, if you’re up for it again

Chkdisk again a few times,

Also defragment the disk a few times. THis should move your paging file (which cannot be resized around) toward the end of hte disk which shoul’d prevent the no space left on device issue I believe you’re currently seeing.

@Fog_Newb That’s an interesting fdrive you got there

Not sure how that would work but to your actual question:

Please try:

touch /images/.mntcheck

As that error is indicating that the /images mount (for deploy points) is missing that file.

@Fog_Newb there is a new sed statement that is trying to set the port for mountd to 20048, but seems it may be setting all ports after mountd to 20048. We are aware but trying to figure out why and how to fix.

@AUTH-IT-Center Should be addressed in the latest.

@george1421 we added a little security bit now too as getting the hostinfo gave us the host sensitive information (ad user , domain , password, etccc.)

https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog#L9

This is the main difference.

We now need to get a token, and pass that token back to the hostinfo (it’s one time and locks upon initial request.)

Edit: Apologies on not posting the direct example, this was written while from my phone, not at a computer so copy paste wasn’t really “suitable”.