Discussion Locked

Outlook 97 in W2K Terminal Services

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I can't get Outlook to work in terminal services. The program loads, but does not recogize the services added (internet e-mail). It works fine if I give the users administrator rights. What do I have to give them rights to inorder for this to work correctly?

14 replies

by stillatit

The problem is that Office 97 apps do not share well under W2k. You get the same problem installing Office on a user machine which will be used by multiple users.

When you installed Outlook, it put some files in places and with protections that block normal users. You can find these files by turning on failure auditing for a user and for the Windows directory, then logging in as that user and running Outlook. Then log back in as the admin and check the event viewer to find the file(s) which the user could not access. Change the protection on those files. Note that if any of these are .pst or .pab, you need to individualize these for the user and you should move them to the user's home directory.

Good luck.

by technews

Has to be a permissions issue. As long as I give them admin rights I can login as anybody and everything works fine. So, I must be missing whatever it is I am supposed to give them rights to.

by curacao_dejavu

Check if they have the appropiate permissions in the registry.

When you try to run Microsoft Outlook 97, you may receive the following error message:

The Program is not registered properly. Please run Setup again. You don't have appropriate permission to perform this operation.
This behavior can occur if you are a local user or a domain user. Local and domain administrators can run Outlook 97 correctly.

CAUSE
When you start Outlook 97 as a local user or a domain user, you musthave permission to write and modify the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Office

RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

To resolve this issue:

Log on to the system as a local or domain administrator.

Start Registry Editor (Regedt32.exe).

Click the following key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Office
On the Security menu, click Permissions.

Add the Local Users group or Domain Users group.

In the Permissions box, give the appropriate user group Full Control access rights.

by curacao_dejavu

In the Permissions box, give the appropriate user group (that's domain users , or terminal server users or a group you made) Full Control access rights.

by technews

I have already given the user(s) permissions to that key in the registry.
In fact, I searched the directory and gave them rights to everything that came up for office and outlook and it still didn't work. That is when I tried admin rights and that works, although I obvioulsy don't want to give all my users admin rights.

Thanks

by sativocomputerservices

I am assuming that this problem presents itself when dialing in. The problem is with the terminal service program using cached account information when a computer dials in. The network assigns an IP address to the laptop or PC when a connection ismade to the terminal server. This does not coorespond to the known IP address in DNS. Consequently, since the PC is assumed part of teh network, for accounts it will use cached information. To get around this, you need to assign IP addresses for the laptops that dial in or uncheck box 47 on the DNS configuration for Microsoft DNS. This should fix the problem.

by maxwell edison

The Ntuser.dat file, which is the default set of registry keys that load each time a Terminal Server user logs on, contains another user's profile information. You get this error message because Outlook attempts to use the other user's profile.

This problem occurs when the administrator runs Outlook and installs Terminal Server simultaneously.

Rename the Ntuser.dat file while you are logged on as the administrator on the Terminal Server console, and then restart the Terminal Server. This creates a default Ntuser.dat file that does not contain any profile information.

For additional information about Ntuser.dat on Windows Terminal Server, click the article number below to view the article in the Microsoft Knowledge Base:

http://support.microsoft.com/directory/article.asp?ID=kb;en-us;Q146050

(REMOVE SPACES from the pasted URL)

Maxwell

This discussion is closed to new replies.