@Sebastian-Roth I have no way of knowing any of that hence the powershell script. What I want is to get a script that does all that FOG users need. Check to see if service is installed, if not Install. Check to see if FOG is broken, I currently look at the FOG.log date. If the date is over 14 days old then its broken, uninstall reinstall. Now I want to read the FOG.log file and key in on something to tell me its broke “Unhandled exception caught” or “Log Hash code” seem like good options. If we get this script to just record info then I can start narrowing down the info your are asking for. We usually dont deploy many snapins post imaging.

My skills in powershell are not amazing so was thinking of colaborating with the FOG community and r/Powershell to get us a good script that others can deploy to their networks to maintain FOG. I plan to add this script to a daily maintence script.

CentOS Linux 7.5.1804
FOG 1.5.6

I have a lot of clients with FOG.logs like this. Is there any way to fix this other than uninstall reinstall? If not could we get some powershell people together to write a script to uninstall reinstall if it finds log files like this?

 11/20/2019 4:39 PM Service Starting service
 11/20/2019 4:39 PM Log Unhandled exception caught
 11/20/2019 4:39 PM Log     Terminating: True
 11/20/2019 4:39 PM Log     Hash code: 63835064
 11/20/2019 7:44 PM Main Overriding exception handling
 11/20/2019 7:44 PM Main Bootstrapping Zazzles
 11/20/2019 7:44 PM Controller Initialize
 11/20/2019 7:44 PM Controller Start

 11/20/2019 7:44 PM Service Starting service
 11/20/2019 7:44 PM Log Unhandled exception caught
 11/20/2019 7:44 PM Log     Terminating: True
 11/20/2019 7:44 PM Log     Hash code: 63835064
 11/20/2019 7:45 PM Main Overriding exception handling
 11/20/2019 7:45 PM Main Bootstrapping Zazzles
 11/20/2019 7:45 PM Controller Initialize
 11/20/2019 7:45 PM Controller Start

 11/20/2019 7:45 PM Service Starting service
 11/20/2019 7:45 PM Log Unhandled exception caught
 11/20/2019 7:45 PM Log     Terminating: True
 11/20/2019 7:45 PM Log     Hash code: 63835064
 11/20/2019 7:46 PM Main Overriding exception handling
 11/20/2019 7:46 PM Main Bootstrapping Zazzles
 11/20/2019 7:46 PM Controller Initialize
 11/20/2019 7:46 PM Controller Start

 11/20/2019 7:46 PM Service Starting service
 11/20/2019 7:46 PM Log Unhandled exception caught
 11/20/2019 7:46 PM Log     Terminating: True
 11/20/2019 7:46 PM Log     Hash code: 63835064
 11/24/2019 5:13 PM Main Overriding exception handling
 11/24/2019 5:13 PM Main Bootstrapping Zazzles
 11/24/2019 5:13 PM Controller Initialize
 11/24/2019 5:13 PM Controller Start

 11/24/2019 5:13 PM Service Starting service
 11/24/2019 5:13 PM Log Unhandled exception caught
 11/24/2019 5:13 PM Log     Terminating: True
 11/24/2019 5:13 PM Log     Hash code: 63835064
 11/25/2019 8:47 AM Main Overriding exception handling
 11/25/2019 8:47 AM Main Bootstrapping Zazzles
 11/25/2019 8:47 AM Controller Initialize
 11/25/2019 8:47 AM Controller Start

 11/25/2019 8:47 AM Service Starting service
 11/25/2019 8:47 AM Log Unhandled exception caught
 11/25/2019 8:47 AM Log     Terminating: True
 11/25/2019 8:47 AM Log     Hash code: 63835064
 11/25/2019 8:48 AM Main Overriding exception handling
 11/25/2019 8:48 AM Main Bootstrapping Zazzles
 11/25/2019 8:48 AM Controller Initialize
 11/25/2019 8:48 AM Controller Start

 11/25/2019 8:48 AM Service Starting service
 11/25/2019 8:48 AM Log Unhandled exception caught
 11/25/2019 8:48 AM Log     Terminating: True
 11/25/2019 8:48 AM Log     Hash code: 63835064
 11/25/2019 9:14 AM Main Overriding exception handling
 11/25/2019 9:14 AM Main Bootstrapping Zazzles
 11/25/2019 9:14 AM Controller Initialize
 11/25/2019 9:14 AM Controller Start

 11/25/2019 9:14 AM Service Starting service
 11/25/2019 9:14 AM Log Unhandled exception caught
 11/25/2019 9:14 AM Log     Terminating: True
 11/25/2019 9:14 AM Log     Hash code: 63835064

@Tom-Elliott Thank you for figure this out. Here is the correct query.

Insert into groupMembers (gmHostID,gmGroupID) Select hostID,'212' from hosts where Right(hostName,6) in ('D02595','110563')

@Daniel-Miller No, I typed in 212. I could get it from another table with another where statement. I think that is the issue.

Ok so it has to be the gmGroupID. It doesnt like me just plain texting it. I am able to run this

INSERT INTO groupMembers
(gmHostID, gmGroupID)
VALUES
(8928, 212)

Error Code: 1064. You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ’ VALUES (‘hostID’,‘212’) SELECT hostID,212 FROM hosts WHERE Right(hosts.hos’ at line 1

So was working with my SQL admin and got this narrowed down to the following. Yet I am still getting a error on my insert statement. What are we missing? 212 is the group ID. Those values I am querying are the asset tags of our machines but would also like to query the whole host names if possible but from what I heard I cant do a in and like statement. My select statement works perfectly.

Insert Into groupMembers (gmHostID, gmGroupID) 
SELECT hostID,212 FROM `hosts` 

WHERE Right(hosts.hostName,6) in ('D02595','110563','110687','110570','110592','111045','111050','111064','111071','96643','D02320','111921','111914','111916','110076','-98264','103070','111846','111842','111840','111459','111470','111471','111463','111437','103636','103638','103639','-97871')

So this can get marked as resolved. Everything worked as expected except when you update the nodes the GUI did not show the new version until after we updated the Master. All the issues we had with 1.5.4 were resolved with 1.5.6. Very happy with this update.

GUI is super fast!
The freezing on formating MBR/GPT on start of imaging is back to only a few seconds. Replication seems to be acting normal again.

@Sebastian-Roth Yes I had already had it disabled.

I tested that node and it still deploys image so my guess is its a glitch in the GUI until we update the master node.