Jump to content
Compatible Support Forums
Sign in to follow this  
bytemangler

win2000

Recommended Posts

Hi all I got another question on top of my previous post. Security issue with win2000 pro. most program requires I install it under admin account. After that however, I set a shortcut for a domain user to access. What I have run into is access denied to launch the application. For example I have a station setup to just scan in B/W blueprints using MS Photo Editor (part of office2K install under admin). Everytime the app is load I get this message "no file information found in the registry". I i give admin priv. to the user no prob. Outlook,Word,Excel does not seem to have issue at all? anyone have a suggestion?

Share this post


Link to post

I've had to deal with the exact same issue. This problem requires a registry edit. I don't have the link to the info at present, I'll see if I can haul it up for you.

Share this post


Link to post

i also noticed that same problem. the registry thingy works

but also w2k seems to have permissions problem

i have fixed many of the problems by resetting the permissions

shocked

Share this post


Link to post

The registry edit allows user specific privellege to the program, without having to change machine wide rights and priveleges. Or, in some cases network priveledges, no point making your regular users into Power users, or building exotic MSI scripts to give access to a simple program, when it can be done at a local level using Regedit.

 

Fact is, the problem shouldn't be there in the first place \ smile

Share this post


Link to post

It depends on the issue, in many cases the application designer should be keeping file and registry key placement in mind when the application is created, but many are in fact too lazy to do this. This particular issue that Catdog is illustrating is along the same vein, but is slightly different. The problem stems from more of a "hiccup" during installation than anything else, and the key permissions were not set properly. This is common in upgrade scenarios, where an older application did not require R/W access to a key, and the upgrade installer did not take permissions into account. Some of the worst offenders are major application vendors like AutoCAD, that seem completely incapable of moving their crappy files into their own directory (R/W access needed), and not allowing for registry permission configs in typical NT networks. Again, a simple matter of just being too damn lazy.

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×