When installing an application (using the Wise Install Program) logged on as the local administrator to the local NT machine
We have the problem that certain active X components (created in VB6) are registered but with the permissions in the registry only giving access to the local administrator.
When a user logs in they get error messages (can't create active X component etc.)
Using the regmon tool we have identified that this is due to ACCESS DENINED on the registry
There are lots of registry settings so identifying these manually is a pain especially since we are installing on many machines
We know that if we give the user full access to all the registry it's OK but this is not acceptable from a security point of view
Are there any NT setting (policy etc.) that could effect the way the registry is updated?
We have the problem that certain active X components (created in VB6) are registered but with the permissions in the registry only giving access to the local administrator.
When a user logs in they get error messages (can't create active X component etc.)
Using the regmon tool we have identified that this is due to ACCESS DENINED on the registry
There are lots of registry settings so identifying these manually is a pain especially since we are installing on many machines
We know that if we give the user full access to all the registry it's OK but this is not acceptable from a security point of view
Are there any NT setting (policy etc.) that could effect the way the registry is updated?