/build/static/layout/Breadcrumb_cap_w.png

Installation works fine locally, doesn't work when deployed from the K1000

I have an MSI installation that I'm trying to deploy (PowerCampus by Ellucian).  I wrote a batch file to install the software quietly and tested the install locally.  The install went fine, so I zipped up the install files and uploaded it to the KBox.  I then tested the deployment from the KBox to another machine.  That deployment didn't work as it was supposed to.  It copied the files over to the program files folder, but didn't create any shortcuts or put the software into Programs and Features.  After fighting with that for a while, I decided to try another tactic.  I put the installation files out on a network drive and created another batch file to run the installer from that drive.  I tested it locally (ran the batch file from my desktop) and again it worked.  When I tested it from the KBox I recieved an error stating "This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.".  Ok, fine.  So I created an updated another batch script to download the files locally to the machine and run the setup.  Again, all tested fine locally.  When deployed from the KBox, I again am left with no shortcuts or Programs and Features entry.  

I am at the end of my rope.  What I am I missing?

Asked 10 years ago 2891 views
2 Comments   [ + ] Show comments
  • the kace installs as system by default - SMal.tmcc 10 years ago
    • you can run it as a specific user from the network share, just add that to the kscript. - SMal.tmcc 10 years ago
      • Created the kscript. The user it runs as is a domain admin. Had it look for a registry value added by the installer as the verify step (that was I won't run it against systems that already have the software). That step works (verified by running the script against two machines, one with and one without the software installed). The batch file that I then have it run chokes. Here's the batch file:

        mkdir C:\PCInstall
        start /wait xcopy P:\PCInstall\*.* C:\PCInstall /s/y
        start /wait msiexec /i C:\PCInstall\sqlncli_x64.msi /qn
        start /wait msiexec /i C:\PCInstall\powercampus.msi /qr

        It makes the folder fine, and then attempts to execute the first MSI file. Problem is that the folder that was created is empty as line two failed.

        As a test I eliminated line two and had the script run the files directly from the P:\PCInstall\ directory. I then received the "This installation package could not be opened" error again. Any thoughts? - scragman 10 years ago
  • Update:

    I think I've got it. Broke the batch file down into two (making the directory in one and running the apps in another), and made the xcopy a 'launch application' command with the right params. Did a test deploy and it seemed to work. - scragman 10 years ago

Answers (0)

Be the first to answer this question

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ