You are a trooper! We certainly appreciate all of your contributions to the FOG project. I agree with @Sebastian-Roth , take some time for yourself buddy. You have been an amazing asset to the FOG project. I don’t know how many times you have bailed me out in the past. Get settled in and get your life in order first. Thank you for making FOG what it is!
Best of luck with your new en-devour!
For those who may come across this same problem…
I updated my BIOS and it resolved the problem.
I figured this one out… I was having problems with security. One of Windows 10’s recent updates (as in the last 3 months or so) was blocking connections to anonymous shares. It allowed them but they needed to be authenticated. For those of you who stumble across this post…
Add your FOG server to your domain and configure Kerberos. After you do this you will need to configure your driver share. I have included the way I did mine and it works. This configuration is for using an existing domain controller. In our case, we use Windows Server 2012 to do domain control.
Do the following:
yum install samba*
yum install krb5-libs krb5-workstation
Confuguration Kerberos /etc/krb5.conf
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
default_realm = YOURDOMAIN
dns_lookup_realm = false
dns_lookup_kdc = false
ticket_lifetime = 24h
renew_lifetime = 7d
forwardable = true
[realms]
DOMAIN.TN = {
kdc = dns-name-your-domain-controller
}
[domain_realm]
netbiosnameyourdoamin = NETBIOSNAMEYOURDOMAIN
netbiosnameyourdomain = NETBIOSNAMETYOURDOMAIN
Configuration samba /etc/samba/smb.conf
[global]
workgroup = DOMAIN
password server = dns-name-your-domain-controller:88
realm = NETBIOSNAMETYOURDOMAIN
security = ads
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/bash
winbind use default domain = false
winbind offline logon = true
log file = /var/log/samba/log.%m
max log size = 50
passdb backend = tdbsam
load printers = yes
cups options = raw
[homes]
comment = Home Directories
browseable = no
writable = yes
[printerdrivers]
comment = All FOG Printers
path = /PATHTODRIVERS
browseable = no
guest ok = no
writable = yes
Add dns name in /etc/hosts
Install and configuration ntp server (It’s important for use Kerborose authorization)
yum install ntpd
edit /etc/ntp.conf
server ip-address-your-ntp-server prefer
Create ticket
kinit account-admin-for-active-directory@NETBIOSNAMETYOURDOMAIN
Add server in domain
net ads join -S dns-name-your-domain-controller -U account-admin-for-active-directory
Create keytab for Kerberos
net ads keytab create -U account-admin-for-active-directory
Edit file /etc/nsswitch.conf
passwd: files winbind
shadow: files winbind
group: files winbind
Restart samba and windind
Test
net ads info
wbinfo -t
Thanks for the advice. We’ll figure it out. I’m sure it’ll be more work but at least we’ll have a clean slate. The good thing is that all of the hosts have been registered with FOG server. So it won’t be as much work as it has been up until now. Plus the multicast issues have been mostly resolved so that’s a plus. Gotta stay positive!
Cheers!
Your suggestion worked!
You might add something to the WIKI to remind those who have passwords on their MYSQL databases to adjust the command accordingly. It took me a minute to figure that out.
mysql --user=FOG_USERNAME --password=YOUR_PASSWORD -D fog
Thanks!
SO… An update to this…
I followed this Technet article and successfully signed my own driver file!
It was quite the process. I’m not an MCSE and prefer my feet in the Linux world. MS makes things so difficult to get done. I ended up having to download the SDK and WDK in order to get this done.
This worked! After I set up the certificate on my local machine and allowed FOG to use the self signed drivers, it installed fine.
SO… Their’s hope that I can get this done using GPO with the article below!
https://technet.microsoft.com/en-us/library/dd919238(v=ws.10).aspx
If you do this, you have to download the SDK package for your version of Windows Server… Why they can’t just package all of these things in Windows Server is beyond me!
Ugh! MS… Can’t live with them… Can’t live without them!
Thank you again!!!
Cheers!
Joe
I was recently asked to give a presentation on FOG by one of the State tech groups (in education) I am involved with in Montana. We have a strong Linux / Mac community here. They are very open source driven and many of the districts here use FOG. Many would like to make the jump into FOG but haven’t taken the leap. I may end up giving a talk here this summer.
I like the idea of setting up a server on a VM. Creating a host image and pushing said image to a new host.
Off topic – At a recent event one of the presenters did a presentation on PFSense. He actually set things up from the ground up. That’s how the conversation arose for me to do the same thing but only with FOG at the State conference.
Good luck!
@george1421
The image transfer is complete!
I had to touch the .mntcheck file to the /images and /images/dev directory. But other than that, I’m up and rolling again! Woo Whooo!
I can’t wait to start fresh with Debian and clean up my server a bit. That’ll be next month’s project!!
Thanks everyone who’s contributed!! I appreciate all the advice! 
Cheers,
Joe Gill
Townsend K-12 Schools
@Joe-Gill said in FOG service quits running:
So I rebooted two different machines that were having this problem. The service restarted on one and not the other. Ha!
Thanks!
I checked the update settings on the machine that the service wasn’t running after the reboot… You guessed it, a Windows Update was running (installing). I’m gussing that is the caust of this entire issue.
Reboot will likely resolve it after the update install is completed. Hope this helps someone else down the road.
Add host name next to Host Management on all pages for Host.
Not a huge deal but it would be handy. I noticed myself having to double check where I was, when I was sending images to hosts.
My idea would be:
“Host Management - HOSTNAME”
or
“Host Management”
“Current Host: Hostname”
You guys are awesome! Thanks!!!
Sounds great! Like I said, let me know what you all are working on and I’ll do my best. I do have some background in programming but it’s been a bit. I am trying to pick up Python and do a little teaching here at our district.
I worked in UNIX for a couple years at one of my first computer jobs. They hired me because I liked tinkering in Linux. I’ve used Linux since the first iterations of Redhat. 
The FOG project does draw you in. It’s a great thing. Some of us can’t afford to throw cash at it but certainly am willing to donate time.
So keep me posted! Thanks!
Well I am currently running version RC-8. I am still having the rolling reboot issue with one of my images. I am deploying a new image this morning on a few remaining machines. I’m wondering if it’s not my image instead of FOG. In the image I’m deploying this morning I have changed the order in which the SetupComplete finishes. I was having SetupComplete install AV first and then do some other tasks… What I failed to realize is that this causes the machine to reboot before the script finishes and it does not let FOG finish. I had a similar issue with snapins not finishing because of a reboot. If the new image seems to resolve this, I’ll be sure to let you all know.
Thanks for all of the support!
Cheers,
Joe Gill
I just checked the boards yesterday to see if anything new was going on with FOG. You answered my question.
Thanks for all of your hard work @Tom-Elliott !
I thought it would be awesome if their was a feature that allowed a user to copy the entire printer in fog to a new printer. It would save many key strokes when creating new printers with the exact same drivers but with different IP addresses. Just a thought.
Thanks guys! You are awesome!
Cheers,
Joe
@Wayne-Workman
@Tom-Elliott
@Developers
The new image seems to work flawlessly, like it should! I’ll have to adjust my script on the other image and go from there. I’m glad I finally managed to figure this one out.
You can change this one to solved!
Cheers!
I’m in the middle of putting every PC in our district into our FOG server and one thing I find myself having to do manually is shutdown each host manually after registration. I know not everyone may be interested in this but adding a prompt to do so would be amazing.
Just an idea!
Thanks!
Cheers,
Joe
So I was trying to debug a script this evening and discovered this…(Look at screenshot below) I find it scary and comical at the same time. All I have to say is “WOW”! This mess is more screwed up than I thought!!!
For those looking for a good script to remove computers from your domain from one single script, look no further…
Check this link out – >
http://blog.the-it-blog.co.uk/2013/08/01/how-to-remove-a-pc-from-a-domain-and-join-it-using-powershell/
I will warn you, I had some bugs to work through. Most will be very simple for you to figure out.
What killed my script was what’s pictured below. When you have ip addresses on your network that represent several different machine names you have bigger issues… UGH!
I did find several variations of this script. Most were written to be ran on your local admin PC. This one is nice because you can create a CSV file of PC names to be removed. Their is also a script on this page to re-add the machines. Both are handy to have!
Anyhow, check out my misfortune. LOL!
@george1421 I’m getting closer! Rebuilding my images directory now on the Server from the Node. Then I’ll make the switch to set the Server to master node.
Then I’ll try MultiCasting and update this post!
Thanks everyone for the support!
It would be really nice if the snapin logs on the server showed which hosts that it was being pushed to. Also it would be nice to have a feature to limit which snapins that were included in the log.
An example of this would be…
Set the date range…
Set which snap-ins you would like to include in the report…
Set whether or not to display host names…
That way you could see which machines you would need to follow up with.
Thanks as usual!
Cheers,
Joe Gill