[THIN] Re: Trend Scanmail 7 Outlook Spam folder error
- From: "Jim Kenzig ThinHelp.com" <jkenzig@xxxxxxxxx>
- To: THIN <thin@xxxxxxxxxxxxx>
- Date: Tue, 16 Jan 2007 14:16:06 -0500
By the way here is the MS KB article refered to below. Appears it will
apply to Office 2007 also and the KB is updated as of Jan 2, 2007
Forms with VBScript do not work with Terminal Services in Outlook View
products that this article applies
to.<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#appliesto>
Article ID : 302003 Last Review : January 2, 2007 Revision : 3.0
This article was previously published under Q302003
On This Page [image:
SYMPTOMS]SYMPTOMS<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#>
[image:
CAUSE]CAUSE<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#>
[image:
WORKAROUND]WORKAROUND<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#>
[image:
Method 1: Copy the Outlvbs.dll file to existing installations]Method 1: Copy
the Outlvbs.dll file to existing installations
<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#>
[image: Method 2: Use the Custom Installation Wizard to deploy Microsoft
Office with an additional property to let the VBScript component to be
installed]Method 2: Use the Custom Installation Wizard to deploy Microsoft
Office with an additional property to let the VBScript component to be
installed <http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#>
[image:
STATUS]STATUS<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#>
[image: MORE INFORMATION]MORE
INFORMATION<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#>
SYMPTOMS If you are using Microsoft Outlook in a Terminal Services
environment, you cannot use Visual Basic Scripting Edition (VBScript) in
custom Outlook forms. This issue can occur when you are using Microsoft
Windows NT 4.0 Terminal Server in Install mode or User mode. This issue also
occurs with Windows 2000 Terminal Server in Application mode but not in
Remote Administration mode. [image: Back to the
top]<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
Back
to the top<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
CAUSE By default, Microsoft Office XP, Microsoft Office 2003, and Microsoft
2007 Office programs do not install the VBScript component in Windows
Terminal Server environments. [image: Back to the
top]<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
Back
to the top<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
WORKAROUND Use one of the following methods to work around this
problem. [image:
Back to the
top]<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
Back
to the top<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
Method 1: Copy the Outlvbs.dll file to existing installations To do this,
follow these steps: 1. Copy the Outlvbs.dll file from a computer that is
not running Microsoft Outlook on a Terminal Server. 2. Copy the
Outlvbs.dllfile to the Program Files\Microsoft Office\Office10 folder
of the affected
Terminal Server computer.
*Note* If the Terminal Server is running Microsoft Office 2003, copy the
Outlvbs.dll file to the Program Files\Microsoft Office\Office11 folder. If
the Terminal Server is running 2007 Microsoft Office programs, copy the
Outlvbs.dll file to the Program Files\Microsoft Office\Office12
folder. [image:
Back to the
top]<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
Back
to the top<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
Method 2: Use the Custom Installation Wizard to deploy Microsoft Office with
an additional property to let the VBScript component to be installedTo do
this, follow these steps: 1. Open the Custom Installation Wizard, and then
create a new transform (.MST) file for the Microsoft Office installation.
2. Configure your installation requirement in the Custom Installation
Wizard. 3. On the last available page of the Custom Installation Wizard,
click *Modify Setup Properties*, and then add the following property name
and value:
Property Name: WTSDISABLED
Value: MsInfoFiles,PPTCastCoreFiles
*Note* both the property name and the value are case sensitive.
For Office XP, *Modify Setup Properties* is on page 21 of 22 of the Custom
Installation Wizard. For Office 2003, *Modify Setup Properties* is on page
23 of 24 of the Custom Installation Wizard. [image: Back to the
top]<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
Back
to the top<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
STATUS Microsoft has confirmed that this is a problem in the Microsoft
products that are listed in the "Applies to" section. [image: Back to the
top] <http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top> Back
to the top<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
MORE INFORMATION Microsoft Office and Outlook Setup detect when you are
installing Outlook on a computer configured with Terminal Services. In these
situations, the support files necessary to enable VBScript in Outlook custom
forms are not installed. Therefore, if you try to start the Outlook Script
Editor, you receive the following error message: Unable to load this
feature. Feature ID not registered.
If you try to use a custom Outlook form that contains VBScript, you do not
receive an error message, but the VBScript code in the form does not run.
*NOTE*: Earlier versions of Outlook supported VBScript in a Terminal
Services environment.
For more information about available resources and answers to commonly asked
questions about Microsoft Outlook solutions, click the following article
number to view the article in the Microsoft Knowledge Base:
287530<http://support.microsoft.com/kb/287530/>(
http://support.microsoft.com/kb/287530/) Frequently asked questions about
custom forms and Outlook solutions
[image: Back to the
top]<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
Back
to the top<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003#top>
------------------------------
APPLIES TO • Microsoft Office Outlook 2007 • Microsoft Office Outlook 2003
• Microsoft Outlook 2002 Standard Edition, when used with: Microsoft
Windows Server 2003, Standard Edition (32-bit x86) Microsoft Windows
Server 2003, Enterprise Edition (32-bit x86) Microsoft Windows 2000
Server Microsoft Windows NT Server 4.0, Terminal Server Edition
On 1/16/07, Jim Kenzig ThinHelp.com <jkenzig@xxxxxxxxx> wrote:
Hi folks,
We just got around to upgrading to Trend Scanmail 7 for our exchange
server and it added a Spam folder to out TS Outlook 2003 users folder and
puts spam messages there. If a user gets a non spam message and wants to
flag the user as a safe send they get an error message that reads " *There
must be at least one name in the "To" or "CC" or "BCC" fields* when
adding the sender to approved sender on the list. . Apparently a DLL file
Outlvbs.dll needs to be copied over to the Terminal server Office11 folder
(for 2003) in orger for this to work. I wanted to document this someplace as
a search on the web via google did not find this for me. here is the Trend
KB article on it.
JK
ScanMail for Exchange (SMEX) 7.0 Approved Senders List on Terminal
Server clients appear as normal emails *Solution ID:* 127258
*A recent system upgrade added a '1' or '2' to old solution IDs. You find
these solutions by removing or retaining the extra '1' or '2'.* *
Product:* ScanMail for Exchange - 7.0 2000/2003 *Operating System:*
Windows
2000 Server, Windows XP *Published:* 12/7/05 3:08 PM
*Problem:*
After installing SMEX 7.0 on a Terminal Server with Outlook 2002/2003, the
Spam Mail folder and the Approved Senders List appear on the user's mailbox.
However, upon opening the Approved Sender List management form, it appears
like a normal email instead of a form. Also, the message *There must be at
least one name in the "To" or "CC" or "BCC" fields* appears when adding
approved sender on the list.
The Approved Senders List appears like
Click
*here*<http://solutionfile.trendmicro.com/imageFile/27258/Approved-bad_big.gif>to
see a bigger image.
instead of the following:
Click
*here*<http://solutionfile.trendmicro.com/imageFile/27258/Approved-good_big.gif>to
see a bigger image.
The issue does not occur if the client is using standard standalone
Microsoft Outlook 2002/2003.
*Solution:*
The issue occurs when installing Outlook 2002/2003 on a machine that is
running Terminal Services, which does not have a copy of the file that
Outlook needs to run custom forms.
To resolve the issue:
1. Go to a client that is also running Outlook 2002/2003.
2. Go to ..\Program Files\Microsoft Office\Office10 and look for the
Outlvbs.dll file.
3. Copy the file to the ..\Office10 directory of the Terminal Server
client.
For more information, refer to *Forms with VBScript do not work with
Terminal Services in Outlook 2002 and in Outlook
2003<http://support.microsoft.com/default.aspx?scid=kb;en-us;302003>
* .
--
Jim Kenzig
Microsoft MVP - Terminal Services
http://www.thinhelp.com
Citrix Technology Professional
Provision Networks VIP
CEO The Kenzig Group
http://www.kenzig.com
Blog: http://www.techblink.com
--
Jim Kenzig
Microsoft MVP - Terminal Services
http://www.thinhelp.com
Citrix Technology Professional
Provision Networks VIP
CEO The Kenzig Group
http://www.kenzig.com
Blog: http://www.techblink.com
Other related posts:
