override install condition using mst
hi all.. i just saw this one and i dont know if it can be done.. can an install condition be override using an mst?
the package i looked at will only install on admin privileges (Sentinel System Driver v5.42.0).. i want to try using an mst so it can install using limited account.. if you have any suggestion that would be a great help.. i got limited time to work on this [&:] and any help would be appreciated..
for the meantime i'll see what i can do [8D]
the package i looked at will only install on admin privileges (Sentinel System Driver v5.42.0).. i want to try using an mst so it can install using limited account.. if you have any suggestion that would be a great help.. i got limited time to work on this [&:] and any help would be appreciated..
for the meantime i'll see what i can do [8D]
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
MSIPackager
18 years ago
Hi Rikx,
You can make any changes you like in you mst.. Chances are it's a launch condition which you'll need to remove which is easy enough - however there will be a reason the package wants admin rights and depending on your environment you may need to do lots more than just remove a line out of the launch condition table...!
There maybe custom actions etc which will only run correctly with local admin rights, you may need to move these around / change the context they are running in. Start with the launch conditions and go from there - if you have problems installing as a locked down user then use a log file to get some idea of where the install is failing.
Presumably you are already installing MSIs with elevated permissions HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer - AlwaysInstallElevated etc?
Hope this helps,
Rob.
You can make any changes you like in you mst.. Chances are it's a launch condition which you'll need to remove which is easy enough - however there will be a reason the package wants admin rights and depending on your environment you may need to do lots more than just remove a line out of the launch condition table...!
There maybe custom actions etc which will only run correctly with local admin rights, you may need to move these around / change the context they are running in. Start with the launch conditions and go from there - if you have problems installing as a locked down user then use a log file to get some idea of where the install is failing.
Presumably you are already installing MSIs with elevated permissions HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer - AlwaysInstallElevated etc?
Hope this helps,
Rob.
Posted by:
rikx2
18 years ago
hi MSIPackager,
yep.. i did get around the installcondition.. but there's more i think.. there's a custom action which needs to specifically run on admin context.. its Sentinel Systems Driver 5.42.. i'll do some more test and see if i can make it run on user context with some editing [8|]
btw.. anyone dealt with this one previuosly?
thnks
rick
yep.. i did get around the installcondition.. but there's more i think.. there's a custom action which needs to specifically run on admin context.. its Sentinel Systems Driver 5.42.. i'll do some more test and see if i can make it run on user context with some editing [8|]
btw.. anyone dealt with this one previuosly?
thnks
rick
Posted by:
MSIPackager
18 years ago
Yeah, a guy here did the same version but he repackaged the install - rather than transforming the vendor MSI...
See if you can move the CA into execute deferred and set it to run in the system context.
Good luck [;)]
Rob.
See if you can move the CA into execute deferred and set it to run in the system context.
Good luck [;)]
Rob.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.