Solved

Cannot setup Office97 on NT properly - PLEASE HELP

Posted on 1998-05-21
10
279 Views
Last Modified: 2013-12-28
I tried to install Office97 to all my Lab computers running NT4.  The installation was OK.  But when users want to save their files in Word or Excel, they get the following error:
Microsoft Word - Error writing updated settings to registry (Error 6 Registry key software\Microsoft\Office\8.0\Common\Open Find\Microsoft Word\Settings\Save As\Any Text MRU).

What does this mean? How to fix it?  If I logon to NT as an administrator, it works fine.  But if students login as a normal user (member of a user group - undergrad), they get this error.  The system and user profile setting are: all user accounts are on PDC (NT4).  All users use centralised *.man profiles.  Local cache profiles will be deleted by the system once the user logs off.  Office97 is installed entirely on the local HDD.  I tried all these: let everyone has full control of entire local hard disk drive; let everyone has full control of all files in server (PDC) \system32\config directory; user still get the same error.  It works only if I let user to use local profiles.  But obviously I don't want to do that.  Considering that we have hundreds of students use the lab,  I just cannot allow users to keep their profiles on each workstaton.  I also tried to set everyone full control to *.man profiles on the server, it still does not work.

I just don't know how to get rid off the error.  Please Help.

Some more info to comments from all helpers

Thank you very much for your help.  Here are some more information:

Connex and Cph - I tried to let the Students had full access to the above mentioned Registry-Key.  It didn't work.  Connex, can you give me some details about the knowledgebase you mentioned? Please.

Cph - They have roaming profiles.  It is OK with local profiles.

TSauer - The way I setup student user: I created a user group called undergrad.  This is the user group for all undergraduate students.  All undergrads are member of this group.  The member of this group has RX rights to all directories local directories and CHANGE to a local USER directory - a directory for them to keep their files.  They can also write their files to a server shared directory (PDC) so that they can access their files on the server no matter which machine they are goning to use next time.  They only have RX to centralised *.man profiles.  I tried to let them to have full control of all profiles.  It didn't work.

Freter - How to fix the bloody thing then.

Cph - I tried to let them to have full control of both local and centralised (*man) profiles. it didnt work, unless I let them to use local profiles.



0
Comment
Question by:fanf
10 Comments
 
LVL 2

Expert Comment

by:connex
ID: 1780114
Have you tried giving the Students write access to the
above mentioned Registry-Key?
We are working with Serverprofiles too and office works fine

0
 
LVL 1

Expert Comment

by:cph
ID: 1780115
connex is right, it looks like they can't write in the registry which is a safe thing. Unfortunately Office needs to write in it (from what you showed us).
The only cure is to give them partial right to write in the registry.
0
 
LVL 1

Expert Comment

by:cph
ID: 1780116
I forgot, do they have roaming profile or local profile?
0
 
LVL 2

Expert Comment

by:connex
ID: 1780117
We use roaming profiles, with some tuning to the registry rights.
I think i remember some knowledgebase articles about that

0
 
LVL 3

Expert Comment

by:TSauer
ID: 1780118
How do you setup your user.

In the case that it is not possible for a "Standard User" to setup Office97 with the NT Security, please describe in detail how you setup the users.
0
Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

 
LVL 2

Expert Comment

by:freter
ID: 1780119
Well, I guess, it is due to the mandatory profiles, hm?

0
 
LVL 1

Expert Comment

by:cph
ID: 1780120
In that case, give them the right in the HK_CURRENT_USER for that specific entry if possible.
0
 

Author Comment

by:fanf
ID: 1780121
Edited text of question
0
 
LVL 2

Expert Comment

by:tbaffy
ID: 1780122
Your problem stems from the fact that Microsoft Office products store information in Most Recently Used keys in the registry.  There are several of these keys that are used to hold variuos pieces of information such as the last entries in a dialog, or the list of files that is at the bottom of your file menu.  

If you are using manditory profiles that are stored on the server you will have to allow the profile to be cached locally.  You can delete the locally cached copy when they log off.  When you specify a manditory profile it is considered read only.  The user MAY be able to alter the locally cached copy if you have supplied sufficient NTFS rights to the local profile directory. You should be sure that the Default User, All Users, and local Administrator profiles are secured.  This should allow the users to alter the locally cached copy of the manditory user profile.  Since the NTuser.man file in the profile is the current users registry key (HKEY_CURRENT_USER) then you will still have to apply the required registry rights to alter any desired keys.

The undergrad group that you created is a global group on the server?  

Did you implement manditory profiles by putting the .man extension on the NTuser.dat file or did you put it on the Profile folder?

What are the permissions on the local Profiles directory?

Tom
0
 
LVL 3

Accepted Solution

by:
rmullins earned 200 total points
ID: 1780123
First of all, great explanation of the problem. Good explanations like that make it much easier for people to get you the proper solution. I have experienced this problem some time ago and believe I remember how to remedy the situation.

Tbaffy has the best explanation here, but it may be a bit difficult to understand unless you are very familiar with profiles and policies, so I will expand on it and point you to some resources.

The key here is not permissions on the files themselves (as you discussed in your message), but on the registry keys within the files that make up the registry.

The reason you are getting this message is because Office 97 must be able to write keys to the registry and/or the keys must exist, or you will get errors like the one you describe.

In case you aren't familiar with it, the following link will give you a brief description of how to change permissions on keys within a profile (in your case, a mandatory profile): http://support.microsoft.com/support/ntserver/serviceware/10141692.asp.  This is not a great description of how to do it, but you should be able to figure it out from this info.

I would try these two things in this order:

1) Edit the permissions on the mandatory profile key: Software/Microsoft/Office and give the appropriate users and/or groups (or everyone) change access to all subkeys. Remember, they are only changing the locally cached copy, which gets dumped upon logoff. This should allow them to make changes to the keys to perform functions such as saving.

2) If you are still having trouble after completing #1, create a new user account locally on one of the workstations. Then, log on locally as that user. Then go into the Office applications and make sure you can save, etc. This should create the necessary keys for MS office in the registry (if you save a file, you should make it a dummy file that everyone can access, or remove it from the MRU list (more on that below). Then, log off and back on the same machine as a different user (you need the profile to be 'released' and written to disk). Then, while logged on as the second user, copy the local profile for the new user up to the network and name it as your mandatory profile. Then perform step #1 above on this new profile. Finally, give it a try by logging on as a user with the new mandatory profile. If you followed this carefully, you should now be able to perform the functions you did when you were logged on with the local account.

If you want some more info on MRU (Most Recently Used) lists and the keys associated, follow this link: http://support.microsoft.com/support/kb/articles/q161/6/30.asp
Although the link is for Word 95, you should get the idea.

I know this is confusing, but if you read it carefully a few times and go through the material I have linked, it should make sense.

-- Rob --
0

Featured Post

Do email signature updates give you a headache?

Constantly trying to correctly format email signatures? Spending all of your time at every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

Join & Write a Comment

Suggested Solutions

Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup". After a while, you have entered a loop for Auto repair which does not fix anything and you will be in a  panic as all your work w…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now