Topics created by Darrin Enerson

@x23piracy That looks like it might be exactly what we’re experiencing but I have no clue why it would only show up intermittently. I’ll test this out and see if it fixes the issue when I can get it to trigger again. Thanks for the info.

Fixed in RC-9. Thanks for reporting.

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

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

@Tom-Elliott Thanks Tom :). I’ll have a chance to do a confirmation test in my setup sometime next week and let you know if I encounter any issues related to this.

Well it looks like this is definitely a problem with this model of laptop. The Windows 7 Enterprise installer finished copying and expanding all of it’s files and then as soon as the first reboot happens the computer hangs at the same black screen I receive after imaging it. Looks like I’m destined for the HP support line to kick this up the chain for a fix :(.

Edit: I just rebooted without the network cable plugged in and now the installer continued without an issue. More testing needed but maybe an issue with how the FOG boot menu is handing back off to the boot cycle on this model. I’ll update once I’ve done more thorough testing.

Edit 2: The solution for this is that the “Host Bios Exit Type” for this model must be set to “GRUB” or it will hang before the OOBE portion of the Windows install process starts. “SANBOOT” causes this 100% of the time on our units and “EXIT” returns an error. Presumably any of the “GRUB” options would work but I haven’t verified any other than the basic “GRUB” option.

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

@Darrin-Enerson I’ve added the warning and an example method to correct the issue, I think, in a more proper method. This warning will be available for the RC6 (Hopefully it can just be 1.3.0 at that point, but meh.)

Issue confirmed. I was tryign to fix a bad status update in the repo earlier and apparently one of my links ended up in the mix.

I deleted the entire repo and readded what was requried back.

This should be fixed now.

Please re-pull your repo (this only affected git users).