Windows installer pops up ever time i try accessing my app. over T

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Windows installer pops up ever time i try accessing my app. over TS

Hi All,

windows 2000 terminal server, service Pack4
Has Sql server 2000 and Office 2000 installed on it.

Users log into the server with their windows account and in the user;s
peroperties profiles tab for these users, i have specifed that the OS takes
them straight to my application (which is done in VB6), i.e they do not even
get the desktop.

All these users are part of the local Users group.

Now this setup works perfect except that when the users log into the
Operating System over TS, they get this Microsoft Office 2000 installer popup
with the progress bar gong from left to right and then pops up and error and
the progress bar goes left to right, dont remember the errror word to word
but it tries installing offfice from the CD and fails since there is no CD in
the CD drive. This nonsense keeps happening until i click on Cancel several
times.

Funny part is that it does not happen when i am logged in as an
Administrator with access to the desktop, which makes me think if this that
there are two reason for this issue, 1 . permissions, 2. access to only the
application. the application does not have any thing to do with outlook. Out
of all the machines that i have installed with this envriorment it is only
this machine which pops up the office 2000 windows installer ever time i log
into my applciation over Terminal Services.

Can anybody shed some light on this issue for me! thanks
Is this some kind of registry setting or some option that i can disable.

thanks
muzammil
 
Reinstall office from a folder on the network that all users have read
access to !MAKE SURE THAT IT IS A UNC PATH, NOT A MAPPED DRIVE
(\\SERVER\PATH\OFFICE2K)!!!!. When installing, choose to "Run All
Features from My Hard Drive". When your clients login to the terminal
server, the office installer will still start but won't try to install
anything that the users don't have rights to install and if the CD is
needed, the office install will go back to the path it was originally
installed from first to update whatever components it needs to update.
Why having the install files available is a requsite for office, I
can't answer - but following the above steps works for me every time.

Note: Make ABSOLUTELY sure that your users don't have administrative
rights to the server, if they do this method could lead to them
breaking the office install - but it is easily repairable if they do...
If anyone else has a better suggestion, I am all ears.
 
Back
Top