Why can't Outlook provide form script support?

 
 

When you start Microsoft Outlook 2010 or 2013 in a Terminal Server environment, the following message appears: "Outlook cannot provide vb script support".

The XPhone Connect Client requires the VB script support for the integration in Outlook. It is usually not installed in the Office versions 2013 and 2010 by the Outlook standard set-up but can be added with the msiexec /i {GUID} ADDLOCAL=OutlookVBScript /qb command. Here, <GUID> is the GUID of the Outlook MSI package. You can find it in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Common\InstalledPackages

msiexec /i {<GUID>} ADDLOCAL=OutlookVBScript /qb


When using Microsoft Office x86 on Windows x64, the registry keys listed are located under the key HKEY_LOCAL_MACHINE\SOFTWARE\ Wow6432Node\.

Microsoft Office 2010 product series

  • Office 2010 Professional Plus x86 Retail / OEM
    msiexec /i {91140000-0011-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Professional Plus x64 Retail / OEM
    msiexec /i {91140000-0011-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Professional Plus x86 Volume license
    msiexec /i {90140000-0011-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Professional Plus x64 Volume license
    msiexec /i {90140000-0011-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Standard x86 Retail / OEM
    msiexec /i {91140000-0012-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Standard x64 Retail / OEM
    msiexec /i {91140000-0012-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Standard x86 Volume license
    msiexec /i {90140000-0012-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Standard x64 Volume license
    msiexec /i {90140000-0012-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Professional x86 Retail / OEM
    msiexec /i {91140000-0014-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Professional x64 Retail / OEM
    msiexec /i {91140000-0014-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Professional x86 Volume license
    msiexec /i {90140000-0014-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Professional x64 Volume license
    msiexec /i {90140000-0014-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Enterprise x86
    msiexec /i {90140000-0030-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2010 Enterprise x64
    msiexec /i {90140000-0030-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb

Microsoft Office 2013 product series

  • Office 2013 Professional Plus x86 Retail / OEM
    msiexec /i {91150000-0011-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Professional Plus x64 Retail / OEM
    msiexec /i {91150000-0011-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Professional Plus x86 Volume license
    msiexec /i {90150000-0011-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Professional Plus x64 Volume license
    msiexec /i {90150000-0011-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Standard x86 Retail / OEM
    msiexec /i {91150000-0012-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Standard x64 Retail / OEM
    msiexec /i {91150000-0012-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Standard x86 Volume license
    msiexec /i {90150000-0012-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Standard x64 Volume license
    msiexec /i {90150000-0012-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Professional x86 Retail / OEM
    msiexec /i {91150000-0014-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Professional x64 Retail / OEM
    msiexec /i {91150000-0014-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Professional x86 Volume license
    msiexec /i {90150000-0014-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Professional x64 Volume license
    msiexec /i {90150000-0014-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Enterprise x86
    msiexec /i {90150000-0030-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Office 2013 Enterprise x64
    msiexec /i {90150000-0030-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb

Microsoft Office 2016 product series:

  • Microsoft Office 2016 Professional Plus DE 32-bit VLK version:
    msiexec /i {90160000-0011-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Microsoft Office 2016 Professional Plus DE 64-bit VLK version:
    msiexec /i {90160000-0011-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Microsoft Office 2016 Standard DE 32-bit VLK version:
    msiexec /i {90160000-0012-0000-0000-0000000FF1CE} addlocal=OutlookVBScript /qb
  • Microsoft Office 2016 Standard DE 64-bit VLK version:
    msiexec /i {90160000-0012-0000-1000-0000000FF1CE} addlocal=OutlookVBScript /qb

Subscribe to our Newsletter

 
 
 
 
 
 
 

Thank you for subscribing. To confirm your subscription, please click the link in your registration email.

 
 

An error occured. Please try again.



Cookies ermöglichen eine bestmögliche Darstellung unserer Dienste. Mit der Nutzung der Seiten von C4B Com For Business, erklären Sie sich damit einverstanden, dass wir Cookies verwenden. mehr Infos