Outlook on Terminal server issue

By Nimmo ·
We have just finished installing a new Terminal server (2k3x64) which has office 2k3 installed.

Every time someone logs into the terminal server and opens outlook it opens then close straight away stating that
"outlook could not be opened. the outlook folder could not be opened".

After troubleshooting for an hour or so I found that if I set outlook to prompt for authentication outlook would open but will then close out and error the same way
once the credentials have been entered - which makes me think it is an authentication problem.
(nothing shows in the audit logs)

But if I log onto the Terminal servers console session, I can put outlook into cached mode which works fine.

I have also found that if I enable encryption the users are able to open outlook in live mode without any issues.

I know the simplist solution is to turn the encryption on, but I haven't seen this problem before at any other site so i dont see why it is needed to be enabled.

I'm wondering if anyone else has seen this issue and if so how was it resolved?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Not really sure if this will help

by Jacky Howe In reply to Outlook on Terminal serve ...

but its a thought.

Create a New Outlook Profile

Collapse -

Been there done that

by Nimmo In reply to Not really sure if this w ...

Thanks for the reply but I have already created a test user on the domain, logged in configured there terminal server & outlook profile, then reconfigured it using different settings.

The results I found are stated in the above post where by for some reason only cached outlook profiles seem to be able to authenticate to the exchange box.

Seen as you can only create a cached profile when connected to the console on a terminal server that isn't a solution either.

Collapse -

RE: have you seen this

by Nimmo In reply to Have you seen this

Users can log onto the terminal server fine it seems to be more of an exchange authentication/privilege issue than anything else.

Related Discussions

Related Forums