I have an application that occasionally needs to install an updated activeX control. Each time this happens, I have to change users from standard to local administrator, let the controls install, and then change it back. How can I allow the machine to install these updates without giving full time local administrator privileges to each user?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to configure install permissions.. 1
- Thread starter cisscott
- Start date
See if Greg's program can help you.
Running Legacy Software on XP with a limited user Account
thread779-676827
Running Legacy Software on XP with a limited user Account
thread779-676827
-
1
- #3
Greg's application may help.
Did you write the ActiveX, or need to "push" one written by others?
I honestly think that something was not done right (particularly for registry permissions) in the .MSI when it was created.
This should be doable.
Did you write the ActiveX, or need to "push" one written by others?
I honestly think that something was not done right (particularly for registry permissions) in the .MSI when it was created.
This should be doable.
Greg's application may help.
Did you write the ActiveX, or need to "push" one written by others?
I honestly think that something was not done right (particularly for registry permissions) in the .MSI when it was created.
This should be doable.
Having complained about the MSI file, three suggestions:
. use RegMon to monitor (as Administrator) the registry changes
. use FileMon to register (as Administrator) the file changes
.... Now check/change permissions on the keys required.
Suggestion #2: Write your own wrapper application. Use the native IEXPRESS application. (You really have to read about it for this to make sense: )
Suggestion #3: Write your own wrapper:
Did you write the ActiveX, or need to "push" one written by others?
I honestly think that something was not done right (particularly for registry permissions) in the .MSI when it was created.
This should be doable.
Having complained about the MSI file, three suggestions:
. use RegMon to monitor (as Administrator) the registry changes
. use FileMon to register (as Administrator) the file changes
.... Now check/change permissions on the keys required.
Suggestion #2: Write your own wrapper application. Use the native IEXPRESS application. (You really have to read about it for this to make sense: )
Suggestion #3: Write your own wrapper:
- Thread starter
- #5
these are awesome suggestions and I am finding even more stuff I need to learn. I'll tell you more about whats happening like I should have before. The App is Crystal Enterprise. When I patch it, it needs to update the activeX control that is basically the cystal viewer. It seems like I remember a way through local policy to set it so that the control can still install itself under a restricted or standard local user account, but Im not having much luck figuring out what it was.
See:
But a lot more information would be needed, including Version numbers.
But a lot more information would be needed, including Version numbers.
- Thread starter
- #7
- Status