• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 582
  • Last Modified:

Common Settings For All Machine Users

I need to deploy an application and want to ensure that all users on a single machine are configured with the same application settings which I pass during the deployment process (msiexec.exe /i "xxx.msi" ALLUSERS="2" SQLDB="yyy"), particularly SQL database name.

The deployment creates the desktop icon, as I want, and when a new user clicks on this, I get the standard message "Please wait while windows configures .....".  I was expecting the new user to have the same setting for SQLDB as the administrative deployment.  It isn't.  What am I missing?

Any guidance would be appreciated.

Regards

Julie
0
AHJ2008
Asked:
AHJ2008
  • 4
  • 4
1 Solution
 
Vadim RappCommented:
please explain how you know that sqldb is not the same.
0
 
AHJ2008Author Commented:
Hi, thanks for responding.

The property is saved to a registry key for each individual user.  I looked at the key for the administrative install and it has the value passed.  The second user has the default setting in the MSI.

Regards

Julie
0
 
Vadim RappCommented:
Which is expected, if there was installation for that 2nd user, and it went without the passed parameter. Properties that took place during the installation are not stored anywhere in the system by themselves. Store this registry setting under hklm; make it the keypath of the component; and the component must have flag "never overwrite".
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
AHJ2008Author Commented:
Hi

OK, so unless I store the results of the first install into a shared registry location, or say an INI file for that matter, any subsequent install will take the default values.

Could you clarify what you mean when you say make it the keypath of the component.  Is that referring to a System Search?
0
 
Vadim RappCommented:
like this for example. Also see description of the flag msidbComponentAttributesNeverOverwrite in the article "Component Table" in Windows Installer SDK Help.
Capture-02-23-00001.png
0
 
AHJ2008Author Commented:
OK ... I think I understand, but you can only set one registry value as the key as its the existence of the key path that is important, rather than the value?
0
 
Vadim RappCommented:
In this case, it's only the way to be able to specify "don't overwrite". You can't specify "don't overwrite registry value" , but you can specify "don't overwrite keypath of the component". So you make the registry value you don't want overwritten the keypath and then specify "don't overwrite keypath" for that component.
0
 
AHJ2008Author Commented:
Cheers, that gives me something I can run with.

Thanks

Julie
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now