Support for Terminal Services and Citrix Presentation servers

Support for Terminal Services and Citrix Presentation servers

  • Article ID:100016635
  • Last Published:
  • Product(s):Enterprise Vault

Problem

Veritas provides client support for Citrix based thin client provisioning. This support is limited to the installation and use of the Enterprise Vault client for Outlook, excluding Vault Cache or Virtual Vault. Support for Vault Cache and Virtual Vault is included only if the criteria specified in the Enterprise Vault Compatibility List are satisfied.

Veritas does not currently support any aspect of its Enterprise Vault server infrastructure provisioned via Citrix.

The Enterprise Vault (EV) client can be made available to users with Terminal Services; however, there are some outstanding issues to be aware of.  

Error Message

  • Microsoft Outlook 2007, 2010 and 2013

    The following errors are generated:

    Cannot enable support for scripting. The functionality is not available.

    Microsoft Office Outlook cannot provide form scripting support.  This feature is not available.
     
  • Microsoft Outlook 2003

    If Outlook 2003 is installed on the Terminal server, nothing happens when the user double clicks on an archived item to attempt to view it.

Solution

Outlook 2003:

1) Refer to the following Microsoft article to troubleshoot VBScript issues when using Terminal Services in Outlook:

Forms with VBScript do not work with Terminal Services in Outlook
https://support.microsoft.com/default.aspx?scid=kb;en-us;302003

2) If after following the above Microsoft KB the issue is still present then the additional step below may be required.

a. Open regedit on the Citrix or Terminal Server 

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes

b. Browse to the following location:

    HKEY_CLASSES_ROOT\Installer\Features\9040210900063D11C8EF00054038389C

c. Remove the DWORD OutlookVBScript

d. Close regedit

 

    Outlook 2007, 2010 and 2013:

    VBScript support for Outlook forms is not allowed by default on a Terminal Service installation. This default setting cannot be changed or added using the add-remove program wizard.

    NOTE : To install the required VB Script functionality, the GUID of the installed package must be known. Ie. Microsoft Office Outlook 2007 or Microsoft Office Professional Plus 2007

    To obtain the GUID of the installed package and then install the VB Script functionality, perform the following:
    1. Verify the product name from Add/Remove programs or the Help > About menu
    2. Open the registry, browse to:

      For 32-bits OS version:
      HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Uninstall

      For 64-bits OS version:
      HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

    3. Identify the GUID as per Microsoft KB 928516 (e.g. {90120000-0030-0000-0000-0000000FF1CE} )

      Office 2007 - https://support.microsoft.com/kb/928516
      Office 2010 - https://support.microsoft.com/kb/2186281
      Office 2013 - https://support.microsoft.com/kb/2786054
            
    4. From command prompt, enter the following syntax: It is case sensitive.

      msiexec /i {GUID.EN_US} ADDLOCAL=OutlookVBScript /qb

      where {GUID.EN_US} is the string identified in step 3 above.

      Examples for common versions of Office:

      Microsoft Office Professional Plus 2007:
      msiexec /i {90120000-0011-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Standard 2007:
      msiexec /i {90120000-0012-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Basic 2007:
      msiexec /i {90120000-0013-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Professional 2007:
      msiexec /i {90120000-0014-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Enterprise 2007:
      msiexec /i {90120000-0030-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Professional Plus 2010:
      msiexec /i {90140000-0011-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Standard 2010:
      msiexec /i {90140000-0012-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Basic 2010:
      msiexec /i {90140000-0013-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Professional 2010:
      msiexec /i {90140000-0014-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Enterprise 2010:
      msiexec /i {90140000-0030-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Professional Plus 2013:
      msiexec /i {90150000-0011-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Standard 2013:
      msiexec /i {90150000-0012-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Home and Business 2013:
      msiexec /i {90150000-0013-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

      Microsoft Office Professional 2013:
      msiexec /i {90150000-0014-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb 
       

    Note: There have been some instances reported where this did not resolve the problem.  In those cases delete the OUTLVBS.DLL file from the Microsoft Office installation folder and try running the MSIEXEC command again.

    Was this content helpful?