Missing Office 2003 feature when installing on TS 2003

[Ole Thomsen]

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

 

[Sue Mosher [MVP-Outlook]]

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/terminalserver.htm#ol2002

 

[Sue Mosher [MVP-Outlook]]

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/terminalserver.htm#ol2002

 

[Sue Mosher [MVP-Outlook]]

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/terminalserver.htm#ol2002

 

[Sue Mosher [MVP-Outlook]]

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/terminalserver.htm#ol2002

 

[Sue Mosher [MVP-Outlook]]

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/terminalserver.htm#ol2002

 

[Sue Mosher [MVP-Outlook]]

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/terminalserver.htm#ol2002

 

[Sue Mosher [MVP-Outlook]]

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/terminalserver.htm#ol2002

 

[Sue Mosher [MVP-Outlook]]

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/terminalserver.htm#ol2002

 

[Sue Mosher [MVP-Outlook]]

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/terminalserver.htm#ol2002

 

[Ole Thomsen]

You're probably thinking of this
http://support.microsoft.com/default.aspx?scid=kb;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

 

[Ole Thomsen]

You're probably thinking of this
http://support.microsoft.com/default.aspx?scid=kb;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

 

[Ole Thomsen]

You're probably thinking of this
http://support.microsoft.com/default.aspx?scid=kb;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

 

[Ole Thomsen]

You're probably thinking of this
http://support.microsoft.com/default.aspx?scid=kb;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

 

[Ole Thomsen]

You're probably thinking of this
http://support.microsoft.com/default.aspx?scid=kb;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

 

[Ole Thomsen]

You're probably thinking of this
http://support.microsoft.com/default.aspx?scid=kb;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

 

[Ole Thomsen]

You're probably thinking of this
http://support.microsoft.com/default.aspx?scid=kb;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

 

[Ole Thomsen]

You're probably thinking of this
http://support.microsoft.com/default.aspx?scid=kb;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

 

[Ole Thomsen]

You're probably thinking of this
http://support.microsoft.com/default.aspx?scid=kb;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]]

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