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