Windows Forum

Ask something
Discussion Locked

W2K TerminalServer+Ex.2K Outlook problem

0 helpful
5 replies

by vahur

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
I have a problem starting Outlook 2000 within Terminal Services environment.
My setup: 1 server
W2K Domain Controller (single DC in a domain) SP4 ? Native Mode
Exchange 2000 Standard Ed. Sp3 Native Mode
Terminal services in application mode
Office 2000 Professional SP3
Whe user tries to start outlook , he/she is prompted for password. Under MAPI profile Network Logon Security is set to NT Password Authentication. After entering the password user gets the error message, stating:
?The logon credentials supplied were incorrect. Make sure your username and domain are correct, then type your password again?. Of course all the information entered (username, domain, password is correct). I have also tried to enter username in a form username@domain without any success.
When I add user to the domain administrators group, he/she can start outlook without any problems ? password prompt does not appear.. Also the administrator can start his outlook without any problems.
I also went to Default Domain COntrollers Policy > Computer Configuration > Windows Settings > Security Settings > User Rights Assignment and added the test user into several polycies, where an administrator account (or dom.adm group) was defined - no success.
Office was installed using .mst file after the terminal server was switched to the application mode.
Does anyone have an idea, how to solve this problem?

Oh, and a Happy New Year to everybody from Tallinn, Estonia!

Vahur

5 replies

by sativocomputerservices

I have had to do some additional configuration to get outlook to work successfully in TS and Citrix. Microsoft has a great article on how to troubleshoot this, but it would be my guess that these users will need local accounts setup on the machine or at least a profile. Without this, and policy changes will be lost. You will not see aproblem with your administrator because this is probably the account you used to install office.

by adrianmrutter

You need to ensure that when you installed Office you used the Transform script for installing Office under Terminal Services. If you ran a native install you would get problems similar to that which you refer.
The Transform scripts are available from Microsoft on the Office Resource Kit.
http://www.microsoft.com/office/ork/2000/appndx/toolbox.htm#orktools
http://download.microsoft.com/download/6/b/3/6b34f4c7-44e6-4d85-91d9-1acf9479da7d/orktools.exe

Further information can be obtained from
http://www.thin-world.com/tips.html

Don't be put off by mention of Metaframe, this is something that has to be installed on Terminal Services.

by adrianmrutter

You need to ensure that when you installed Office you used the Transform script for installing Office under Terminal Services. If you ran a native install you would get problems similar to that which you refer.
The Transform scripts are available from Microsoft on the Office Resource Kit.
http://www.microsoft.com/office/ork/2000/appndx/toolbox.htm#orktools
http://download.microsoft.com/download/6/b/3/6b34f4c7-44e6-4d85-91d9-1acf9479da7d/orktools.exe

Further information can be obtained from
http://www.thin-world.com/tips.html

Don't be put off by mention of Metaframe, this is something that has to be installed on Terminal Services.

This discussion is closed to new replies.