Here's a possible suggestion.
About 90% of programs fail to run due to either file permission problems (e.g. requiring RWXD to the original program folder), or because they;re trying to write back to HKLM (most of which is RO).
Use tools such as regmon and filemon by sysinternals to find the security violations. Then make a judgement call whether or not to modify the security to allow that program to run.
Finally, write a security template which you can then apply to all the machines (use SECEDIT to apply).
I created a custom template for our machines at work which works very well....
Cheers,
Mike
Almost - but not quite. The NTUSER.DAT for a particular user also has it's own internal security permissions. These can be viewed by importing the NTUSER.DAT using REGEDT32.
The missing link is to EXPORT the user account, thus allowing the internal permissions to be reset.
Slashdot Mirror
Nope, it doesn't appear to have been fully rejected. Scottish Hydro Electric appear to offer the service. Website with details here:
Cheers,Scottish Hydro
Mike
Here's a possible suggestion. About 90% of programs fail to run due to either file permission problems (e.g. requiring RWXD to the original program folder), or because they;re trying to write back to HKLM (most of which is RO). Use tools such as regmon and filemon by sysinternals to find the security violations. Then make a judgement call whether or not to modify the security to allow that program to run. Finally, write a security template which you can then apply to all the machines (use SECEDIT to apply). I created a custom template for our machines at work which works very well.... Cheers, Mike
Almost - but not quite. The NTUSER.DAT for a particular user also has it's own internal security permissions. These can be viewed by importing the NTUSER.DAT using REGEDT32. The missing link is to EXPORT the user account, thus allowing the internal permissions to be reset.