Problem with SURunAsWizard

I am about to rollout several customized Lotus Notes 8.5.2 installation kits. I want to use Smart Upgrade and attach the installation-kit as a big .exe-file in the Smart Upgrade document.

I have a big problem with SuRunAsWizard. The problem is the following:

  1. Using Lotus Notes 8.5.2 English client downloaded from Partnerworld

  2. Extract installation files into a folder

  3. Modify installation files using Install Shield Tuner for Lotus Notes. I now have a customized mst-file

(I do not touch location of shortcuts)

  1. Test package by installing on Windows XP SP3 English. Everything works as intended and shortcuts are placed correctly in Start Menu

  2. I use SuRunAsWizard.exe (taken from Lotus Administrator 8.5.2) and select all files withing the Customized installation kit

  3. Select “setup.exe” as the program to execute

  4. Add this line as command to setup.exe:

-s /s /v"TRANSFORMS=customer1.mst ADDLOCAL=ClientSingleLogon /qb-!"

(I have also tried without mst-file and it the same result)

  1. When the package is built I test it (in the same environment as previous test) and all the short cuts that are supposed to be in Start Menu end up in C:\

Here is where the Shortcuts end up:

C:\Lotus Notes 8.5.lnk

and

C:\Lotus Applications\Support

C:\Lotus Applications\Lotus Notes 8.5.lnk

C:\Lotus Applications\Notes Minder.lnk

C:\Lotus Applications\Support\Collect Lotus Notes diagnostic data and exit Notes.lnk

C:\Lotus Applications\Support\Collect Lotus Notes diagnostic data and leave Notes running

I also tested to do exactly the same steps using Lotus Notes 8.5.1 installation files and SuRunAsWizard.exe (from Lotus Administrator 8.5.1) and the exact same problem occur.

Anyone with an idea how to solve this?

Subject: Some things to try…

What user account are you configuring in the SURunAsWizard to run the Notes install kit with? It might be that the account doesn’t have the correct locations for the Windows Installer engine to resolve.

You could try starting a command prompt as that account, see Windows help and learning and then run the Notes installer from that prompt. That would emulate the context that SURunAs is trying to run the Notes installer in.

Taking a look at the verbose output of the installer when installed using that account would show this. Change your embedded command line to:

-s /s /v"TRANSFORMS=customer1.mst ADDLOCAL=ClientSingleLogon /qb-! /l*v C:\VerboseInstall.log"

And examine the VerboseInstall.log file. You should see a section near the top like this:

MSI (c) (20:3C) [13:20:53:133]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\jeffm\Application Data

MSI (c) (20:3C) [13:20:53:133]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\jeffm\Favorites

MSI (c) (20:3C) [13:20:53:133]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\jeffm\NetHood

MSI (c) (20:3C) [13:20:53:133]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\jeffm\My Documents

MSI (c) (20:3C) [13:20:53:133]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\jeffm\PrintHood

MSI (c) (20:3C) [13:20:53:133]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\jeffm\Recent

MSI (c) (20:3C) [13:20:53:133]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\jeffm\SendTo

MSI (c) (20:3C) [13:20:53:133]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\jeffm\Templates

MSI (c) (20:3C) [13:20:53:133]: SHELL32::SHGetFolderPath returned: C:\Documents and Settings\All Users\Application Data

As you can see above my installation has those value correctly resolved.

Finally you can try to force Windows to load the profile of the account you are trying to run the Notes installer in when you run SURunAs. The command line option for that is -profile. So running

SURunAs.exe -profile

will try that.

~jeff

Subject: Solved

Hi Jeff!

Thanks for this help! I was able to solve this problem by adding ALLUSERS=1 into the command line.

The SURunAsWizard explicitly says that ALLUSERS=1 must be used. I don’t know why I missed this important parameter.