@Tom-Elliott

Updating to version 7785 seemed to do the trick. Webacces is now full functional. Moving on to the next problem.

Thank you all SO SO much for your help 🙂

Remoted in and was able to find a way to properly operate around the issues.

@Tom Elliott

Hi,
Thanks for your quick answer.
you are completely right, as always
I have updated the server to 7779 version

Have a good day

@Sebastian-Roth I stand corrected after a long day of typing.

I really do know the difference between iPXE kernels and linux kernels even though my fingers lie once and a while.

Update fog.

@george1421 Yea I tried to do the fdisk thing and also thought it was scary so stopped before I could do any damage. I might try again because I have a snapshot of the server so If I do anything I can just revert to the snapshot. I just wanted to be pointed in the right direction before I put time into it. I’m reading the first article you posted and if that doesn’t work I will try using fdisk. Thank you for replying, I’ll let you know what happens 🙂

@chetansays

If you want to disable globally
FOG Configurations->FOG Settings->FOG Client - XXXXXXX
For now just disable all FOG Client sections individually

Or you can do on a host by host basis (probably what you want for this test)
Host Management -> List all Hosts -> {Select your host}
Then from the left menu select Service Settings and then uncheck all under service configuraiton.

@tmerrick I’m making an implicit check for the interface based on the ip stored for the node.

Can you just run update.

It can yes. I was using the easy method of eliminating one possibility before I dug deeper.

@george1421 UPDATE: I followed your instructions and I got my system to work exactly how I wanted it too. I really appreciate the help. Thanks again.

Unfortunately I ran into a small hiccup during the deployment process. You’ll see the post soon once I get the photo uploaded haha.

@Tumulus You’re fine, FOG runs on Ubuntu 16 just fine. You simply run the installer as tom said, and everything is just-fine.

@Julianh It’s also worth noting that the remaining two didn’t need turned off. They would have began imaging when a slot opened. I limit my FOG server’s maximum connections to 2, and I image 50 to 60 computers at once. 2 go, the rest wait in line.

@Tom-Elliott

--------------------------------PrinterManager-------------------------------- 5/19/2016 10:24 AM Client-Info Client Version: 0.10.6
5/19/2016 10:24 AM Client-Info Client OS: Windows
5/19/2016 10:24 AM Client-Info Server Version: 7717
5/19/2016 10:24 AM Middleware::Response Success
5/19/2016 10:24 AM Service ERROR: Unable to run module
5/19/2016 10:24 AM Service ERROR: Object reference not set to an instance of an object.

@Quazz Hi, thank you i could fix the problem it was really an access problem, right for everyone was missing, i broke the share and inherited everyone for only that folder and now it works. Great 🙂

Works again after updating to svn 7713

@Sebastian-Roth

That’s kind of odd from my point of view as the tools used to do the actual up- and download (udp-sender for multicast download and NFS for upload and unicast download) haven’t changed much in a while!

we’ve made changes to how compression/decompression is handled to better utilize the processing power available

@Junkhacker
Thanks again!

@Sebastian-Roth I agree. But I also don’t have access to my building’s switches to fix multicast.

@TreyBentley if you have any trouble with resolving fog kernel panics, just start a new thread and we’ll help you out.