/build/static/layout/Breadcrumb_cap_w.png

deployments installing for each user

We are a school district and our user profiles are not saved on the local machine. When I try to deploy a package repackaged with AdminStudio the package goes through the installing routine when each user runs the package for the first time. This is not working for us since our users do not have local profiles on the machines and the package does the installing routine everytime they use it. I am new to packaging and need a way to keep this from happening. Any help would be appreciated...

0 Comments   [ + ] Show comments

Answers (5)

Posted by: mikkojarvinen 13 years ago
Senior Yellow Belt
0
Just a guess: You have included some user-specific setting (under HKCU or "Documents and Settings") in the MSI and Windows Installer is trying to fix the "broken" install for users. Get rid of those settings.

And you really have understand how Windows Installer and MSI packages works before you can start repackaging.
Something to start with:
<http://itninja.com/blog/view/working-with-windows-installer>
And here is the answer to (almost) all questons:
<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/windows_installer_start_page.asp>
Posted by: blockern 13 years ago
Yellow Belt
0
Thanks for the links. I will check some things on my packaging. We have always had to copy the profile we make specific settings in to the default user profile on each machine so that the users will get those settings. I am hoping I can avoid that this time.
I am packaging some smaller packages, as well as, openoffice 2.2 at the moment.
Posted by: mikkojarvinen 13 years ago
Senior Yellow Belt
0
blockern wrote:

Thanks for the links. I will check some things on my packaging. We have always had to copy the profile we make specific settings in to the default user profile on each machine so that the users will get those settings. I am hoping I can avoid that this time.

If you include user-specific settings inside your MSI (and Windows Installer notices that the component's KeyPath is missing) then the Self-Healing is what happens. It is also possible that you have included some system settings that shouldn't be inside MSI.


I am packaging some smaller packages, as well as, openoffice 2.2 at the moment.

OpenOffice.org is already a MSI.
Posted by: knight 13 years ago
Orange Senior Belt
0
Hi,

If you included a user specific files or registries in your package, try to use active setup.

Everytime a new user logged in, specific files and registries will be loaded on logged in user profile.

Hope this helps,

Knight
Posted by: anonymous_9363 13 years ago
Red Belt
0
OpenOffice.org is already a MSI.You probably ought to have added that re-packaging apps which are already in MSI is *generally* considered to be A Bad Thing. Maybe the OP already knew that anyway and meant that he's creating transforms for these apps.
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