integrating office in terminal services

  • Thread starter Thread starter cfiller
  • Start date Start date
C

cfiller

Guest
I had to reinstall office on terminal services to fix an integration issue
with another package. Now that I've done that users can't sign on remotely
and run office - it says you need to be an administrator to install software.
If I have the user sign directly on to the server, then I can open an office
application and it does the little office install that is needed. Once this
is done, office works fine when they sign on remotely. I can't have all
users sign on to the server directly - how can I get this to work properly?
BTW I did do the install from the add/remove programs - as recommended.
 
Re: integrating office in terminal services

You can post this question in following news groups,
microsoft.public.office.misc and
microsoft.public.office.setup

Ratnesh

"cfiller" <cfiller@discussions.microsoft.com> wrote in message
news:166E3DA2-FE44-48F9-B0AB-22F456D0098B@microsoft.com...
>I had to reinstall office on terminal services to fix an integration issue
> with another package. Now that I've done that users can't sign on
> remotely
> and run office - it says you need to be an administrator to install
> software.
> If I have the user sign directly on to the server, then I can open an
> office
> application and it does the little office install that is needed. Once
> this
> is done, office works fine when they sign on remotely. I can't have all
> users sign on to the server directly - how can I get this to work
> properly?
> BTW I did do the install from the add/remove programs - as recommended.
 
Re: integrating office in terminal services

Check following links for Best Pratice for Software installation under TS
enviroment
http://technet2.microsoft.com/windo...ec28-4d62-b1d5-79c4bd544b361033.mspx?mfr=true

Ratnesh

"cfiller" <cfiller@discussions.microsoft.com> wrote in message
news:166E3DA2-FE44-48F9-B0AB-22F456D0098B@microsoft.com...
>I had to reinstall office on terminal services to fix an integration issue
> with another package. Now that I've done that users can't sign on
> remotely
> and run office - it says you need to be an administrator to install
> software.
> If I have the user sign directly on to the server, then I can open an
> office
> application and it does the little office install that is needed. Once
> this
> is done, office works fine when they sign on remotely. I can't have all
> users sign on to the server directly - how can I get this to work
> properly?
> BTW I did do the install from the add/remove programs - as recommended.
 
Re: integrating office in terminal services

The information you referenced was helpful in providing a better
understanding of Terminal Services, but it didn't answer my specific problem.
I still need to have users sign directly on to the server itself before I
can successfully set up Outlook.

"Ratnesh Yadav [MSFT]" wrote:

> Check following links for Best Pratice for Software installation under TS
> enviroment
> http://technet2.microsoft.com/windo...ec28-4d62-b1d5-79c4bd544b361033.mspx?mfr=true
>
> Ratnesh
>
> "cfiller" <cfiller@discussions.microsoft.com> wrote in message
> news:166E3DA2-FE44-48F9-B0AB-22F456D0098B@microsoft.com...
> >I had to reinstall office on terminal services to fix an integration issue
> > with another package. Now that I've done that users can't sign on
> > remotely
> > and run office - it says you need to be an administrator to install
> > software.
> > If I have the user sign directly on to the server, then I can open an
> > office
> > application and it does the little office install that is needed. Once
> > this
> > is done, office works fine when they sign on remotely. I can't have all
> > users sign on to the server directly - how can I get this to work
> > properly?
> > BTW I did do the install from the add/remove programs - as recommended.
>
 
Re: integrating office in terminal services

Which version of Office?
Have you checked the EventLog on the server?
Check if this helps:

911682 - Windows Installer-related event IDs are logged in the
Application log when you start an Office program
http://support.microsoft.com/?kbid=911682

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Y2ZpbGxlcg==?= <cfiller@discussions.microsoft.com> wrote
on 29 apr 2008 in microsoft.public.windows.terminal_services:

> The information you referenced was helpful in providing a better
> understanding of Terminal Services, but it didn't answer my
> specific problem.
> I still need to have users sign directly on to the server
> itself before I
> can successfully set up Outlook.
>
> "Ratnesh Yadav [MSFT]" wrote:
>
>> Check following links for Best Pratice for Software
>> installation under TS enviroment
>> http://technet2.microsoft.com/windowsserver/en/library/7c5ff862-
>> ec28-4d62-b1d5-79c4bd544b361033.mspx?mfr=true
>>
>> Ratnesh
>>
>> "cfiller" <cfiller@discussions.microsoft.com> wrote in message
>> news:166E3DA2-FE44-48F9-B0AB-22F456D0098B@microsoft.com...
>> >I had to reinstall office on terminal services to fix an
>> >integration issue
>> > with another package. Now that I've done that users can't
>> > sign on remotely
>> > and run office - it says you need to be an administrator to
>> > install software.
>> > If I have the user sign directly on to the server, then I can
>> > open an office
>> > application and it does the little office install that is
>> > needed. Once this
>> > is done, office works fine when they sign on remotely. I
>> > can't have all users sign on to the server directly - how can
>> > I get this to work properly?
>> > BTW I did do the install from the add/remove programs - as
>> > recommended.
 
Back
Top