SendTo Functionality

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

Guest

I've got Windows 2000 Terminal Services with users connecting using both thin clients and PCs with the Remote Desktop Client.

I've got one problem to which I've never found a solution. When my users are in Excel, Word, or any other app, for that matter, and want to send a file to an email recipient, if they hit File->SendTo->Mail Recipient, it locks their application on the server. It doesn't break any other sessions running on the server, but there's is locked. My only fix is to remotely kill the user's session and reset it, and then, when they get back in, everything works again

Any ideas here? I would like to simply remove this functionality, but I can't do that because my users are demanding it. Thanks for any help

Chris
 
What version of Office and did you install it properly, i.e. while in Application Server Mode, and install mode (change user /install or Add/Remove Programs). If it's Office 2000 did you use the transform (TERMSERV.MST) from the resource kit? Office XP & 2003 don't require a special transform to install on TS

What SP is the TS and Office

The reason I'm asking these "dumb" questions is because if the Office Suite is installed properly it shouldn't do what you're describing

http://www.microsoft.com/office/ork/2000/two/30t3.ht
http://www.microsoft.com/office/ork/xp/one/deph02.htm#sub_
http://www.microsoft.com/office/ork/2003/two/ch5/DepD06.ht
http://support.microsoft.com/default.aspx?kbid=83275

Patrick Rous
Micrsoft MVP - Terminal Serve
http://www.workthin.co

----- Chris Smith wrote: ----

I've got Windows 2000 Terminal Services with users connecting using both thin clients and PCs with the Remote Desktop Client.

I've got one problem to which I've never found a solution. When my users are in Excel, Word, or any other app, for that matter, and want to send a file to an email recipient, if they hit File->SendTo->Mail Recipient, it locks their application on the server. It doesn't break any other sessions running on the server, but there's is locked. My only fix is to remotely kill the user's session and reset it, and then, when they get back in, everything works again

Any ideas here? I would like to simply remove this functionality, but I can't do that because my users are demanding it. Thanks for any help

Chris
 
I had a similar problem a long time ago where I had
enabled NT's DLL security, and my mail program's DLL that
handled mailto functionality was being rejected. Are you
enforcing "Approved Shell Extensions" through group
policies?

-M
-----Original Message-----
What version of Office and did you install it properly,
i.e. while in Application Server Mode, and install mode
(change user /install or Add/Remove Programs). If it's
Office 2000 did you use the transform (TERMSERV.MST) from
the resource kit? Office XP & 2003 don't require a
special transform to install on TS.
What SP is the TS and Office?

The reason I'm asking these "dumb" questions is because
if the Office Suite is installed properly it shouldn't do
what you're describing.
http://www.microsoft.com/office/ork/2000/two/30t3.htm
http://www.microsoft.com/office/ork/xp/one/deph02.htm#sub_ 2
m
http://support.microsoft.com/default.aspx?kbid=832752

Patrick Rouse
Micrsoft MVP - Terminal Server
http://www.workthin.com

----- Chris Smith wrote: -----

I've got Windows 2000 Terminal Services with users
connecting using both thin clients and PCs with the Remote
Desktop Client.
I've got one problem to which I've never found a
solution. When my users are in Excel, Word, or any other
app, for that matter, and want to send a file to an email
recipient, if they hit File->SendTo->Mail Recipient, it
locks their application on the server. It doesn't break
any other sessions running on the server, but there's is
locked. My only fix is to remotely kill the user's
session and reset it, and then, when they get back in,
everything works again.
Any ideas here? I would like to simply remove this
functionality, but I can't do that because my users are
demanding it. Thanks for any help!
 
Patrick: This is Office XP installed using "change user /install". I'll verify that I'm using Office XP Service Pack 2...this may be part of the problem. I'm running Windows 2000 SP3 with all post-SP3 hotfixes. I've not installed SP4 because of problems that I've read regarding the service pack and Citrix/Terminal Services

Matthew: I just checked and I'm not enforcing "approved shell extensions only." I wish I was, because that would've been a quick fix.

I'll post tomorrow about the results after installed SP2 for Office XP. I'm quite sure that I've got it loaded already, but it's been awhile, so I don't remember off the top of my head

Thanks for the tips

Chris
 
Back
Top