thanks in advance,
-daren kobata
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Creating HKLM keys as Restricted User
Started by
darenko
, Feb 28 2002 23:38
1 reply to this topic
darenko
-
- Members
- 14 posts
Posted 28 February 2002 - 23:38
I am using ISWI 2.01. Our current product requires that we create HKLM keys. But, as a restricted user, you cannot add keys in this location (only HKCU). Does anyone know a way around this? Does the new Developer 7.0 handle this problem? It works through Group Policy, but does not as a regular installation. Any help would be appreciated.
tsweet
-
- Members
- 15 posts
Posted 21 March 2002 - 19:05
Change the perms for them......
What you can do is:
1. For them to install as admin by making a launch condition of adminuser with text of "you must be admin... " or "you are not worthy....
2. add registry permissions in the lock perm table.
In your registry component, right click and add a MSIvalue to each tree. I do it to a data value in each tree. then in the lock perms table, enter something like.
Lockobject = MSILOCK1
Table = Registry
Group =
User = Everyone
Permission = 268435456
It is really not that hard. Some frown upon this sort of thing, but it gets the job done. If you dont use the MSIvalue as the primary key, then you can look in the registry table in ORCA and all the entries will be listed as registry1, registr2, etc. You could use those, but if you ever add keys to the install, all the numbers get reset, so use the msivalue key
see lockpermissions in the Windows Installer help, no ISWI
What you can do is:
1. For them to install as admin by making a launch condition of adminuser with text of "you must be admin... " or "you are not worthy....
2. add registry permissions in the lock perm table.
In your registry component, right click and add a MSIvalue to each tree. I do it to a data value in each tree. then in the lock perms table, enter something like.
Lockobject = MSILOCK1
Table = Registry
Group =
User = Everyone
Permission = 268435456
It is really not that hard. Some frown upon this sort of thing, but it gets the job done. If you dont use the MSIvalue as the primary key, then you can look in the registry table in ORCA and all the entries will be listed as registry1, registr2, etc. You could use those, but if you ever add keys to the install, all the numbers get reset, so use the msivalue key
see lockpermissions in the Windows Installer help, no ISWI
Thank you[br]Tom Sweet