Hi,
I have a fixlet that is supposed to install an application (pretty easy). The task that runs this fixlet completes successfully, but the application doesn’t install. If I were to take the command that is in the fixlet and run it interactively on the target computer, it works fine. IEM’s log indicates everything completes successfully, still no application actually gets installed and the target computer is still relevant to the fixlet.
At 10:29:43 -0400 - mailboxsite (http://iem.company.com:52311/cgi-bin/bfgather.exe/mailboxsite13842724)
Relevant - Software Distribution - Deploy: Maple 2015 64-bit (Classrooms license) (fixlet:84071)
At 10:29:44 -0400 -
ActionLogMessage: (action:84071) Action signature verified for Downloads
At 10:32:07 -0400 -
ActionLogMessage: (action:84071) Non-Distributed - DownloadsAvailable
ActionLogMessage: (action:84071) Action signature verified for Execution
ActionLogMessage: (action:84071) starting action
At 10:32:08 -0400 - actionsite (http://iem.company.com:52311/cgi-bin/bfgather.exe/actionsite)
Command succeeded (Prefetch download manager collected file) prefetch 1aee7edd99e4241ae97fbb44e91b7c2b89bf81d8 sha1:1aee7edd99e4241ae97fbb44e91b7c2b89bf81d8 size:953018196 http://iem.company.com:52311/Uploads/1aee7edd99e4241ae97fbb44e91b7c2b89bf81d8/Maple2015.tmp (action:84071)
At 10:32:17 -0400 - actionsite (http://iem.company.com:52311/cgi-bin/bfgather.exe/actionsite)
Command succeeded extract 1aee7edd99e4241ae97fbb44e91b7c2b89bf81d8 (action:84071)
Command started - wait __Download\Maple20151WindowsX64Installer.exe --optionfile installer.properties --debugtrace “C:\Maple2015Install.txt” (action:84071)
At 10:32:44 -0400 -
Report posted successfully
At 10:32:44 -0400 - actionsite (http://iem.company.com:52311/cgi-bin/bfgather.exe/actionsite)
Command succeeded (Exit Code=1) wait __Download\Maple20151WindowsX64Installer.exe --optionfile installer.properties --debugtrace “C:\Maple2015Install.txt” (action:84071)
At 10:32:44 -0400 -
ActionLogMessage: (action:84071) ending action
At 10:32:44 -0400 - mailboxsite (http://iem.company.com:52311/cgi-bin/bfgather.exe/mailboxsite13842724)
Not Relevant - Software Distribution - Deploy: Maple 2015 64-bit (Classrooms license) (fixlet:84071)
At 10:33:33 -0400 -
Report posted successfully
At 10:42:07 -0400 -
Report posted successfully
How do I get IEM to stop lying and do its job?
thanks
Your working directory when the script runs is probably the root of the custom site and not the download folder so it might be looking for your installer.properties inside of the custom site folder instead of the __Download folder.
Try changing the optionfile parameter to --optionfile “__Download\installer.properties”
1 Like
I’m pretty sure that @strawgate has the correct answer for your problem, but in my experience you often need the absolute path, not the relative path to the file being passed as a parameter. ( the absolute path may not be required in all cases, but it is good practice to always use the absolute path, and you don’t need to know it ahead of time thanks to the relevance below )
Try this:
waithidden __Download\Maple20151WindowsX64Installer.exe --optionfile "{pathname of download file "installer.properties"}" --debugtrace "C:\Maple2015Install.txt"
Also, the reason BigFix/IEM reports success has to do with your success criteria, not if the application actually installed. BigFix/IEM can tell you if it was actually installed or not, but you have to set the applicability relevance in such a way that it is only relevant on machines that do not have it already installed, and then set the success criteria to “applicability relevance evaluates to false”. This is a best practice and you should do it this way for all of your Fixlets and Tasks. If you do not do it this way, then all BigFix/IEM can tell you is if the script ran through without execution errors, which does not mean there were not errors.
See this example: http://bigfix.me/fixlet/details/3827 ( Relevance 2999205 )
1 Like
In addition to the helpful comments from @strawgate and @jgstew, for reference your logfile actually does show where the installer command returned an error result -
At 10:32:44 -0400 - actionsite (http://iem.company.com:52311/cgi-bin/bfgather.exe/actionsite)
Command succeeded (Exit Code=1) wait __Download\Maple20151WindowsX64Installer.exe --optionfile installer.properties --debugtrace "C:\Maple2015Install.txt" (action:84071)
The “Exit Code=1” is the return code provided by WindowsX64Installer.exe. By convention an Exit Code of 0 indicates success, and an other exit code indicates an error (where many products will indicate the type of error based on the number returned). If you were to run this in a Command Prompt, you can see the installer’s return code via
echo %ERRORLEVEL%
1 Like
strawgate’s suggestion worked great. I have also changed the success clause to include “applicability relevance evaluates to false.” The command to install Maple was running, but then immediately exiting when it couldn’t find the unattend file.
many thanks!
1 Like