• Facebook
  • RSS Feed
  • Instagram
  • LinkedIn
  • Twitter
Feb 102011
 

A few days ago some questions were asked about an article I wrote in September last year.  It concerned installing the Enterprise Vault Outlook Addin on to a Windows 2008 Terminal Server.  The questions I was asked related to how to do this on Windows 2008 R2 x64, and using Outlook 2010.

Remember this isn’t officially supported by Symantec, it’s just my installation in my own time.

Here is how to do it :

The first part of things is largely the same as the “old” article; you have to enable Terminal Services, now called Remote Desktop Services.

There are several other options as you walk through the wizard, and if you are lucky enough to be doing this on real, supported hardware (I’m using VMWare) then you can enable all sorts of neat stuff :

ol2k10-2

And

ol2k10-3

At the end of the installation I restarted machine, and begun the next step of installing Office 2010

Installing Office 2010

I thought that this would be easier with the new version of Office, but on entering my product key I was given the following problem :

ol2k10-4

My keys are MSDN ones, and I thought that I was going to be scuppered, because I know that we don’t have Volume Licensing Keys.  However, when I checked the product keys section on MSDN there is a nice “enabler” key under Office 2010.

So that let me finish the install.

Installing the Enterprise Vault Outlook Add-in

The chose the 9.0.1 client, and the installation of that was just perfectly normal.

Publish Outlook as Remote App

Just like before all you then need to do is publish Outlook as a Remote App.  The screenshot for that is largely the same as before :

ts-remoteapp

Build an MSI for clients

To build an MSI for clients to use, click on the RemoteApp program that was added above, if you right click it you have various options including building an MSI.

Install the MSI on a client machine

If you share out the location on the server that you built the MSI then any client with permissions can browse to that network folder, and run the MSI.  After doing so they will have a “Remote Programs” program folder containing Outlook

Launching Outlook

I thought things had gone well to this point, but when I started Outlook I saw :

ol2k10-5

Dreaded VBScript problems.

After a bit of searching you can enable it (as before) using MSIEXEC.  The bit you need is the GUID.  The screenshot shows it :

ol2k10-6

So you find in HKLMSoftwareMicrosoftWindowsCurrentVersionUninstall, and look for the entry that contains “Microsoft Office Professional Plus 2010”.  There are lots of others higher up the list with names like “Microsoft Office Shared Setup Metadata MUI (English)” – ignore all those, you are after the one for the “main product”, and then run :-

msiexec /i {GUID} ADDLOCAL=OutlookVbScript /qb

Bingo, Outlook then runs very nicely indeed with the Outlook add-in.

What’s even more cool is that I installed Office 2010 x64, on a 64 bit Windows 2008 R2 machine … and I can run the MSI to install the Remote App on 32 bit Windows XP.  It works just fine.

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

  3 Responses to “EV Outlook Add-in on Windows 2008 R2 x64 Terminal Server”

  1. Nice post. I was checking continuously this weblog and I’m impressed! Very helpful info specially the closing part 🙂 I maintain such information much. I was seeking this particular info for a long time. Thanks and good luck.

  2. Nice article.

    Adding the string for Office 2010 Pro Plus
    change user /install
    msiexec /i {90140000-0011-0000-1000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb
    change user /execute

    Some additional info from a Citrix Forum post:
    If you didn’t create the transform to include VBScript while installing Office 2010 you need to do either of these:

    1. Search the registry under HKEY_CLASSES_ROOT\Installer\Features\ for OutlookVBScript and delete the key or;
    2. Open the Custom Installation Wizard, and then create a new transform. Go to Modify Setup properties and add:
    Property Name: WTSDISABLED
    Value: MsInfoFiles,PPTCastCoreFiles

    I tried these to methods on 2 separate application servers and both resolved the issue for me.

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)