Software Deployment Question

Packaging UPS WorldShip 10.0

08/19/2008 8181 views
A few tips to package UPS WorldShip 10.0 using Wise Package Studio

WorldShip must be split into 2 packages, because their Policy Manager has to install AFTER reboot WITH services running. I know it’s crazy, but that’s the way UPS set it up.
FIRST PACKAGE: I could not wrap it, it had to be a capture. Start capture, start install. When prompted to reboot, stop the capture. Start second capture, allow computer to reboot and complete install. **NOTE** If the computer reboots automatically, you will need to restart the capture on a clean machine. The next time, just start notepad, type a few letters in it, and leave it sit. The computer won't automatically reboot with it open.
Combine the two captures into one script. I found that just doing 1 capture and letting the reboot happen loses some important changes, and it seemed to work better by capturing in parts. The software won't run correctly with some add-ins if you change the default path, so save yourself some frustration and don't change it.
The services installed by this package default to “Start Service – Manual. If you are in a managed environment, change them to “automatic,” or the software will not run.
VERY IMPORTANT when installing on end-user machines -–- install the first package, then force a reboot of the computer
SECOND PACKAGE: It’s a wrap. In the package, run msiexec with the following command line: /qb-! /wait /i “YourSourcePath\PolicyManager.msi ARPSYSTEMCOMPONENT=1 INSTALLDIR="C:\UPS\WSTD" /l*+ "C:\UPS\WSTD\MSI.log" REBOOT=ReallySuppress ALLUSERS=1
When I packaged 9.0, I only had to wrap Policy Manager, but I found that I also had to include Forms Component.msi this time.
That’s it. WorldShip 9.0 took about 6 months to figure out. Worldship 10.0 took about 6 days, with testing and updates, etc. After all of that frustration, it actually ended up relatively easy to do. I just had to find the magic combination to make it work. Here's hoping that others will benefit from this.
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

It's been over 2 years since your last post, but would the same procedure work when packaging the current Worldship 2011 software. We use LANDesk to distribute software. The only attemp I've made is using AdminStudio. But that didn't capture all the necessary files.
Answered 07/14/2011 by: rmund2000
Yellow Belt

i would recommend at mimimum not using command line to specify the properties as these will be dropped during repair states which could possibly cause the delivery of the application to change.
Answered 07/14/2011 by: jmcfadyen
5th Degree Black Belt

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