I was thinking of leaving him with his file server, TS and everything else, but just using google apps for email. 2009/8/26 Evan Mann <emann@xxxxxxxxxxxxxx> > I’m way ahead of you there. Looked at Google Apps first. He didn’t like > the way Google Docs worked. Also looked at Sharepoint, didn’t like that > either. At the end of the day, he is set in his ways and likes accessing > his files on his local LAN through windows. It’s fast, he’s done it that > way for 6 years, and he doesn’t want to have to change that for himself. > Changing the user is the hardest thing. > > > > I discussed full cloud, but he doesn’t like the fact that he’d be in the > cloud and his speed of working would be effected. He also has some “big > brother” issues that I’ve been working on for the past 2 years. He’s > finally going to agree to online backup, but it took 2 years of recommending > it. Having him work entirely in the cloud would probably never materialize. > > > > *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Greg Reese > *Sent:* Wednesday, August 26, 2009 9:37 AM > *To:* thin@xxxxxxxxxxxxx > *Subject:* [THIN] Re: Outlook Exchange Cached Mode > > > > This is exactly the type of business that Google Apps for business was > designed for. legitimate email, cloud storage. Surprised that doesn't work > better. > > > As for cached exchange mode, I don't know of any other hacks to try. You > could slap together something with VDI but you would be introducing a level > of complexity that overshadows the benefits. > > Greg > > On Wed, Aug 26, 2009 at 8:27 AM, Evan Mann <emann@xxxxxxxxxxxxxx> wrote: > > I’m supporting a small home based HVAC business that has a 2008 Terminal > Server so a few field employees can connect in remotely to access a > repository of documents. They want to legitimize themselves on e-mail and > stop using yahoo/gmail/ISP e-mails. I’ve signed them up for a Hosted > Exchange service but ran into a problem last night. No cached exchange mode > in Terminal Server due to the disabling of support for OST files (and > offline files in general) > > > > Quick search, yes, disabled on purpose by MS. Lots of potential hacks, > none of them work. I tried a few things of my own, but no go. I know the > reasons for disabling OST, but none of them are concerns for this small > business who has 3 users who use terminal server. Moving to in house e-mail > is not an option. > > > > Hosted Exchange without cached mode is simply not usable. Most e-mails > contain a minimum attachment size of 1 MB and even working through text only > e-mails in the mailbox is painfully slow. Moving e-mail in house is not a > viable option. The best I can do is setup these users for IMAP, but they > lose all the collaboration benefits. Some would consider the simply fix is > to deploy Outlook Anywhere to their local desktop, but that doesn’t do much > good when 99% of their e-mailing requirements saving/attaching of company > documents, only available on the terminal server. > > > > There is no budget to spend more money to change the way things work. So > I’m out of ideas. Does anyone know of some ”inside” info to enable > OST/Cached Mode support on 2008 TS? > > > > > > > > > > > > > > >