Zip extraction time is too long before setup.exe is called.
I have my Adobe Reader XI customized and packed in a zip and deployed to my test boxes. One works great, the other being a few years older takes too long to extract.
I have the script set to wait for startup, which does seem to pause it some opposed to not having it checked instantly fails. The error I get is the (XP Setup) Please go to the control panel to install and configure system components.
I'm using $(KACE_DEPENDENCY_DIR)\setup.exe in my script, so other than timing, I'm not sure why else it would look to XP's path that finds the System32\setup.exe.
So other than uploading several dependency files, I'm not sure of a way to pause longer. I suppose I could add the setup.exe outside the zip but boy what a PIA!
BTW, running the extracted setup.exe installs the package correctly, but looking at the $(KACE_DEPENDENCY_DIR) there are no files extracted after kace deploys it.
I'm using 7-zip to archive the zip using Maximum not Ultra for the compression level as I have found systems without 7-zip cannot handle Ultra. Will try Normal compression level next.
Update: Normal compression did not work it out.
Answers (2)
Verify Verify the process “AcroRd32.exe†is not running. Unzip “$(KACE_DEPENDENCY_DIR)\AdobeReader11.0.01-Silent-Installer.zip†to “$(KACE_DEPENDENCY_DIR)â€. Verify that the file “$(KACE_DEPENDENCY_DIR)\setup.exe†exists. Didn't notice the Unzip option available in Verify! So naturally I also made sure setup.exe was ready to roll too.
Verify
- Verify the process “AcroRd32.exe” is not running.
- Unzip “$(KACE_DEPENDENCY_DIR)\AdobeReader11.0.01-Silent-Installer.zip” to “$(KACE_DEPENDENCY_DIR)”.
- Verify that the file “$(KACE_DEPENDENCY_DIR)\setup.exe” exists.
I'm using Managed Installs with Adobe Acrobat XI (haven't updated reader yet) and I'm not having any problems. Just zip up the files and just tell the MI what command to run and it works great.
Comments:
-
For some apps I do use the Managed installs once a lot of dust settles on mass deployments. In my case I have issues needing user involvement to get it deployed using Scripted installs' online notifications.
I don't necessarily need this app to deploy via Scripting, but, I like being able to push via run now instead of forcing 2-3 force inventory's.
I'm not using 5.4 yet so actions to selected PC's may change the way I deploy in the future. - worzie 11 years ago