UPS WorldShip Packaging

I was able to successfully Package this,

Critical Steps include modifying the default settings.ini file in the INSTALLATION_22_0_17_0 source folder and changing

[Threshold]
Hours=1

to

[Threshold]
Hours=100000  ( The Installer compares up time to this and fails if the uptime it greater than the threshold. )

Next Create a silent install ini file and copying it before running the installer.

Example : WS_Silent.ini

[configuration]
Language=ENU
approvelegalagreement = yes
country = US
installtype = standalone
shortcut = no
autolaunchworldship = no

When Creating the Deployment Package Step 1 would be to copy your new WS_Silent.ini file to the target computer in a standard directory. 

I used c:\temp\

( This will not work with a relative path.  ) 

Step 2 would be to install the program stage the INSTALLATION_22_0_17_0 source folder with modified settings.ini file

Select the Setup.exe 

and add extra parameters of  /s /i c:\temp\WS_Silent.ini  /l c:\temp\ups.log 

and check the include Entire Directory

Good Luck everyone !

I realize this thread is more than a year old at this point, but I am unable to get this working. I do not have a default settings.ini file as mentioned in your solution above. I simply have an executable file. Could you possibly post the contents of the ini file?

I am attempting to deploy version 2020 of Worldship and have created the silent install ini file as you listed. Hoping there is a further solution for the remainder. Thanks for your help in advance.

Jason,

Run the WS2020_23_8.exe you downloaded and it will create the Installation directory I usually exit after it extracts the contents and tells me to reboot. 

In the INSTALLATION_23_0_8_0 folder it creates you need to modify the settings.ini file and re-save it.

Next Create the PDQ Package around the setup.exe in the INSTALLATION_23_0_8_0 folder with the flags above.

Ahhhh...thank you for the clarification on that and your assistance. Much obliged!

I'm still unable to get this to work properly. It errors out part way through the installation just saying "silent mode option flag found." Thank you anyway for your help. I'm not going to continue trying to work on this at this point.

This is an old thread but I ran into the same issue as Jason. The issue is that running UPS Worldship's setup.exe with the silent flag returns the string "silent mode option flag found" and prints it to standard error, triggering the error flag and causing PDQ to halt the install. What you need to do is redirect stderr to null by adding "2>nul" at the end of your install command i.e.

C:\temp\setup.exe /s /i C:\temp\WS_Silent.ini /l C:\temp\ups.log 2>nul

I created a package for deploying version 26.0 of WorldShip according to the instructions in this thread.  I too receive the "silent mode option flag found" error.  I then added "2>nul" to the end of the install parameters but get the following error:  Silent Mode Option Flag found
UnKown CommandOptions [ - 2>nul] Specified.. See Help for details

Take a look at the Sample in  INSTALLATION_26_0_6_0\PIF\IM\Resources\WS_Silent_Sample.INI 

We use a server-client based UPS Worldship deployment so rather than calling setup.exe directly, I created a batch script, "WS_Silent.cmd," and call that from PDQ. PDQ copies the batch file to the target computer and executes it, which then initiates the install of the Worldship client from the share on the UPS server. The contents of the batch are as follows:

@ECHO OFF
if not exist "C:\temp\" mkdir "C:\temp" >nul
\\[UPS Server Hostname]\[UPS WS share name]\UPS\WSTD\Remote\Install\Disk1\setup.exe /s /i \\[UPS Server Hostname]\[UPS WS share name]\UPS\WSTD\Remote\Install\Disk1\WS_Silent.ini /l C:\temp\ups.log 2>nul
reg import %~dp0UPS_DirectAccess.reg

You could use this exact method for a standalone install by making the following changes:

1. Ensure that "WS_Silent.ini" is in the same folder as Setup.Exe
2. Place "WS_Install.cmd" in the same folder as Setup.exe
3. Within "WS_Install.cmd," replace the UNC paths with "%~dp0" so:

\\[UPS Server Hostname]\[UPS WS share name]\UPS\WSTD\Remote\Install\Disk1\setup.exe /s /i \\[UPS Server Hostname]\[UPS WS share name]\UPS\WSTD\Remote\Install\Disk1\WS_Silent.ini /l C:\temp\ups.log 2>nul

now becomes:

%~dp0setup.exe /s /i %~dp0WS_Silent.ini /l C:\temp\ups.log 2>nul

You will notice that the last step in the batch script is to import a registry key. Importing this key will set the UPS Worldship proxy settings in advance so you don't get a prompt to set them the first time Worldship launches. I place the .reg file in the same folder as WS_Install.cmd and ensure PDQ copies over all files in the folder. Because we do not use a proxy in our deployment, the content of our reg file is as follows:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\UPS\ICC\DA]
"DAEnabled"="y"
"VerifyCgi"="/wstd/cgi-bin/kdhclcms"
"VerifyURL"="www.ws.cms.ups.com"
"DATimeout"="5"
"DAVerified"="y"
"Proxy"="n"
"ProxyAuth"="n"
"ProxyID"=""
"ProxyName"=""
"ProxyPort"=""
"ProxyPwd"=""

Please note that if your organization proxies internet traffic, you will need to modify the values in this registry key accordingly.

Thanks and I hope this was helpful.