Requests for Wiki Access <--- ASK HERE
-
This post is deleted! -
This post is deleted! -
This post is deleted! -
This post is deleted! -
@DevinR, @Jason-Rush, @Marcus-Allen, and @Trevelyan I’ve created your wiki accounts. You should receive an email containing a randomly generated password. Once received, you will have to change your passwords. If you’re still having issues, please just let me know.
Thank you, sorry it took so long.
-
This post is deleted! -
This post is deleted! -
-
This post is deleted! -
@mauirixxx By all means, go ahead. There are actually two articles on CentOS7.
https://wiki.fogproject.org/wiki/index.php/Installation_on_CentOS_7_x64_Full_Guide
https://wiki.fogproject.org/wiki/index.php/Installation_on_CentOS_7I know for a fact that CentOS 7 is the very best option for FOG Trunk right now. (and I’m a Fedora kinda Guy)
I will also tell you that the instructions for CentOS 7 are even shorter than the instructions in the Fedora 21 Server article - but use almost exactly the same commands, less in fact.
-
This post is deleted! -
Hi,
I am requesting Wiki access to contribute as I get our company’s site up and running with the Fog Client.
-
Hi, I am requesting access to the wiki to add information as I am deploying fog on Debian.
Thanks!
-
HI,
I am requesting access to the Wiki to change the steps on how to step up Windows DHCP to work with FOG. I am also testing FOG on the latest versions of Debian, Ubuntu and Fedora to see which I like best and I will report here on my finds, when I have free time(hehe) to do so.
-
@iyoung Which DHCP article are you looking at?
-
@Wayne-Workman This article only mentions option 66 and 67, but on Windows Server you also need to enable option 60 through netsh to turn on the PXEClient.
-
@iyoung said:
@Wayne-Workman This article only mentions option 66 and 67, but on Windows Server you also need to enable option 60 through netsh to turn on the PXEClient.
And the User Guide as well.
-
@iyoung Can you explain more about your environment? I ask because I only run Windows DHCP at work and I do not have option 060 set, but network booting works fine here. Other sites in my organization also work fine with just Windows DHCP and options 066 and 067 set. So I’m wondering what it is that your environment needs option 060 for.
-
@Wayne-Workman I have a 2008r2 Domain controler that acts as the DHCP server as well and I have options 66 and 67 set as it shows on guide. My FOG is on Ubuntu 15.04. When my workstations go into network boot, they send out discovery packets but don’t get any packets in response. Looking into it, I found that DHCP option 60 needs to be enabled. I was going to test it on my server here before editing the wiki and to be honest, I didn’t expect such a quick response. I’ll make a post in the correct area of the forum if I need anything farther.
-
@iyoung said:
to be honest, I didn’t expect such a quick response.
That’s how we roll around here.
And understand I’m just trying to figure out why you need this option but I don’t.
Are you in total control of your network equipment? Do you have iphelpers set?
