/build/static/layout/Breadcrumb_cap_w.png

Enterprise Install Sourcepath change

I've been tasked with relocating my package installation sharepoint to another server. This sharepoint has been in place for a while and has many packages that have been deployed to apx. 600+ workstations. I don't have any type of SMS server/client tool, and I've been deploying all of my applications with login scripts. This is going to break self-healing and advertised feature installs for all of the programs I've published on this sharepoint.

I know there are source path keys on my workstations in the following locations:

HKEY_CLASSES_ROOT\Installer\Products\<GUID>\Net

HKEY_CURRENT_USER\Software\Microsoft\Installer\Products\<GUID>\Net

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\<GUID>\Net

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Userdata\<SID>\Products\<GUID>\InstallProperties

What I don't know is if there is a specific search order in which these keys are processed, or if there is a clientless tool I can use to change these keys on all my workstations. Has anyone out there undertaken something like this, and what did you do to make it work? Any feedback is greatly appreciated!

Cheers!

~Mike

0 Comments   [ + ] Show comments

Answers (1)

Posted by: MSIMaker 19 years ago
2nd Degree Black Belt
0
Darwin Sanoy at www.desktopengineer.com has created a utility for doing exactly what your asking for. Check it out.
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