@Tom-Elliott @george1421 I have someone from Zen support looking at it now. But I am going to assume they find the same issue and tell me to deal with it but we will see. Is there a way to run a .exe then keep going with the .bat? If I can do that then I can make this work.

@Tom-Elliott The log part never worked. I dont think you can make your own log location by the looks of it. I agree with -U it is not needed. The issue I think I have now is 1 the installer is not listening to the augments and 2 because its not listening to augments to goes ahead and reboots before finishing the .bat script and doesnt tell FOG it done.

@george1421 Sorry for long response time. So here is what happens. Run the cmd manually it will run and install but still ask for reboot thus I cant get the echo Exit Code is %errorlevel%. Run the came cmd with FOG it force reboots but doesn’t tell FOG it completed thus it loops installing over and over.

@george1421 Its this. Even when running quietly it still pops this up.

@Sebastian-Roth Its Zenworks 17.4 Agent Updater. Its custom to our environment so not expecting others to have it. I just have never had a plain .exe run and FOG not record it as complete.

Usage: ZenAgentUpdater.x64.17.4.exe <options>

    BUILDTIME <options> are:
      -f <file>    =  add <file> to extractor
      -o <outf>    =  create extractor named <outf>
                      (default is wrapped.exe)

    RUNTIME <options> are:
      -l           =  list contents only (do not extract)
      -n           =  no command execution (extract only)
      -x           =  suppress reboot command passed to ZENPreAgent(Manual Reboot)
      -q           =  show no reboot prompt(quiet install)
      -m           =  have a rebootless agent with limited agent if opting for silent install(-q)
      -Z           =  log ZESM setup.exe installation
      -U           =  force uninstall previous ZENworks Desktop Management agent
      -k <registration key> =  register with the specified registration key after install
      -c <file>    =  custom standalone install file
      -d <dest>    =  extract files to <dest>
                      (default is C:\Windows\novell\zenworks\stage\)
      -A <file>    =  read arguments from file
      -b <component>    =  block installation of component."component" can be a single component or a comma separated list of ZENworks components
                           Supported component names:fde,zesm,asset,policies,bundles,patch,users,imaging
      -K <flags>    =  pass flags to install drivers for component."component" flags need to be passed for ZESM,FDE,FLA,ASD in the given order.Pass 1 to enable drivers and 0 to disable driver installation for the corresponding component
                       For example passing 1110 meaning install drivers for ZESM,ZFDE and FLA but skip driver installation for ASD.

    OTHER <options> are:
      -v           =  be verbose
      -h           =  help (show this message)

hit any key to continue

The install is finishing. I might try the quite switch. But if I just do it with a script FOG completes the task once the script runs I believe. The only issue then is it will keep trying to delete the .exe as it thinks its done but it will be locked.

CentOS Linux 7.7.1908
FOG 1.5.6

Have not had issues running a .exe before but for some reason this one will not tell FOG its done. The .exe runs and reboots apart of the install on a delay of 5mins. It installs and reboots but FOG never gets the message it completed then it runs the install again and reboots and loops.

Do I need to set this as a Snapin Pack and run with a script? Or do I use the Snapin Timeout feature (Never used it before and not much info on it in Wiki)

@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