/build/static/layout/Breadcrumb_cap_w.png

Acces permissions on Registry

Hello,

Does anyone know how to set permissions on one of the "Root" Registry key’s?
So I mean HKEY_CLASSES_ROOT, for instance.

It has to be done either from within the MSI itself, ore by script.
I know of a solution by script, but the problem is I have to use a MSI-Property as group name, and I don't know how to get a property from a MSI file, into a VBS-Script ..

So if anyone can help me with setting the permissions directly, or getting a property value from an MSI into a VBS-Script, I would be ferry happy.

Thanks in advance. [;)]

0 Comments   [ + ] Show comments

Answers (6)

Posted by: FunnyName 20 years ago
Senior Yellow Belt
0
I found out how to get a property out of the running MSI file. If you want to know, read the following link:
http://www.installshield.com/news/newsletter/0302-articles/msiaccess.asp
Posted by: Mooijr 20 years ago
Yellow Belt
0
In your msi call a vbs action en copy the vbs in to it
with de MMC create a sec.inf file en set the extra key's you want the user te modify and put this inf file in youre msi

at the end sec edit wil purce these rights good luck!!!


Dim objShell, objFso '// Declaring object variables
Set objShell = CreateObject("WScript.Shell") '// Creates Shell object
Set objFso = CreateObject("Scripting.FileSystemObject") '// Creates File System object
Set strSystemPath = objFso.GetSpecialFolder(1)
objShell.Run strSystemPath & "\secedit.exe /configure /db secedit.sdb /cfg " & _
"""%WINDIR%\security\templates\APPLICATIONNAME.inf"" /log " & _
"""%WINDIR%\security\logs\Appicationname.inf.log"" /quiet", 0, true
Posted by: FunnyName 20 years ago
Senior Yellow Belt
0
Thanks, this methode I didn't knew ..
I am using SetACL.exe now, a handy util that does the job fine. There is also a W2k resource kit utill named Dacl.exe, I've heard this can be helpfull too.

Thanks for the inside![:D]
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
I like to use reggrant and secedit with inf files.

I find them both very good.
Posted by: ssweb 20 years ago
Senior Yellow Belt
0
I have looked around here a bit for working with file permissions and found that this looks the best option.

I am not much of a VB person so I would like to know if this script is OK. You know the old fat finger syndrome. What is with the underscores after the &

I tried this in a msi and it did not seem to want to work.

THanks for the help


ORIGINAL: Mooijr

In your msi call a vbs action en copy the vbs in to it
with de MMC create a sec.inf file en set the extra key's you want the user te modify and put this inf file in youre msi

at the end sec edit wil purce these rights good luck!!!


Dim objShell, objFso '// Declaring object variables
Set objShell = CreateObject("WScript.Shell") '// Creates Shell object
Set objFso = CreateObject("Scripting.FileSystemObject") '// Creates File System object
Set strSystemPath = objFso.GetSpecialFolder(1)
objShell.Run strSystemPath & "\secedit.exe /configure /db secedit.sdb /cfg " & _
"""%WINDIR%\security\templates\APPLICATIONNAME.inf"" /log " & _
"""%WINDIR%\security\logs\Appicationname.inf.log"" /quiet", 0, true
Posted by: xink22822 20 years ago
Senior Yellow Belt
0
Have you made an inf file with security templates?
You must add the inf file into the package under c:\windows\security\templates.
You also have to modify the APPLICATIONNAME.inf name in the script with the name of your inf filename.
After that it will lauch secedit.exe to apply the inf file to set permissions.

ps: the underscores is just an end of line sign
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