/build/static/layout/Breadcrumb_cap_w.png
01/09/2019 149 views

A PDF driver that is critical to my company's business processes needs to be updated to be compatible with a new software we are deploying.  The installer for the new PDF driver is essentially broken and calls for a DLL from a much older version of the driver.

To solve this problem, I have a batch file that will silently install the new driver, then silently install the old driver.  Then, the batch file will unregister 6 DLLs (3 from c:\windows\system32 and 3 from c:\windows\syswow64).  Finally, the batch file will register the 3 correct DLLs (2 from c:\windows\system32 and 1 from c:\windows\syswow64).

When the batch file is run locally on a workstation using an elevated command prompt, everything works properly.  The software installs correctly and the DLLs unregister and register properly and my updated software works great.

I have been attempting to push this script via Kace scripts for over a week with no success.  If I disable the silent switches and actually watch the installation, I still do not have success with the DLL registration.  In fact, I will receive the pop-up notification that my action was successful, however, the DLLs do not actually register because my new software does not work correctly.  Again, if I run the batch file locally using an elevated command prompt, the DLLs register properly.

I've tried a staggering number of permutations on this, running as Local System or Local Administrator credentials.

My hunch is that the DLL in the syswow64 is not registering properly because the KACE agent is running as a 32 bit application.  That's just a guess at this point.

Has anyone had success registering DLLs via KACE?  Is there a secret cheat code someone can throw my way?

0 Comments   [ + ] Show comments

Comments


All Answers

0

Could be that the script is running as system and does not work.  Some things require that a user be logged in to run due to temp areas or other things needed that system cannot get to.


I have a couple of scripts that must be run as administrator vs system.  My 1809 upgrade script is an example.  Try setting up credentials in the manager and use those to run the script



Answered 01/10/2019 by: SMal.tmcc
Red Belt