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! :D
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!
I’d love to help out where I can. I’m not really a Windows guy. I’m more of a UNIX / Linux guy stuck in a Windows world. But I can certainly test things in my lab. I have a couple labs that get used very little that would offer a good test bed for features in the field.
Let me know what types of things you all need help with and I’ll see where my skillset works best.
Let me know how I can help. I have a lab that gets used very infrequently that I can test things on if need be. (Time permitting…) My time begins to get more free here in about a month or two and then gets more busy again in February. I’d be more than happy to help out the project!
@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.
So I rebooted two different machines that were having this problem. The service restarted on one and not the other. Ha!
Thanks!
I will try a reboot on the machine I had quit checking in yesterday and see.
I just noticed something… While looking for log files again this morning… I had one machine that the service literally quit working yesterday… My event logs show events just AFTER the FOG service quit logging…
This machine is on Windows 10 1709 build 16299.15…
Guess what happened after that? Windows ran an update!
We do all of our updates from a Windows WSUS…
Hopefully this helps!!
Here is the entire FOG log on one of the 8/20/19 machines. I can post it as code too if you’d like it. I just thought a log file may be simpler.
Thanks!
@Sebastian-Roth said in FOG service quits running:
Thanks heaps for looking into it. Do I get this right, most of the machines having the issue showed (in the logs) the service stopped working on the very same day, all on 8/20/19??
Not a problem! I am happy to help out the project. The service quit on a handful of machines on 8/20/19 and some were in July.
So far all of my logs are not showing anything back when the problem occurred.
So the event logs go back to that date but there is no notice/warning/error in the event logs?
The event logs don’t go back far enough to show anything. In other words the event logs don’t start until after the service quit working (days later).
I have noticed that a commonality in the FOG logs is that this issue happens after FOG sleeps or reboots.
Do you mean PC reboot? Can you post an example log when it seems to happen on “reboot”?
I’ll go grab an entire log and post it here.
Alright, I have a bit of info to share here…
I have a machine with Windows 10 1709 OS Build 16299.15 and an identical machine (sitting next to it) that has Windows 10 1703 Build 15063.0. The 1709 machine FOG service is not running. The 1703 FOG service IS running.
I checked multiple machines and none seem to have logs that go back far enough to any events that happened on the day the service quit. That said the things these all have in common (on some machines) occurred two days prior to a system update. (8/20/19) The update occurred on 8/22/19… I had a few outliers that happened mid July.
Oddly enough, I was out of the office the week (8/19/19) this event occurred. I checked with the other tech and we had no physical issues that day and the folks that were here used this very lab that day.
So far all of my logs are not showing anything back when the problem occurred. I have noticed that a commonality in the FOG logs is that this issue happens after FOG sleeps or reboots.
Let me know what else I can provide you. I have several machines in the same lab that have this issue. I had a few that after I logged into AD, the service checked in and everything seems to be working.
Cheers,
Joe