If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Missing Office 2003 feature when installing on TS 2003
When installing Office 2003 Pro on Windows 2003 server running terminal
services, the Outlook component Visual Basic Scripting Support is missing from installation options. When terminal services are removed from the server the option is available during setup. I need scripting support badly for some custom Outlook forms, and it was working on Windows 2003 terminal services running Office 2000, so any help will be appreciated. Regards, Ole Thomsen |
#2
|
|||
|
|||
Missing Office 2003 feature when installing on TS 2003
It should be a matter of just copying a .dll from a non-TS installation. I
haven't seen it documented for OL2003, but believe it's the same issue as that described for OL2003 at http://www.slipstick.com/config/term...ver.htm#ol2002 -- Sue Mosher, Outlook MVP Author of Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx "Ole Thomsen" wrote in message ... When installing Office 2003 Pro on Windows 2003 server running terminal services, the Outlook component Visual Basic Scripting Support is missing from installation options. When terminal services are removed from the server the option is available during setup. I need scripting support badly for some custom Outlook forms, and it was working on Windows 2003 terminal services running Office 2000, so any help will be appreciated. Regards, Ole Thomsen |
#3
|
|||
|
|||
Missing Office 2003 feature when installing on TS 2003
You're probably thinking of this
http://support.microsoft.com/default...;en-us;Q302003 It does not solve the problem. I've been advised to try the OVERRIDETERMINALSERVER=1 parameter doing a new install, and that will be my next step. Ole Thomsen Sue Mosher [MVP-Outlook] wrote: It should be a matter of just copying a .dll from a non-TS installation. I haven't seen it documented for OL2003, but believe it's the same issue as that described for OL2003 at http://www.slipstick.com/config/term...ver.htm#ol2002 "Ole Thomsen" wrote in message ... When installing Office 2003 Pro on Windows 2003 server running terminal services, the Outlook component Visual Basic Scripting Support is missing from installation options. When terminal services are removed from the server the option is available during setup. I need scripting support badly for some custom Outlook forms, and it was working on Windows 2003 terminal services running Office 2000, so any help will be appreciated. Regards, Ole Thomsen |
#4
|
|||
|
|||
Missing Office 2003 feature when installing on TS 2003
Yes, that's exactly what I was thinking of. Let use know if that setup
option solves the problem and any fallout it incurs. -- Sue Mosher, Outlook MVP Author of Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx "Ole Thomsen" wrote in message ... You're probably thinking of this http://support.microsoft.com/default...;en-us;Q302003 It does not solve the problem. I've been advised to try the OVERRIDETERMINALSERVER=1 parameter doing a new install, and that will be my next step. Ole Thomsen Sue Mosher [MVP-Outlook] wrote: It should be a matter of just copying a .dll from a non-TS installation. I haven't seen it documented for OL2003, but believe it's the same issue as that described for OL2003 at http://www.slipstick.com/config/term...ver.htm#ol2002 "Ole Thomsen" wrote in message ... When installing Office 2003 Pro on Windows 2003 server running terminal services, the Outlook component Visual Basic Scripting Support is missing from installation options. When terminal services are removed from the server the option is available during setup. I need scripting support badly for some custom Outlook forms, and it was working on Windows 2003 terminal services running Office 2000, so any help will be appreciated. Regards, Ole Thomsen |
#5
|
|||
|
|||
Missing Office 2003 feature when installing on TS 2003
OVERRIDETERMINALSERVER=1 did the trick.
As we're using an AD managed installation of Office which is also running on PC's and laptops, I chose not to alter the installpoint and do a new install. Instead I ran setup/update with the above switch on the terminalservers, adding Outlook support for scripting to the existing Office. This works fine. Ole Thomsen Sue Mosher [MVP-Outlook] wrote: Yes, that's exactly what I was thinking of. Let use know if that setup option solves the problem and any fallout it incurs. "Ole Thomsen" wrote in message ... You're probably thinking of this http://support.microsoft.com/default...;en-us;Q302003 It does not solve the problem. I've been advised to try the OVERRIDETERMINALSERVER=1 parameter doing a new install, and that will be my next step. Ole Thomsen Sue Mosher [MVP-Outlook] wrote: It should be a matter of just copying a .dll from a non-TS installation. I haven't seen it documented for OL2003, but believe it's the same issue as that described for OL2003 at http://www.slipstick.com/config/term...ver.htm#ol2002 "Ole Thomsen" wrote in message ... When installing Office 2003 Pro on Windows 2003 server running terminal services, the Outlook component Visual Basic Scripting Support is missing from installation options. When terminal services are removed from the server the option is available during setup. I need scripting support badly for some custom Outlook forms, and it was working on Windows 2003 terminal services running Office 2000, so any help will be appreciated. Regards, Ole Thomsen |
#6
|
|||
|
|||
Missing Office 2003 feature when installing on TS 2003
OVERRIDETERMINALSERVER=1 did the trick.
As we're using an AD managed installation of Office which is also running on PC's and laptops, I chose not to alter the installpoint and do a new install. Instead I ran setup/update with the above switch on the terminalservers, adding Outlook support for scripting to the existing Office. This works fine. Ole Thomsen Sue Mosher [MVP-Outlook] wrote: Yes, that's exactly what I was thinking of. Let use know if that setup option solves the problem and any fallout it incurs. "Ole Thomsen" wrote in message ... You're probably thinking of this http://support.microsoft.com/default...;en-us;Q302003 It does not solve the problem. I've been advised to try the OVERRIDETERMINALSERVER=1 parameter doing a new install, and that will be my next step. Ole Thomsen Sue Mosher [MVP-Outlook] wrote: It should be a matter of just copying a .dll from a non-TS installation. I haven't seen it documented for OL2003, but believe it's the same issue as that described for OL2003 at http://www.slipstick.com/config/term...ver.htm#ol2002 "Ole Thomsen" wrote in message ... When installing Office 2003 Pro on Windows 2003 server running terminal services, the Outlook component Visual Basic Scripting Support is missing from installation options. When terminal services are removed from the server the option is available during setup. I need scripting support badly for some custom Outlook forms, and it was working on Windows 2003 terminal services running Office 2000, so any help will be appreciated. Regards, Ole Thomsen |
#7
|
|||
|
|||
"Ole Thomsen" wrote in message ...
OVERRIDETERMINALSERVER=1 did the trick. As we're using an AD managed installation of Office which is also running on PC's and laptops, I chose not to alter the installpoint and do a new install. Instead I ran setup/update with the above switch on the terminalservers, adding Outlook support for scripting to the existing Office. This works fine. Ole Thomsen Sue Mosher [MVP-Outlook] wrote: Yes, that's exactly what I was thinking of. Let use know if that setup option solves the problem and any fallout it incurs. "Ole Thomsen" wrote in message ... You're probably thinking of this http://support.microsoft.com/default...;en-us;Q302003 It does not solve the problem. I've been advised to try the OVERRIDETERMINALSERVER=1 parameter doing a new install, and that will be my next step. Ole Thomsen Sue Mosher [MVP-Outlook] wrote: It should be a matter of just copying a .dll from a non-TS installation. I haven't seen it documented for OL2003, but believe it's the same issue as that described for OL2003 at http://www.slipstick.com/config/term...ver.htm#ol2002 "Ole Thomsen" wrote in message ... When installing Office 2003 Pro on Windows 2003 server running terminal services, the Outlook component Visual Basic Scripting Support is missing from installation options. When terminal services are removed from the server the option is available during setup. I need scripting support badly for some custom Outlook forms, and it was working on Windows 2003 terminal services running Office 2000, so any help will be appreciated. Regards, Ole Thomsen Hello, Can you tell me what steps to do to use the OVERRIDETERMINALSERVER=1. Not sure exactly how to use this. I am having the same problem that you were having on a Windows 2003 server. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Office 2003 / Office XP Shortcut Bar | Marc Bressman | General Discussions | 6 | June 26th, 2004 08:42 AM |
Upgrade 03 Trial to Full | Tom | Publisher | 2 | June 4th, 2004 12:18 AM |
MSI installer runs when I run Office 2003 app | Ralph Sharett | Setup, Installing & Configuration | 1 | May 27th, 2004 07:58 AM |
Office 2003 deployment w/o volume key | Ulrich Wurst | Setup, Installing & Configuration | 2 | May 19th, 2004 06:39 PM |
Office 2003 and Office 2000/97 coexist on same PC? | John | General Discussions | 3 | May 6th, 2004 12:36 PM |