Re: Outlook 2003 issues on our Terminal Server - no send and receive (0x80040119)

He doesn't need it, but our remote office does. We have 6 users who work in
a satellite office that connect to our TS. Uninstalling Outlook from the TS
is not an option.

What I'll maybe try to do is disable those laptop users (only those that
need on OST) from using Outlook on the TS, and point them to either Outlook
over HTTP or OWA instead.

I know why Microsoft have disabled OST's on TS (or at least their official
line), but it seems a bit draconian to prevent it in all cases. We have < 10
remote users on our system. Is having OST's really going to be a performance
zapper, considering we've got a dual-quad-core system with 4GB and very fast
disk subsystem?! But then again, if you actually take a look at the
recommended hardware specs for a TS, then maybe it is? Surely, if that is
the reason MS have disabled cached exchange on a TS, then leave it up to the
end user. They could simply recommend not doing it rather than preventing
it. Is there some other reason that MS won't or can't allow it?

What about Server 2008? Is that going to be the same (I've not checked any
release notes, so it may already be common knowledge)?



Neil


"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:ukwiMj0FIHA.5752@xxxxxxxxxxxxxxxxxxxxxxx
I would disable (uninstall) Outlook on the TS. If he uses Outlook over HTTP
he doesn't need it on the TS.

I'm not aware of any 3rd party solution that would handle this. The only
thing would be to copy them into a pst. But I would not recommend that as
it creates a whole set of other issues.

--
Claus
"Neil Myers" <neil@xxxxxxxxxx> wrote in message
news:eeyd3U0FIHA.4628@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Claus,

Outlook's not the reason he needs the TS access. He already uses Outlook
over HTTP. We were looking for a way to get around the cached mode issue
on the TS. Even enabling Outlook over HTTP, he's still going to get the
problem when he's working on the TS desktop if he ever opens up Outlook
on there.

Likewise, if I disable cached mode, unless he's connected to the
internet, his email won't be available. Not much use if he's stuck in a
meeting and has no network/wifi access!

Is there any third-party solution that allows an offline Outlook mail
store without having to enable cached mode?




"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:ueXvwQxFIHA.284@xxxxxxxxxxxxxxxxxxxxxxx
Why are you not configure him to use Outlook over HTTP? That would solve
all your problems and he wouldn't need to use TS in the first place.

--
Claus
"Neil Myers" <neil@xxxxxxxxxx> wrote in message
news:eW2fYusFIHA.5228@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

We have a Windows 2003 TS member server on our SBS network that we use
for our remote/out-of-hours users.

There is currently an issue with at least one of our users' Outlook
connection. On his office laptop we have no problems - connections to
the Exchange server are perfectly fine. However, when connecting via
the TS, he encounters errors when sending and receiving, specifically
"Task - 'Microsoft Exchange Server - Sending and Receiving' reported
error (0x80040119) : 'Unknown error 0x80040119)".

Futher investigation reveals that there seems to be an issue with
cached Exchange mode - we have this enabled on the network computers. I
am aware that that OST's are not possible in a TS environment, but, if
I take a look at the mailbox settings from within Outlook 2003 (Tools >
Email Accounts), although greyed out the "Use cached Exchange mode" box
is ticked.

If, on the TS, I delete the Outlook mail profile, then recreate it,
then everything is fine again. However, after he's logged in again
locally from his laptop, the setting on the TS reverts. He needs OST's
on his laptop, so turning off caced Exchange on here is not an option.


Any ideas?


Thanks


Neil









.

Relevant Pages

  • Re: How Big is Big?
    ... I have been using Outlook 2003 in cached mode personally ... and find that it is also more aware of its connection state than 2002 and ... I have proposed that we upgrade at least all remote users to ...
    (microsoft.public.exchange2000.admin)
  • Cahced Exchange + Roaming profile = problems?
    ... apparently the default config for the Outlook 2003 client is to ... operate in cached Exchange mode. ... I *love* the new cached Exchange ... this only seems to occur on users with roaming profiles (70% of our ...
    (microsoft.public.windows.server.sbs)
  • outlook 2003 actions not updated in office when done remotely & vice versa
    ... We have Outlook 2003 at the office running in Cached Exchange Mode and ... Outlook through our Terminal Server (Remote Desktop connection not ... Terminal Server Outlook for security I presume. ...
    (microsoft.public.exchange.admin)
  • RE: Setting emails to be delivered at a later time on exchange 2003
    ... Outlook runs but not work as expected if the outlook does not start. ... The behavior is normal if your Outlook is running under the Cached Exchange ... In the Cached Exchange Mode, the Do Not Deliver Before" option only works ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: how can i secure my default mailbox in outlook 2003.
    ... I'd still say that there should be a way to run multiple outlook profiles ... with cached exchange under same windows login and have password protection ... Cached Exchange is needed to optimize speed of use. ... or her own user login. ...
    (microsoft.public.outlook.general)