🙂 🙂 🙂

0_1466584964300_Screen Shot 06-22-16 at 09.42 AM.PNG

@Tom-Elliott Thank you again for your response
This screenshot is from another fog, which is 100% functional.
My fog does not display the network graphic and freeze dashboard.
cordially

Wanting to point out to readers this problem was due to no remote access enabled on the database, and the answer is in the wiki article “Troubleshoot MySQL”.

@moses Possibly just start by re-installing those ssl and cert packages? rpm -qa | grep -e ssl -e cert to find the packages.

Done.
Now I’m at…

Running Version: 8197 SVN Revision: 5726

I can now select a very recent date that a PC was imaged on (6/15/16). However, another PC was just imaged a few hours ago and today’s date doesn’t show up as an option to choose from. Also, now when sitting at the dashboard /var/log/httpd/error_log now continuously scrolls…

PHP Warning: curl_multi_add_handle() expects parameter 1 to be resource, null given in /var/www/html/fog/lib/fog/fogurlrequests.class.php on line 108, referer: https://10.1.10.212/fog/management/index.php

0.32 images would be in partimage format, so you’d set this per image I think in FOG Trunk, or in fog settings somewhere in 1.2.0. I’d suggest as soon as you’re able to download those images, to re-upload them so they are in the new format.

While I still stand by what I’ve already said - just try multicast and see if it works - for same images at once. Stick computers into a group, and initiate multicast from the group.

@Tom-Elliott its no big deal. once this summer is over, adding new hosts gets more rare. It was just this being our first roll out, there will be a lot of machies to touch. All good though, rather have FOG do what it needs correctly instead of me tearing it up.

@Roger-Saffle I’m just guessing that the ca was updated at some point either knowingly or unknown. I’d suggest updating the image that has the 0.9.10 client on it.

I wanted to thank you guys for your help. I updated to the Trunk (version 8179) and its working out just fine, its able to see the new PC’s and can register/image them without any problem. Thanks again.

That seems to have worked!

@adukes40 I guess if I was more on top of my game tonight, I’d have seen the 500 page and said to look at the Apache Error logs, and I imagine we would see some errors about memory being exhausted… I’m glad you figured it out.

Sorry to bring this up again, but having the same issue. Different fog server however. using build 8179.

I created a small group of hosts ~25 and went to the group page, checked the box and it didn’t autofill the form, thought OK, remembering this thread that didn’t necessarily matter. Then went to a host and saw the box was checked to join and the old information that was in there was now gone. I then tried to update the individual host by clearing the fields and hitting the join box, still didn’t autofill, checked the defaults in Settings and that was still there and correct. I believe this was working on SVN5675.

Browser is Chrome 51. (Now that I think about it I think my chrome updated last week sometime)(perhaps chrome issue?)
Tried MS Edge, Works as expected.

Can someone verify my results?

@9intelligence cool.

@dmoseley What’s typically happening if the fog client is running, is that during the OOBE setup the fog client may do an unscheduled reboot which kind of whacks the OOBE setup. Starting the service at the end of the setupcomplete.cmd makes sure that windows is fully setup before the fog client connects the device to AD or renames the computer.

Ubuntu 16.04?

@Tom-Elliott Thanks very much for the quick response Tom, I figured that was the case. So there’s no way to specify a next-choice pxe option (like chaining another server), just using something from “Exit to Hard Drive Type”?

Yes, sorry, we are on Fog version 1.2. Yes, I want to display the “Full Inventory and Registration” task for all Hosts registered or otherwise in the PXE menu.

Our naming convention is Buildingname-room-systemnumber,

example would be ZES-204-S-01

You guys are awesome!!!
OK, So here is what was happening.
WDS was still running on an old server (I am trying to decommission but it has our lunchroom software)
Stopped WDS and Boom!!! Now I have PXE boot.
I still have to move my datastores for image locations but now can at least boot into PXE.
Lots of tweaking and I am sure questions. But I feel I am moving in the correct direction.
Thanks!
Rob
Please mark as closed.

@Sebastian-Roth Updated to fail in the case we can’t create the mount directory OR the partition cannot be mounted. Because I write the data to a log, I am also able to output the “reasoning” behind the failure too to try to help people hone in on the issue.