Updating to Sametime 7.5.1

I'm trying to script a silent install of 7.5.1 My trouble is that it would seem that the previous installation of 7.5 was done from a per user basis (sametime default?). So when I try to drop the 7.5.1 install on top it is looking for the source files in the profile that no longer exists. I can't seem to find a way to redirect the installer to an alternate location using a script. I know the MSI works as a source because i can browse to it manually at the dialog.

How can I get the installer to look where I want it to instead of where it thinks the source files are?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: anonymous_9363 12 years ago
Red Belt
The SourceList is located at [HIVE]\Software\Microsoft\Installer\Products\<product code>\SourceList\Net
where '[HIVE]' is either HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE depending on whether the product was installe dper-ser or per-machine respectively.

The list can be manipulated in script, too, using the WindowsInstaller.Installer object. There's a bunch of Installer scripts (amongst many others) at http://www.desktopengineer.com - look for MSISources.VBS specifically.
Posted by: fearlessfreep32 12 years ago
Yellow Belt
In HKLM I have the uninstaller source
In HKCU I have the installer source
Both changeable via script and of course changing HKCU will change HKU

I am trying to deploy my script via Altiris and I think that the script is running using the Altiris account through the agent.
This is creating a new key in HKU that has pulled in the old installer source. Where is that coming from. Can I change that?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
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