Discussion Locked

rights issues with ms office 2000

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Does anyone know why when the user permissions on the local machine are set to anything below power users, ms office won't run? We would like to limit installs of unauthorized software by limiting rights on the local machine, but office won't run.

6 replies

by beermonster

Hi,
I'm assuming that there are parts of office that are causing you problems, rather than office itself not running (although if it doesn't run full stop I wouldn't be surprised). I've had issues with office at several company sites, and can tell you the reason - microsoft are a bunch of cowboys (and that comes from someone who makes a living from their software : ).

Basically, the first versions of office were deigned around windows 9x, where there was no concept of different users having different rights. Basically, if you could get on to the machine, you could do anything. The office designers duly went ahead and had the various office components creating, modifying or deleting files and registry entries all over the system....

Now comes the idea of different levels of security. Now you'd think (ha ha), bearing in mind that all releases of office are at core the same but with a few addons and takeouts, that the office team would be made to go through all of the components and ensure that where they create, delete or modify files \ registry settings that the new security model would be taken onto account

BUT NO..... OHHHH NNNNOOOOOOOOOOOOOO

THAT WOULD BE TOO F~~$?*G EASY!!!!!!!!!!!!!!!!

So instead youhave security setting hell. Now, the microsoft office team would have you believe that they have handled this, and that they alter the security as part of their install - hell, they even include an xls file of all the registry updates they are claiming to do. Some news fella's - IT DOESN'T WORK PROPERLY.

by beermonster

Hmmmm, enough of this ranting. How to solve your problems - the following is a cut and paste from an answer given to someone else with office problems. There is a file called regmon at the same site which will do the same thing for registry problems- believe me you'll be needing it, just when you think it's job done someone will ring you up about the obscure piece of office functionality (which you've never heard of) that isn't working. If you find any of the instructions confusing then mail me at darthurs@hotmail.com

Good luck.....

Download filemon.exe from www.sysinternals.com this util will tell you about every file and folder access while it is running, as well as the result of that access. log in as admin, run filemon (filtering it to look at only winword.exe will cut down the output), then use 'runas' (highlight winword.exe, press shift and then right click) to run word as a restricted user. Once the error message appears, scan the output of filemon and look for 'access denied' errors. this will tell you what area of the file system word is trying to access at that point. If you get no access denied errors, remove the filter in filemon so that it looks at everything. To immediately fix the problem, open up just thatarea to all users.

by beermonster

One more thing, I'm assuming that you are running win2k \ xp - if it's nt then you can start regmon \ filemon as localsystem while logged in as a user via the the old scheduling trick. Make sure the schedule service is running as localsystem, log inas the user and schedule a job via the at command to open up a cmd window a couple of minutes into the future. When it opens - hey presto a command window as localsystem (don't you just LOVE microsoft). use that window to open regmon \ filemon....

by tracarts

Thank you, the actual application that was causing the problem was not the rights, but the integration between office and filenet a panagon database application. Once we removed the integration, then office ran.

This discussion is closed to new replies.