MSI Utility
Novell Cool Solutions: Cool Tool
Reader Rating 
from 7 ratings
In Brief
Avoid pushing out a policy to elevate the MSI installer.
Vitals
| Posted: | 16 Sep 2002 |
| File Size: | 205KB |
| License: | Free |
| Download: | /coolsolutions/tools/downloads/msiutil.zip |
| Publisher: | Doug Glenn |
Disclaimer
Please read the note from our friends in legal before using this file.
Details
These utilities upgrade MSI to "AlwaysInstallElevated" in pre-distribution and then it is removed in post-distribution scripts. Eliminates the need to set the policy to allow MSI to AlwaysInstallElevated and to open a security hole.
Not everyone sets the Windows 2000 policies to allow any MSI based install to have elevated privileges; yet the Windows Installer sometimes requires this to be set when writing to a network drive.
These two utilities provide a means to set these settings temporarily during an install to avoid pushing out a policy to elevate the MSI installer.
Contains premsi.exe and aftermsi.exe.
PREMSI.EXE enables all the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Installer keys to a value of 1
It writes the following keys and values into the registry when run:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"AlwaysInstallElevated"=dword:00000001
"AllowLockDownBrowse"=dword:00000001
"AllowLockDownMedia"=dword:00000001
"AllowLockDownPatch"=dword:00000001
"EnableAdminTSRemote"=dword:00000001
"EnableUserControl"=dword:00000001
"TransformSecure"=dword:00000001
AFTERMSI.EXE removes all of the above keys and the Installer key when run.
Usage:
Add these files to the pre-distribution and post-distribution sections of the MSI install object. There are no command line parameters.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com
Reader Comments
- Exactly what I need.
- ??? I thought Zenworks distributed MSI's do this inherently???
- I get an error accessing the registry when I run it. I can change the key in a .REG file, though. So at least I was pointed in the right direction.
- did not get to work unless I associated the package by workstation instead of user ID.
- You must be administrator to run premsi.exe and then we are back to where we were...
- A real necessity! Works flawlessly.