On Mon, May 2, 2011 at 10:35 AM, David Lum <[email protected]> wrote: > The workaround is if I log in as local admin and launch the app it will then > start working again for those users as well.
I've seen this behavior before from an application that (attempts to) register DLLs or OCX custom controls when it invokes those components, rather than at startup. So some rarely-used feature is invoked by the users, it sees the component is not registered, tries to register it, hits restrictive permissions, pukes and dies. You run it as admin, it registers the needed components, now it works for the users. As for why 2008 vs 2003, Microsoft keeps cleaning up the security in Windows with every release. Older releases were more permissive. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
