@george1421 This is correct. It works fine. Thanks,
Best posts made by lperoma
-
RE: Could not mount /dev/sda3: Metadata kept in Windows cache, refused to mount.posted in FOG Problems
-
RE: Attempting to join domain: The parameter is incorrect, code = 87posted in FOG Problems
This worked for me :
Domain name: subdomain.domain.tld
OU: OU=Computers,DC=SUBDOMAIN,DC=DOMAIN,DC=TLD
AD DEFAULT USER: adminuser
Domain Password: supersecret
Name Change/AD Join Forced reboot?: chekedNot sure if I was doing anything wrong, I tried too many things, but this now works. Thanks.
-
RE: Kernel Panic - not syncing, unable to mount rootposted in FOG Problems
Is your machine trying to boot bzimage32 ? send a picture if you can.
-
RE: Could not mount /dev/sda3: Metadata kept in Windows cache, refused to mount.posted in FOG Problems
OK, looks like Disable Fast Startup in Windows solved the issue. Sorry for the noise.
Latest posts made by lperoma
-
RE: A reimaged host stays stuck on an old directory join plan ("marker absent; automatic retry refused")posted in FOG Problems
Thanks Tom, I tested #2122 and it does what you described.
I applied the two
srcfiles of the PR by hand on top of thepatcheschannel (schema 465, agent 0.1.28) and reproduced the same situation with test-bios. First Deploy (16928): the agent asked for the directory join and the plan went toawaiting_reboot(attempt12f448e3…,trigger_task_id16928). Before it rebooted I powered the VM off and queued a second Deploy (16929), which completed normally. The agent enrolled by itself after that (rebind, approved via deploy).For a while the old plan was still in
hdRejoinState, stillawaiting_rebootwith trigger 16928, so right after queuing the Deploy nothing had changed. Once the machine booted the new Windows and the agent checked in, FOG replaced it on its own. A minute later there was a new attempt (3e64f53…, trigger 16929,awaiting_reboot). I didn’t touch “Clear directory operation review” or edit anything in the database. After one reboot the host wasverified,hdJoined=1,hdKind=ad,secure_channel: healthy.So the old attempt is dropped after the new Deploy and the first boot, not at the moment the Deploy is created, which matches what you wrote. It only looks odd if you check the host in between and still see the old plan. No problem on my side, just mentioning it in case anyone else notices the same thing.
One idea, only if you think it’s worth it: a checkbox in the Deploy task form, something like “discard every pending task of this host”, unchecked by default. The automatic rules are safer for the normal case, but sometimes the admin knows everything left over from the previous install is dead (queued tasks, snapins, a pending directory join) and wants to force a clean start right when the Deploy is queued, without waiting for the first boot and without the “Clear directory operation review” box. In our case, when a machine misbehaves it often keeps snapin tasks queued, and today you have to open the host, work out which tasks it has and delete them one by one. In a big fleet that is slow and easy to get wrong, whereas one box on the Deploy would clean the slate in a single step.
I’ll drop my manual patch when #2122 reaches
patches. -
A reimaged host stays stuck on an old directory join plan ("marker absent; automatic retry refused")posted in FOG Problems
Hi Tom and everyone,
First, thanks for the quick work on the shared adapter and enrollment issues. I tested #2116/#2118 today and enrollment behaves now. While doing that I hit something else with the directory join that I think is worth a thread of its own.
Setup: FOG 1.6.0.158 stable moved today to the patches channel (schema 465, so it includes #2111, #2112, #2113, #2116 and #2118). Two Proxmox VMs (test-uefi and test-bios) deployed from the same image, whose source machine already has agent 0.1.28. Both hosts are set to join AD and both had been deployed once before today.
After the second Deploy, test-bios joined the domain without any trouble. test-uefi never did. It kept the Windows name “instalacion”, stayed in the workgroup, and installed its software normally (Chrome, VLC, 7-Zip and Avast, before the activation snapin, which is the order we wanted). The agent log shows this every minute, and nothing else about the directory:
2026-11-20T19:24:29+01:00 this state was made on another machine (a cloned or reimaged disk); generated a new key and enrolling as this machine 2026-11-20T19:24:29+01:00 enrolled as host 666, certificate valid until 2027-11-20 18:24:29 2026-11-20T19:26:01+01:00 facts: sending inventory=true software=6 directory=true printers=4 network=1 2026-11-20T19:26:04+01:00 directory rejoin: directory rejoin marker absent; automatic retry refused 2026-11-20T19:28:55+01:00 directory rejoin: directory rejoin marker absent; automatic retry refusedSo the very first directory poll after the reimage was already refused. On the server,
hostDirectory.hdRejoinStatefor that host had this (trimmed):"phase":"awaiting_reboot", "attempt_id":"add87a0f...", "trigger_task_id":16923, "last_deploy_task_id":16923, "retry_authorized":false, "placement_hold":trueThe Deploy that had just reimaged the machine was task 16927, newer than 16923, but it did not replace that plan. The computer account was fine in AD (it existed and belonged to the account FOG uses to join), so it was not an account problem.
Reading the code, this looks like the intended protection:
PROTECTED_PHASESis started, awaiting_reboot, unknown and failed, and only a plan inreadyis dropped when a newer Deploy arrives (dropSupersededPlan, reasondirectory_task_superseded). That makes sense for the old disk, where the join may really have happened. But after a Deploy the old disk is gone. The plan waits for a local marker and a reboot that can no longer exist, the new install has no marker, so the agent refuses, and the server keeps waiting for the agent. Neither side ever gives up.What happened to this host before is simple: it had a join plan pending that never actually ran, I reinstalled it, and it got stuck on that old plan. I can’t show you the log of the earlier install, because the reimage overwrote it, so the odd part is that the stored state says awaiting_reboot for something that, as far as I know, was never executed. test-bios did not get stuck, and its previous plan had ended in “verified”.
The way out is the “Clear directory operation review” checkbox, and here is where I got a second surprise.
clearReview()writes a new state withlast_deploy_task_idset to the latest Deploy and dropsworkgroupandobservation. As far as I can tell, with the Deploy counted as already used and no workgroup flag, nothing gets planned afterwards. On a real PC earlier today, ticking the box left the host with no plan at all. I added"workgroup":trueby hand and FOG did plan a join, but that agent never ran it and I joined the machine manually.For test-uefi I wrote the cleared state by hand instead:
reason: operator_cleared,workgroup: true, andlast_deploy_task_idset to the previous Deploy (16923), so that 16927 was still pending. On the next poll FOG created a new plan (ready, trigger 16927), the agent ran it (awaiting_reboot, no error), and after a reboot it went toverifiedwith the host joined. So the join itself works, and only the stuck state was the problem.What I would suggest, if you agree:
- A new Deploy for a host should clear everything that was pending for the previous installation: queued tasks, snapin tasks and directory join plans, not only plans in
ready. This includes plans in started, awaiting_reboot, unknown and failed, because they refer to a disk that has been replaced. Whatever the Deploy itself creates (for example the snapins attached to it) would of course stay. I only checked the join plans; I have not tested what happens to old queued tasks and snapins when a Deploy is created, so please take that part as a suggestion. - The review checkbox should keep
workgroupandobservation, and should not mark the latest Deploy as used, so the next poll can plan the join again. - When the agent says “marker absent; automatic retry refused”, the host’s Active Directory panel could say that this needs the checkbox. Right now the only hint is in the agent log on the machine.
Open question on my side: I don’t know why that first plan was in awaiting_reboot if it never ran. If there is something I should capture the next time (agent log before reimaging, a particular field of the state), tell me and I will.
Thanks!
- A new Deploy for a host should clear everything that was pending for the previous installation: queued tasks, snapin tasks and directory join plans, not only plans in
-
RE: Feature request: a way to handle USB Ethernet adapters shared between many hostsposted in Feature Request
Hi Tom, thanks again for the shared-adapter work.
We hit a case with the new agent that your replies in this thread don’t spell out, and while reproducing it we found a few more things, so here are the details.
Setup: FOG 1.6.0.158 stable with #2100, #2104 and #2111 applied by hand,
FOG_HOST_IDENTIFY_SMBIOS=register, agent 0.1.24, Windows 10 IoT LTSC images, HP laptops that boot from the shared USB-C Ethernet adapter.What worked yesterday and what doesn’t today: yesterday, with #2104 and #2111 already applied, we tested two VMs with a duplicated MAC and FOG handled it fine at PXE (
register, firmware first). Today, when we reinstall hosts whose firmware is already registered, it is the agent’s enrollment that fails when a MAC belongs to another host.The laptop that could never enroll
The laptop’s host has a full inventory (system serial, UUID, board serial), and no other host has any of those values. Boot worked: PXE identified it correctly through the shared adapter, since in
registera unique firmware match wins over the MAC. But the agent tried to enroll every 5 minutes and always gotHTTP 409 with status "error", 16 times in a row. Each attempt left this infaults-web.log:Database save failed: Class: AgentEnrollment ... SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (`fog`.`agentEnrollment`, CONSTRAINT `fk_agentEnrollment_aeHostID` FOREIGN KEY (`aeHostID`) REFERENCES `hosts` (`hostID`) ON DELETE CASCADE)The agent sends two MACs: the shared adapter’s, still stored on another laptop’s host, and one of its own that no host had. Reading the code,
MachineIdentity::choose()returnsconflictwithhost_id0 when the firmware points to one host and a MAC points to a different one.Enrollment::enroll()then sets the reason toconflictand saves the row withhostID0, which doesn’t exist inhosts, so the foreign key fails and nothing is stored. Nothing shows up in All Pending Agents, so the admin never sees it. The agent enrollment code only checks whether the setting isoff, soregisterandenforcemake no difference there.We worked around it by deleting the adapter’s MAC from the other host. The very next attempt enrolled fine (
known-host-no-agent).Reproducing it with a VM
We gave a VM the MAC of another VM’s host (approved,
hmPending=0). Its firmware UUID names its own host. This time the conflict was stored: All Pending Agents shows it asidentity-conflict(the enroll got a 202) and the agent logs:directory rejoin: this machine's MAC addresses or SMBIOS identity match more than one FOG host; ... this state was made on another machine (a cloned or reimaged disk); generated a new key and enrolling as this machine pending approval on the server (identity-conflict); waitingThat row has no
_directoryIdentity. After the agent restarted, every enroll gotHTTP 409 with status "error"again, but with no database error infaults-web.log. We approved the pending row, restarted the VM, and the agent still gets 409 while the row staysissuedwith its certificate uncollected. As far as we can tell fromMachineIdentity::enrollmentGate(), it returnsupgrade_blocked: the stored row doesn’t have_directoryIdentityand the new request declares it, and that check runs before the row’s state is looked at. We haven’t confirmed that part on the agent side.So the same mismatch seems to end in two different 409 loops. If the agent declares the directory-identity feature from its first contact (the laptop, whose rows all have
{"required": true}), the conflict goes throughMachineIdentity::resolve()and ends with host 0 and the foreign key error. If it doesn’t declare it at the first contact (the VM), the conflict is stored, but the agent is locked out as soon as it starts declaring it, even after the admin approves.What we expected
A shared MAC shouldn’t be a conflict at all when the firmware identifies a different machine, which is what
enforce/registeralready do at boot. So:- Could agent enrollment follow the same rule as boot, so that a unique firmware match wins over the MAC?
- If a conflict is meant to apply there anyway, the row should be saved with the host the firmware matched (or none) instead of host 0, so it doesn’t fail on the foreign key.
- All Pending Agents only shows the Windows name, the reason, the IP and the UUID. It would help to show which host the conflict is with, so the admin can tell it’s another machine before approving.
- Approving a conflict should let the agent collect its certificate, even if the stored row was created before the agent started declaring the feature.
Happy to send full log lines or test a patch. We’re posting a second, unrelated problem (the “Clear directory operation review” button leaving a host unable to join) separately.
-
RE: FOG 1.6 – Dependencies between Software Management and Snapins?posted in FOG Problems
Thanks Tom, this is useful for us too. We use the same modules, and we have the opposite constraint to the one in the first post. We haven’t hit it yet (our hosts are still on 0.1.24, and we’ll test 0.1.26 on a VM first), but it follows directly from the new order.
Our setup
- One group with Chocolatey packages, including Avast Business (its own package generated by us).
- In the same group, one snapin run with
powershell.exethat checks the Windows activation.
What we expect
- Once Avast is installed it generally blocks PowerShell on our machines, so PowerShell snapins stop working.
- Until now the snapin ran first and the software after, so they never collided. With software always before snapins, the Avast package may install first and block the snapin.
Two suggestions, both as a per-snapin flag on the group’s snapin grant (so only the snapins that need it are affected, and other groups behave as today):
- Run before software. A flag on a snapin granted by a group, to run it before the host’s software instead of after.
- Run when a host joins the group. Today a group’s snapins are only used when a task is created (Deploy, Single Snapin, All Snapins). Software is applied as soon as a host is in the group; it would be handy for such a flagged snapin to be queued once when a host joins, if the host never completed it before.
Both default to off, so nothing changes for anyone who doesn’t set them. We’re happy to test any patch on our server.
-
RE: Feature request: a way to handle USB Ethernet adapters shared between many hostsposted in Feature Request
Quick update: we’ve tested PR #2111 and it works perfectly for us.
Setup
- We also updated from 1.6.0.14 to 1.6.0.158 (stable).
- On top of it we applied #2100, #2104 and #2111 by hand (we skipped the schema 462 step, since it only changes a setting description).
FOG_HOST_IDENTIFY_SMBIOSis set toregister.
Test (two Proxmox VMs)
We moved the MAC of an already registered host onto a different machine. The machine with the different serial was not taken for the registered host: it booted as unregistered and registered as a new host, and the original host kept its MAC. Exactly the shared USB adapter case from this thread.
Real laptops with the shared adapter are the next step, and I’ll report back if anything behaves differently. We’ll switch to the stable release on December 11.
Thanks, Tom, this solves our problem.
-
RE: Feature request: a way to handle USB Ethernet adapters shared between many hostsposted in Feature Request
Thanks for #2104. The case that is still open for us is PXE registration and the PXE menu.
A new laptop (not in FOG) boots through the shared USB adapter whose MAC is still on another host Y. Its firmware matches no host, so FOG falls back to the MAC and answers “This machine already registered as Y”.
Could the identification order be simply this? Always check UUID and serial first. Use the MAC only when the machine reports no usable firmware data (empty or placeholder values). If it does report firmware data and it matches no host, it is a new machine: offer registration, without moving any MAC and without giving the new host the adapter’s MAC.
It could be a new value of
FOG_HOST_IDENTIFY_SMBIOSsoenforcestays as it is.We understand that iPXE already sends the UUID and serial numbers with every PXE request (
sysuuid,sysserial,mbserial), also when booting through a USB adapter, since the firmware is read from the laptop and not from the NIC. Please correct us if that is wrong for registration.In our case the laptops that boot only through a USB adapter are recent and always report UUID and serial.
Happy to test a patch.
-
RE: Feature request: a way to handle USB Ethernet adapters shared between many hostsposted in Feature Request
@Tom-Elliott Thanks a lot Tom, that was fast.
I’m still on 1.6.0.14, and I couldn’t apply #2104 by hand like I did with #2100: it patches
MachineIdentity.php, which doesn’t exist in my version, and the change inEnrollment.phpcalls it. So I’ll wait for the update instead. Do you know which stable release is expected to include it?I’ll also run a full inventory on the hosts that share an adapter, as you suggest, so they have a serial stored. And I’ll report back once I’ve tried it with real laptops.
-
RE: Feature request: a way to handle USB Ethernet adapters shared between many hostsposted in Feature Request
@Tom-Elliott Thanks a lot, Tom. I tested it today on 1.6.0.14, with the two files from PR #2100 applied by hand (
SmbiosIdentity.phpandIpxeBootMenu.php) andFOG_HOST_IDENTIFY_SMBIOSset toenforce.I used two Proxmox VMs, both already registered, each with its own UUID. I gave one of them the MAC of the other and booted it by PXE. The menu said
Host is registered as bios-test!, which is the right one, and the log shows what happened:FOG host identity (enforce): MAC resolved "uefi-test" (id 658); SMBIOS resolved "bios-test" (id 659) on sysuuid=795efc04-...; SMBIOS winsBoth inventories were left alone and the MAC stayed on the first host. Without the patch the same thing overwrote the UUID of the host that owned the MAC, as you described.
I also hit the gap you mentioned, with a machine FOG did not know yet. Before registering the second VM I gave it the MAC of the first, and FOG took it for the first host. The agent did the same: the enrollment request of the second VM got attached to the first host (reason
known-host-no-agent). I don’t know if that last part is worth a look on your side.I have only tested VMs so far. The real case is a few laptops that share one USB adapter,