Archived from groups: microsoft.public.windowsnt.terminalserver.setup (More info?)

I have an application which I would like to serve out using Terminal Server,
but a key aspect of the application is that it can export data to Excel
using OLE.

Is there a way of making TS use the client's installation of Excel, rather
than having to have it on the TS machine. I really don't want to have to
serve out Office, since this is bound to be incredibly expensive!

TIA
Graeme

Archived from groups: microsoft.public.windowsnt.terminalserver.setup (More info?)

No, not with native Terminal Services. Citrix supports this, it's
called "content redirection". But talking about expensive...:-)

On the other hand, deploying Office on your Terminal Server
shouldn't cost you anything at all license-wise, provided that your
clients already have a locally installed and properly licensed
version of Office.
The rule for Office licenses is: one client, one license. And it
doesn't matter if the client runs Office locally or through a TS.
Documented here:

Licensing Microsoft Office in a Windows Terminal Server Environment
http://www.microsoft.com/windows20 [...] ing/licens
office.asp

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"Graeme Neath" <graeme@whatever.com> wrote on 26 maj 2005 in
microsoft.public.windowsnt.terminalserver.setup:

> I have an application which I would like to serve out using
> Terminal Server, but a key aspect of the application is that it
> can export data to Excel using OLE.
>
> Is there a way of making TS use the client's installation of
> Excel, rather than having to have it on the TS machine. I really
> don't want to have to serve out Office, since this is bound to
> be incredibly expensive!
>
> TIA
> Graeme

Archived from groups: microsoft.public.windowsnt.terminalserver.setup (More info?)

Excellent news re: Office licensing.

Many thanks!
Graeme


"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9662F27ED4B1Averanoesthemutforsse@207.46.248.16...
> No, not with native Terminal Services. Citrix supports this, it's
> called "content redirection". But talking about expensive...:-)
>
> On the other hand, deploying Office on your Terminal Server
> shouldn't cost you anything at all license-wise, provided that your
> clients already have a locally installed and properly licensed
> version of Office.
> The rule for Office licenses is: one client, one license. And it
> doesn't matter if the client runs Office locally or through a TS.
> Documented here:
>
> Licensing Microsoft Office in a Windows Terminal Server Environment
> http://www.microsoft.com/windows20 [...] ing/licens
> office.asp
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> "Graeme Neath" <graeme@whatever.com> wrote on 26 maj 2005 in
> microsoft.public.windowsnt.terminalserver.setup:
>
>> I have an application which I would like to serve out using
>> Terminal Server, but a key aspect of the application is that it
>> can export data to Excel using OLE.
>>
>> Is there a way of making TS use the client's installation of
>> Excel, rather than having to have it on the TS machine. I really
>> don't want to have to serve out Office, since this is bound to
>> be incredibly expensive!
>>
>> TIA
>> Graeme