Deployment Solution

I'm just in testing phase with Windows 7 and DS 6.9 SP3 and have come across an oddity when deploying my first test job of Winzip 14

The job is simply a script running as "Default (local system account)" and contains:
msiexec.exe /i \\%DSSERVER%\express\RIPs\winzip14\winzip140.msi /qb

This runs OK, but on the client machine no winzip icon appears on the Desktop, nor does it appear in the Start Menu and no context-menu entry for Winzip appears. It does install correctly as the Winzip folder is present in Program Files (x86) and also appears in "Programs and Features" and can be uninstalled. Once the application is run from the Winzip folder the context Manu item appears.

The odd thing is when I manually run the exact same command from a Command Prompt, it installs as expected along with the icons and context menu.

Any ideas on why this happens? Deploying the same job to Windows XP machines (Aclient installed) works as expected.

We had a lot of weird things happen on Windows 7 x64 when deploying MSI's with SP3.  One of the fixes in SP4 was to address MSI permissions when deploying software to Win2003 systems -- nothing specifically identifying Windows 7 -- but when we did the upgrade our problems went away.

Odd that it installed "halfway" for you -- our jobs were failing outright with 1603 errors.

Fun things happen when UAC is enabled.  Try disabling UAC if it isn't already.

My guess is that the shortcuts are being installed in the system account's user profile. The simplest way to remedy this is to enable the ALLUSERS property of the msi install, this will cause the shortcuts to be installed for all users rather than only the current user.

Try this command:
msiexec.exe /i \\%DSSERVER%\express\RIPs\winzip14\winzip140.msi ALLUSERS=1 /qb

Many thanks, ConderMan. That's the one that's done the job.

(Turning off UAC as suggested above didn't make a difference however.)