#Efax messenger x64 install#
So the new sequence ended up being -Ĭompiled EXE uses psexec to run a second batch file as local admin -> second batch file kills explorer, restarts it as local admin, kills it again -> calls install routine -> calls system restart.
By having the script being run as local admin end the explorer process then restart it as itself, the profile is in essence created and the install can go through without issue. I guess it helps to just empty everything out sometimes to get a fresh look at the problem. I'm at my wits end, hoping someone has seen/dealt with this before. A registry error comes up referencing "HKLM\SOFTWARE\Microsoft\CTF\KnownClasses" with the result "NAME NOT FOUND"Īnybody have any idea what may be causing the application to throw this error or what it might be looking for that's only created once the local admin has logged into the computer once? The application is built on top of "Advanced Installer" if that's at all helpful or anyone has experience with it. Watching the install with Procmon, trying to catch what it's failing with. Manually creating and importing the HKCU\Volatile Environment key with the entries created when a valid logon by admin is done (Same error) This works absolutely fine if the administrator user has logged into the computer at least once.Įditing the MSI with Orca to remove/change the %USERPROFILE variable to a static location (MSI completely fails) I'm assuming as the local admin hasn't logged in, there's a registry entry or folder path that's not being created and thus the failure. This whole kludgey process works with one caveat - if the local admin has never logged into the computer before the process fails - the MSI throwing an error "Could not access network location \My Documents\eFax Messenger 4.4" Start "" "C:\Program Files (x86)\eFax Messenger 4.4\J2GTray.exe" Reg import c:\users\%1\AppData\Local\Temp\圆4.reg Start "" "C:\Program Files\eFax Messenger 4.4\J2GTray.exe" Reg import c:\users\%1\AppData\Local\Temp\x32.reg
Reg Query "HKLM\Hardware\Description\System\CentralProcessor\0" | find /i "x86" > NUL & set OSver=32BIT || set OSver=64BITĬ:\users\%1\AppData\Local\Temp\msgrplus.exe /exelang 1033 /qn Logon Script EXE calls efax_installer.bat as local computer admin offĮcho Installing eFax Messenger - Please wait. %temp%\psexec.exe -accepteula -u administrator -p PasswordHere "%temp%\efax_installer.bat" %username% Reg Query "HKLM\Hardware\Description\System\CentralProcessor\0" | find /i "x86" > NUL & set OSOSver=32BIT || set OSver=64BITĭir "c:\Program Files (x86)\eFax Messenger 4.4" >nulĭir "c:\Program Files\eFax Messenger 4.4" >nulĬopy \\\sysvol\\scripts\MSI\eFaxMessenger\*.* %temp% User Logon Script (compiled to an encrypted EXE to hide the password) off That's why what I'm about to detail below looks so out of whack. so using my phone a friend.Īpp can't be installed to all users, whether via executable or MSI extracted from MSI. I've been banging my head against this for a few weeks and at wits end. I have an app ( eFax Messenger) that I'm trying to work out a method to deploy via group policy.
0 kommentar(er)
