@altitudehack Thank you, you too

@altitudehack You could also run the installer with:

./installfog.sh -y

@altitudehack I’m working to fix the entry points.

@sebastian-roth or the web items are being compressed, but not decompressing for display.

@altitudehack The clear current tasks run the following:

truncate table powerManagement;
truncate table scheduledTasks;

This will restart both tables to ID of 1, but hopefully after this you will be good to go.

@kevinnew22 So, a few questions come to mind:

Is this Active Directory or open ldap?

While I appreciate your privacy, I never understand why people block of “certain” points. I can understand hiding your IP if it’s a public IP address, but if it’s Private it makes little sense to block it. (Private IPs are 192.168.x.x/24 172.16.x.x/16 and 10.x.x.x/8)

First:

LDAP Server should be a dns name. Normally when you look at your domain you will see the “name” it maps to. Of course I have to make some assumptions so please just take my info and adjust as needed.

So let’s say I have a domain called example and the “common” name to map to the same domain is example.com. I would use example.com in the server area. (Of course this assumes DNS is handled by the domain as well which is generally common.)

LDAP Server port. If you’re using LDAPs you will likely need to import your domains certificate tree to the FOG Server for it to work properly. (I don’t understand why you blocked this out because there’s only 2 parts. So if you’re using 389 as the server port, this is not a secure port. Otherwise it is the secure port.

Search Base DN looks correct though I don’t know if it actually matches your domain structure.

Your Group Search DN may be correct but I’m not sure. Of note, with this being set, any group you’re attempting to match must reside in here. So I see your Admin Group is set to Admin. So under {blank}.sa -> grupo {blank} should contain the admin group. If it doesn’t this would be reason for you not being able to log in with your LDAP information. To generalize it for testing at least, you should probably set Group Search DN to the same as Search Base DN.

Admin Group appears correct assuming you have a Group named admin in your domain.

Mobile Group appears correct but is redundant. As you already have this setup for the Admin Group, this is unnecessary. It’s going to set the user as admin, so having Mobile user filled in with the same group doesn’t do anything.
Please Note with both of these, you can use multiple groups by separating them with commas. For example, you could associate all admins for the group admin and domain admins by entering int he Admin Group field: admin,domain admins

Username Attribute looks correct assuming Active Directory

Group Member Attribute looks correct assuming Active Directory

Bind DN appears to be correct though this is totally on you.

Bind password is already set but I have no way of knowing if it’s correct.

Of note, there are logs that are written when theres an error that might help you troubleshoot too.

On redhat based linux, this is /var/log/php-fpm/www-error.log. You would need to look up your systems error log. For Debian this might be /var/log/apache2/error.log, but it could also be under /var/log/php{phpver}-fpm/www-error.log (or very close to it) replacing phpver with the running php version (can be known by running php -v | awk 'match($0, /^PHP (([0-9])[.]([0-9]))[.][0-9]/, ary) {print ary[1]}'

Hopefully this helps narrow down where to look.

@coxm There isn’t really an “auto imaging” field per se.

The imaging happens via a few different methods, but only one could kind of being “Auto”.

So you could have a scheduled task (cron style) that could be considered “automated”, but I would not consider this “auto image”. To check if you have any scheduled tasks: Tasks -> Scheduled Tasks should show them all.

You could have a host in a task. Again this isn’t “auto image” and would only “hang” on a task if there was an error during the process. Check: Tasks -> Active Tasks or any of the other imaging styles (Multicast, Scheduled, Active, etc…, Snapin tasks do not require imaging of a machine to run, so you shouldn’t need to check here.)

You can task hosts via the PXE Menu, but this requires physical intervention to setup.

The only Auto-Image I would consider in the sense of what you’re asking, is from Quick Registration. You would need FOG Configuration Page -> FOG Settings -> Quick Reg -> Image defined. Then you would have to boot an unregistered machine and tell PXE to perform a quick registration. Once the registration completes (no user intervention beyond selecting quick registration) it will reboot the machine and immediately boot into PXE and will be deployed the image defined.

So you can change an image defined to any host at any time (other than if it’s in a task currently) and it will not “auto-image”.

Let us know if you have any other questions.

@robertkwild yes, it can.

@tesparza You can update the information in FOG Settings, but it will not automatically apply it to the hosts. This is just the “default” storage point, not the thing each host uses.

If you update the AD information on each of the hosts, it will rejoin the domain using the new information. No need to redeploy the image or client.

To change all the hosts more quickly, create a group, add all the hosts you need to change into the group. Then update the AD information from within the group.

@michaeloberg

As this is for testing I’d suggest:

wget -O /var/www/fog/service/ipxe/bzImage-rt-v215 https://drive.google.com/uc?id=1qxcjC9ZrV8lVh4T6rgBtmtgSp7SWRzL9&export=download
wget -O /var/www/fog/service/ipxe/bzImage-rt-opts https://drive.google.com/uc?id=1t4WgWHOv3wIFjnodRtMsRcaO87XIZxM4&export=download

From the host in question, assuming it’s registered, go to edit it and in the Kernel field type in the name of the kernel file to test:

E.G.:
bzImage-rt-v215
bzImage-rt-opts

I don’t know if you purposely deleted, but I will say our community isn’t as harsh as the arch community with questions.

That said if you’re okay with it, copy the files you change to your git clone as appropriate and run git diff

To complete installation run:

./installfog.sh -yX

it will take a bit but it will continue.

@fabiano-matos et al.

The TSC DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later)

Isn’t really an issue in the context of imaging. This is just meaning the microcode of the controller is older than what the kernel is expecting. Itself, is not an issue you should have to be worried about.

As far as your DHCP failed or we were unable to access…, that’s seeming to indicate the issue in your case is specific to not being able to get a DHCP address for some reason. This could be due to STP going alive, then down, then alive but the down period is longer than the period that FOG is trying to get the IP address. I haven’t been around very often recently, but I do recall there was a version or hold pattern that was set by the UI that could hopefully determine if this was indeed the issue.

Please see if STP is enabled on your network and maybe enable Fast STP RSTP or whatever it is called in your environment or disable STP altogether if you can.

@fabiano-matos I’m only giving information that I know when I don’t know all the details.

If other machines aren’t having an issue, maybe try changing the port the machine is linking up to to see if that helps.

@robertkwild Yes, at least by default. I don’t know how frequently we’ve had things actually usable from a partition to partition image, but typically the flow is:

Erase the Existing drive
Configure the Existing with the image partitioning schema
Write the image to the disk
(If resizable - expand partitions)
Reboot

@george1421 yes, you can extend an xfs partition but we can’t decrease it. Not nicely that I’m aware of at least.

@zaboxmaster You can probably accomplish this with a postinit script to overwrite the existing erasure script that runs.

I don’t have a direct example, but you can use the base script to essentially iterate over all hdd’s on the machine and perform the same actions.

@lukebarone Just so you know I’m not crazy lol:

https://github.com/FOGProject/fogproject/blob/b619bfe7b4cd8afff80a7c0a3fa56c1f6d3741e3/packages/web/lib/fog/fogftp.class.php#L464

@Jasper507446 Just because a host is part of a group does not mean they have an image associated to it.

@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.