Topics created by Greg Plamondon

@Greg-Plamondon Try these queries:

Get a list of (unique) host IDs where username logged in to:

SELECT DISTINCT utHostID FROM userTracking WHERE utUserName LIKE '%username%';

Now combine this query to get the list of hostnames as well:

SELECT hostID,hostName FROM hosts WHERE hostID IN (SELECT DISTINCT utHostID FROM userTracking WHERE utUserName LIKE '%username%');

Be aware that the first query might return more results than the later one because older user tracking entries will still exist even if you delete a host from your database. In that case the later query won’t return this host.

@greg-plamondon What is your end goal for this fog server?

How many computers will have the fog client installed on them that will hit this FOG-Pi server?

@Greg-Plamondon Sorry for the really long delay. Hope you got this solved!

Just for the record, fog-client auto registration currently works (FOG 1.5.9.200 - fog-client 0.12.2) and I don’t think it was broken in the versions you have.

@greg-plamondon Rejoice too early! Tried to replicate the issue with SubnetGroup plugin installed at first because from the code it looked like this could be it. But exit type settings stayed. Also made the iPXE hidden but same result. Then installed HostStatus plugin but again exit type settings don’t get reset.

I am wondering if it’s possible this was due to an issue in the database that was cleaned out by removing those plugins?!

I see you have used the FOG 1.6.0-alpha version as well. Is this on a different server or do you switch between 1.5.x and 1.6.x on the same server?

@Greg-Plamondon Oh yeah, good point! Block size can be an issue when you connect across routers with different MTU configured.

@gandzioreek said in Boot Porteus Kiosk iso from fog pxe menu:

I tried, didn’t worked

What didn’t work? What did you see?

While this thread is 2 years old, I just looked at the Porteus Kiosk iso image again, and it looks pretty much the same, so the menu settings I recommended previously should still work.

If it wasn’t for the details most things would work right out of the box.

@greg-plamondon Should be fixed in latest.

Thank you,

@Greg-Plamondon Interesting point you have there. You might take a look at the hostSecTime column in hosts table in the database. I am not sure how often this is being updated but it should let you find hosts that have not checked in in a long time.

@sebastian-roth yes I believe that was the case. I don’t remember the record count as I already purged data older than 30 days. I set up a SQL event that runs daily.

DELETE from userTracking WHERE utDate < now() - interval 30 DAY;

I can now run the reports

I figured it out… I must have screwed up some permissions on the web_root so I removed /var/www/html/fog/ and re-installed fog and all is well…

Thanks!

@sebastian-roth Thanks for that, The PC in question was in the pending hosts.
After approving it joined the domain as expected.

@sebastian-roth said in Fog 1.5.9.62 Location problems.:

@Greg-Plamondon Just pushed the fixed 1.5.9.63.

Awsome!
Appreciate your work!

@greg-plamondon yes.

@greg-plamondon That is one of the reasons I set this up, we have some wifi only devices, setting them to default boot to lan just doesn’t work. Also users get confused and or complain about the time it takes for the lan boot. So I set up a custom boot manager and got the best of all worlds.

I did recently accidentally (so sadly not sure how to recreate it) find that the windows boot manager does still have a gui mode. So you could theoretically create this functionality without the use of third party tools. I discovered it when I imaged a computer that had 2 drives. I imaged the nvme in a desktop that had a old spinning drive that still had a windows install on it and windows saw the old spinning drive’s install first and kept booting to that. At some point I had a windows boot menu that showed both windows options. So there is still a way to add custom boot entries to the windows boot manager. Probably a mix of enabling the timeout in bcd bootmgr settings and then adding a custom boot option. So you could theoretically make it so you see an option for straight windows boot and straight fog ipxe.efi file boot. Personally I like using grub, but just wanted to let people know it’s an option someone could try to figure out.

@Greg-Plamondon said in REQUEST: UltraVNC connect to client pc via fog interface...:

No, I just get a white page. I think that’s trying to use Java.

I realize that this will sound harsh, but if this bit doesn’t work, what the FOG Wizards can do will not matter. Look at your settings you may need to enable the web interface. We use TightVNC in my organization and when I access that page I just got a white page with a link to the tightvnc website. We use the vnc viewer so I don’t know if the web ui was ever configured.

@Tom-Elliott said in Fog V1.5.9.29 Active Directory Defaults for OU not populating Database:

Found and fixed in 1.5.9.34

Thank you,

Thanks!