hi , trying to install a Fontagent 10 windows 10 software , i can install it silently with Fixlet Debugger but when i execute it from action script it does not install
does fixlet debugger skip or ignore any UAC permission ?
waithidden cmd.exe /C C:\bestemp\FontAgent_Windows_10\setup.exe /qn - Not working and it does not install software
action uses wow64 redirection false
createfile until EOF
cd C:\bestemp\FontAgent_Windows_10\setup.exe /qn
I see youâre already disabling wow64 redirection, good, thatâs one of the most common issues.
I donât know anything about FontAgent, but perhaps it is a per-user installation. You may need to override the âwaitâ command to run in User context rather than LocalSystem context. I have a post describing those options at Tip - Action Override User settings
Donât think this is accurate execution. It probably needs to be something like:
cd C:\bestemp\FontAgent_Windows_10\ & setup.exe /qn
or C:\bestemp\FontAgent_Windows_10\setup.exe /qn
depending on your intentionsâŚ
Also, donât think the following is right, at least doesnât mention any kind of shorthandedness to be allowed override waithidden=true
According to documentation, you need to specify what you are overriding and then the key-value pair for the behaviour that you want to override.
override <cmd>
<keyword>=<value>
<keyword>=<value>
<cmd> <rest of command-line>
i tried with the below script but still it is blocking msi to run and getting below error message , but when i run it from fixlet debugger it succeeded
try adding cmd.exe to the execution and see if it makes a difference, something like: wait "{pathname of system folder & "\cmd.exe"}" /C "C:\bestemp\FontAgent_Windows_10\install.bat"
i tried but i got same error, it is executing and open a cmd prompt but without runas administrator and that is the main issue i guess , msi is running in normal cmd window
Even when i tried to install msi manual on normal cmd windows does not work but it works only in runas admin cmd window
how to fix runas admin in current user session windows in bigfix ??
i used the below it works but , i canât hardcode the user name as i might not aware which user will be there in the desktop or laptop
override wait
runas=localuser
user=user1
password=required
asadmin=interactive
wait âC:\bestemp\FontAgent_Windows_10\install.batâ
2nd option , but did not work
override wait
runas=localuser
user=administrator
password=required
asadmin=interactive
targetuser=domain\{name of logged on user}
wait "C:\bestemp\FontAgent_Windows_10\install.bat"
@JasonWalker - As i was unable to upload the .log / .txt file so changed the extension to .pdf., please download and change the extension to .txt. so that you can review that file.
It looks as though the software is standard MSI so All Bigfix is really doing is invoking the Windows installer service to process the MSI. A few thoughts.
Calling the MSI directly can fail in some cases if the user has inadvertently assigned the MSI file type to another application. Its safer to call the MSI with misexec.exe to avoid those possible scenarios/
You can call the MSI directly from the action, no need for a batch script., eg wait msiexec.exe /I {path_to_installer.msi} /qn {plus any other MSI options}
Try enabling verbose logging with the msiexec switches, /l*v then review the Windows installer log for possible causes. See msiexec.exe /? for command line options
Does the vendor support an All Users type install via the system. Maybe MSI properties passed on the command line can help force the mode to meet your requirements, eg /ALLUSERS=1
Consider contacting the vendor to seek advise on how to perform installation via enterprise software distribution tools such as, but not limited to, Bigfix.