Packaging UPS WorldShip 10.0
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.
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
Answers (2)
Please log in to answer
Posted by:
rmund2000
12 years ago
Posted by:
jmcfadyen
12 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.