Joe Bianco
Oct 7, 2009
(3 votes)

Utilizing the Microsoft Office Add-In and Client Components with EPiServer CMS

EPiServer CMS provides tools for integrating with Microsoft Office client applications which include the Microsoft Office Add-In and the EPiServer CMS Client Components. This post describes the process for enabling, installing, and activating Microsoft Office integration and client components for EPiServer CMS. 

The Microsoft Office Add-In enables Editors to publish files to an EPiServer site directly from Microsoft Word, Excel, and PowerPoint.

The EPiServer CMS Client Components provide the following capabilities:

  • Integrated spell checker
  • Export form data to Excel
  • Drag and drop and multiple file upload into the EPiServer File Manager

To utilize these features, Office integration must be enabled and activated on each CMS site and the Microsoft Office Add-In and EPiServer CMS Client Components must be installed on each client machine that is to utilize the components.

Enabling Office Integration

Office integration must first be enabled in the web.config file for each CMS site on which you wish to utilize it.

To enable Office Integration on your CMS site…

1. Open the web.config file from the root of the site on which you wish to enable the Office Add-In and Components and uncomment the following text. Note that the portion of the path preceding “/OfficeIntegration” will vary depending on what was configured when the site was created (e.g. the “Relative Path”  setting on the “Create new EPiServer CMS site” dialog of the EPiServer Deployment Center).


<!--<location path="UI/OfficeIntegration">
      <allow users="*" />

2. Change the “UI” portion of the “path” attribute to the “Relative Path” that was set for the “EPiServer User Interface” on the “Create new EPiServer CMS Site” dialog when the site was created with the EPiServer Deployment Center. For example…

<location path="Cms/OfficeIntegration">
      <allow users="*" />


If you receive the following error it is likely because you did not enable Office integration as described above.

“Failed to contact EPiServer CMS, make sure the URL is valid and you are authorized to perform this action.[200]”


Installing the Microsoft Office Add-In

The Microsoft Office Add-In must be installed on each client computer that is to utilize it. This can be done from Edit Mode in CMS.

1.  From the client machine, in CMS Edit Mode, select the “Root folder” in the “Structure” pane and select the “Microsoft Office Add-In” tab.


2. Click the “Install version x.x” button and follow the instructions in the EPiServer CMS Office Add-In Wizard.



Activating the Microsoft Office Add-In

The Microsoft Office Add-In must be activated for each CMS site on which you wish to utilize it.

1. In CMS Edit Mode, select the “Root folder” in the “Structure” pane and select the “Microsoft Office Add-In” tab.

2. Select the “2. Activate” tab and click the “Activate” button.



If the client machine is running Windows Vista, Windows Server 2008, or Windows 7, the activation may fail silently but appear that it succeeded because of Internet Explorer security settings.  An easy workaround for this is to to add the CMS site to the Trusted Sites in Internet Explorer on the client machine. 

Make sure the siteUrl attribute of the siteSettings element in web.config is correct (e.g. the machine or domain name in web.config matches the name in the URL you are accessing to activate the add-in).  The activation will fail silently if the siteUrl is incorrect because the add-in is activated for this URL.  A colleague of mine ran into this issue when setting up CMS on an Amazon EC2 instance because the machine gets renamed every time the instance is brought up.

Installing the Client Components

1. From the client machine, in CMS Edit Mode, select the “Root folder” in the “Structure” pane and select the “Components” tab.

2. Click the “Install version x.x” button.


3. The Components tab should look like the following when the components have been successfully installed.



You may not be able to install the client components via the browser on Windows Vista or Windows Server 2008 depending on your Internet Explorer security settings. In this scenario, the “Client components installation” window below will be displayed after clicking the “Install version x.x” button, but the client components will not be installed.


You can work around this by manually extracting the client component DLLs from…

  • CMS 5 - C:\Program Files\EPiServer\CMS\<CMS version>\Application\UI\ActiveX\EPiServerClientComponents
  • CMS 6 - C:\Program Files\EPiServer\CMS\<CMS version>\Application\UI\CMS\ActiveX

…CAB on the server and registering them manually on the client machine using the following commands:

regsvr32.exe EPiFileUpload.dll
regsvr32.exe EPiOfficeIntegration.dll

Oct 07, 2009


Sep 21, 2010 10:32 AM

Great post, will activate it now. Keep them coming
/ Jacob Khan

Leif Boström
Leif Boström Sep 21, 2010 10:32 AM

Nice post! One more thing to add to the list.

After everything is up and running editors may experience that they can't use "drag-and-drop for multiple file uploads". Go into Admin mode -> Config tab -> Security -> Permissions for Functions, and set the "Allow advanced upload of files using for example drag-and-drop" for the appropriate users and roles.

Sep 21, 2010 10:32 AM


Sep 21, 2010 10:32 AM

i am facing problems with ie7 version and the CMS Client Components..
I would really need that ie.7 hotfix package.
Where it is possible to load?


/ Sirpa May 13, 2011 11:29 AM

Thanks for the information exactly what I was looking for. I have problems installing EPiServerClientComponents and get a redcross, when I try to install. I have canged the security to minimum in IE9, but with no succes.

I extracted the files from the server (win server 2008, with EPiServer 6). But when I try to register the file om my computer (win7, IE9) I get an error:

"Modulen EPiFileUpload.dll lästes in, men anropet till DllRegisterServer misslyckades med felkoden 0x80070005."

The errorcode seems to indicate "Access denied", but I am logged in as admin om my computer. Do you hade any ideas what could be the problem? May 13, 2011 02:04 PM

Problem solved :) I had to run Command prompt as Administrator. Rightclick and choose "Run as administrator"

Works great now!

Thanks a lot for the information! Apr 18, 2013 01:07 AM

We're in the process of upgrading to CMS7 and the officeintegration is not working for us. Of course, the admin and edit UI have changed significantly, but there appears to be no reference to the addin after uncommenting via web config.

Under the Root folder ins editmode there are just two links to "My Settings" and "License Agreement". There are no "tabs" available there as in your CMS6 screen shots - certainly not one saying "Microsoft Office Addin"

Do you know if the process has changed? Can you provide any pointers? All references in CMS7 suggest drag and dropfor file upload is still available but we can't get it to work.

Thanks in advance.

Please login to comment.
Latest blogs
Customizing Property Lists in Optimizely CMS

Generic property lists is a cool editorial feature that has gained a lot of popularity - in spite of still being unsupported (officially). But if y...

Allan Thraen | Oct 2, 2022 | Syndicated blog

Content Delivery API – The Case of the Duplicate API Refresh Token

Creating a custom refresh provider to resolve the issues with duplicate tokens in the DXC The post Content Delivery API – The Case of the Duplicate...

David Lewis | Sep 29, 2022 | Syndicated blog

New Optimizely certifications - register for beta testing before November 1st

In January 2023, Optimizely is making updates to the current versions of our certification exams to make sure that each exam covers the necessary...

Jamilia Buzurukova | Sep 28, 2022

Optimizely community meetup - Sept 29 (virtual + Melbourne)

Super excited to be presenting this Thursday the 29th of September at the Optimizely community meetup. For the full details and RSVP's see the...

Ynze | Sep 27, 2022 | Syndicated blog

Preview multiple Visitor Groups directly while browsing your Optimizely site

Visitor groups are great - it's an easy way to add personalization towards market segments to your site. But it does come with it's own set of...

Allan Thraen | Sep 26, 2022 | Syndicated blog

The Report Center is finally back in Optimizely CMS 12

With Episerver.CMS.UI 12.12.0 the Report Center is finally re-introduced in the core product.

Tomas Hensrud Gulla | Sep 26, 2022 | Syndicated blog