Welcome to the Indigo Rose Software discussion forums! You will need to sign up for a forum account and login before you can post. Need help? View the Forum FAQ.
Setup Factory installations adhere to security permissions the operating system has set for the user who is currently logged in. If that user does not have permissions to modify some registry settings, Setup Factory's actions will fail due to that fact.
Nine times out of ten a setup program needs administrative priviledges to perform its function properly, so the user will have to login as administrator before they can install anything. However, there are certain facilities inside windows to allow normal users to read and write to priviledged parts of the registry like HKEY_LOCAL_MACHINE, etc. In order to do this the keys with relaxed security will have to be created using the right security settings. SUF allows us to create new keys, but it does not allow us to set the security on these keys.
At the moment we have created our own dll which SUF calls to create the relaxed key under HKLM. We want the key there because now all users can share some data when appropriate. It would be nice if SUF allowed us to specify the security setting for new keys.
I'll certainly add your suggestion for consideration. I don't know if this is a possibility or not as I'm not too familiar with the security settings on Registry keys, or what needs to be done, however if it is of a generic nature, maybe you could create a Registry file to be merged with the user's registry so that the settings are already made? You can find a Knowledge Base article for merging files with the user's Registry at the following link:
The problem with our application is that certain things need to happen whoever happens to be the active user. For instance, timer recordings will have to go ahead no matter what, and hardware tweaks will have to be known to all users.
We were looking for a generic solution to make the same data available and modifiable to/by all users and came across this not very well known registry feature. MSDN has some info on the topic and with some creative browsing we managed to get enough of an idea to implement a helper dll.
Comment