@Tom-Elliott Apologies for taking so long to make this reply.

The login history report now runs, but it is not giving any useful information. Steps to replicate (this is using rc8):

Go to Report Manager > Login History Enter username and hostname, then click ‘Search’. Things start to get weird here. A table appears with two columns: one labeled ‘Host/User name’; the second labeled ‘Username’. The first column is filled with the hostname entered in step 2, while the second column is empty. Click on the first instance of the hostname in the ‘Host/User name’ column. Enter a date range and click ‘Search’. At this point I get a message saying ‘No results found’. I get this regardless of what date range I choose.

Now, if I go to Host Management > List all hosts > hostname > Login History, then the report DOES show the correct history for any date I choose.

Confirmed working at home.

@Thiago I’ve been working on the SnapinPacks wiki article, it may interest you seeing that you have 30-some-odd things that need deployed. Perhaps you can contribute your notes if you give SnapinPacks a shot?
https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks

@Wayne-Workman If I remember correctly there was an issue that @Tom-Elliott found in the current iPXE code. Well not exactly in the code but we saw issues with binaries compiled with a later version. Tom and I talked about git-bisect-ing to find out what exactly is the problem. Unfortunately this would take a little bit of time - although not too much. It’s not too much of trouble if you have a device that hangs on that issue (is it only the surface devices or others as well??) and a couple of hours to bisect from the known working version up to current.

Anyone keen to do this? I should be able to do the bisect-ing and provide the binaries. Who is willing to test?

Fixed in RC-9. Thanks for reporting.

https://github.com/FOGProject/fogproject/commit/087d398211a881fd1ebf0dad52eae7387b44e9bd

@Tom-Elliott Hi - I just ran into the same problem. I’ll go ahead disable ipv6 but thought I’d let you know the development installer grabbed from github still seems to try to include ipv6 in fog.conf

@Wayne-Workman There was a laptop with secondary mac adress identical to another laptop pirmary mac adress

@Wayne-Workman That’s something that I’d considered but what gets me is that the drop down loads appropriately on the “List All Hosts” page. I haven’t taken a look to be certain but I’d guess that the code is the same for both pages for that part so the fact that it works on one for me and not the other would seem to indicate a bug that I’m hitting due to some edge or corner case.

Actually, What I thought was fog was this: https://social.technet.microsoft.com/Forums/en-US/030ee94a-047d-460a-bc39-52351a199364/kb3163912-breaks-point-and-print-restrictions-gpo-settings?forum=winserverGP

This “Package Aware” drivers problem was causing my headaches.

I had to republish rc 8 which pushed svn up one but I did not update the svn version because it would not have matched git. This is to be fixed when rc 9 is released.

@syschuck But I can guarantee the comment is done with a ‘#’ anyway.

Unless the files are not interchangable.

Just to help clarify, basically it was filtering the array out. Because there was only two tasks, and one of them was invalid, it was not defining the tasks as an array.

Just to help clarify, basically it was filtering the array out. Because there was only two tasks, and one of them was invalid, it was not defining the tasks as an array.

@apathetic_admin said in RC-1 Hosts Disappear When a New Host is Added:

It appears that the old host data is still in the database, so I’m not really sure where to go from here, if I should just suck it up or if maybe we can get it back.

I’ve not seen this. I’ve only heard of one other case of this, but it was during a time when the DB was plagued with all sorts of issues (because of my coding having some error or another).

This should not have happened to begin with, but it’s not something that’s a common occurrence and if it were, I’m sure it would’ve been posted all up and down the forums by now.

@Joe-Schmitt Thinking of it that way I see your point. I hadn’t considered the malicious halting but now that you mention it I could see that being a major issue. I withdraw my request/suggestion on this one. Thanks for the time to explain your thinking.

Neither of these two things are bugs in the sense that FOG is not capable of fixing them.

For UEFI boot, the escape key sequences aren’t built into iPXE. The only key sequence that is is the ESC key which is why it defaults to it.

The rEFInd config is default from the source itself, and it’s designed to allow you to configure your own needs as needed. While I could create a better config, it’s still very dependent on your own environment.

Fixed for RC-9

@Wayne-Workman I think the wake-up task must be delivered anyway. This poses no problem to simply start a station while another task is pending or in progress.

This is why the Debugger was made. Note that there is a bug in the Debugger starting at 0.11.0 with exiting so for the below instructions please use the one from 0.10.6 (https://github.com/FOGProject/fog-client/releases/download/0.10.6/Debugger.exe)

Make a snapin with the following settings:

Snapin File: Debugger.exe Snapin Arguments: user list > C:\user-dump.txt

Deploy this snapin on a problematic host. A listing of the logged in users will be in C:\user-dump.txt.