Outlook 2010 on Terminal Server

[hungrybeaver]

I've been looking around for a fix or registry hack for a while now that allows Outlook 2007 to enable cached-mode on a terminal server. It seems that Microsoft disabled this feature because of the load on the TS if pst and/or ost files are stored locally. I kinda see where they're coming from but still, some environments have enough resources or are remote enough to warrant local mail stores. At least give me the option dammit!

I hear that Outlook 2010 has cached-mode enabled (or at least it can be enabled) when creating a users profile. Has anyone here successfully installed Outlook 2010 with cached-mode enabled on a TS? Did you come across any problems? Has the load on the network/server increased significantly?

I'm looking at doing this for 20 or so users, so if any of guys have done this I'd really like to hear if you encountered any issues during the install/configuration process.

 

[bubbatentoe]

You're a brave man to run a mission critical resource hungry service like Exchange 2010 under TS + have clients run in cached mode.
LOL.
I hope you have a HUGE server + lots of hard drive space + super fast RAID/NAS + fast connections to your clients.

or there will be tears.


MS doesn't recommend it, see here: http://technet.microsoft.com/en-us/library/ff945789.aspx

Enable cached mode for TS clients by following this:
http://uksbsguy.com/blogs/doverton/...server-which-means-that-bcm-can-work-too.aspx

never done it myself (too scared)
**running Exchange 2010 on a Proliant 580 with 4 x quad core 2.8's & 21 Gb RAM with 1.5TB on RAID1 and RAID6. (15K RPM SAS drives)


Best of luck,.

 

[TheGuy]

Doesn't look like he is running Exchange on the TS otherwise there will no need to enable cached exchange mode.