This article provides guidance to IT administrators and corporate software groups who are evaluating or deploying the Office Timeline add-in. It covers system requirements, software distribution system configuration, and registry key settings.
The Office Timeline End User License Agreement (EULA) can be found in the product at installation. A licensing overview can be found here: https://www.officetimeline.com/license. The most current build of Office Timeline can be found here: https://www.officetimeline.com/updates
In order to successfully deploy Office Timeline, each machine must meet Microsoft's requirements for add-ins. Here are the minimum requirements:
- Windows Vista, Windows 7, Windows 8, Windows 10
- Microsoft Office 2007, 2010, 2013 or 2016
- .NET Framework 4.5.2
- VSTO 2010 Runtime (v10.0.50903) or newer
- .NET Programmability Support for PowerPoint enabled in Microsoft Office. This is typically enabled by default during an Office install.
* Although Windows XP is not supported, many customers use Office Timeline on Windows XP.
To deploy Office Timeline within a corporation, follow the instructions below:
Purchase a volume license (multi-licenses). Contact email@example.com for info.
Download OfficeTimeline.zip from here and install on a prep system.
Make sure the target systems have the following software installed:
- Office 2007 or newer (2010 or newer is recommended)
- Office 2007 must have Service Pack 3 installed
- .NET Framework 4.5.2
- VSTO 2010 Runtime v10.0.50903 or newer (download from here)
Configure your software distribution system to install Office Timeline using the following command line:
msiexec /i OfficeTimeline.msi LICENSEKEY=AAAA-BBBB-CCCCC-DDDDD-EEEEE-FFFFF(Replace the AAAA-... part with your actual volume license product key.) The installation must execute with a user logged on.
It is possible the installation will execute without a user being logged on, but this scenario is not supported yet. If the activation cannot be performed by the setup (because the activation server is blocked by your company firewall, for example), the add-in will display the activation dialog at the very first run and the user or the system administrator will have to manually enter the product key in that dialog (this solution was chosen to protect the product key).
To configure the add-in to not send usage data to Office Timeline, add this parameter to the command line:
To block the add-in from checking for updates, add the following parameter to the command line:
This will disable both automatic update queries and the ones performed manually by users.
If you want to only deploy the Free Edition, configure the following command line:
msiexec /i OfficeTimeline.msi
If automatic activation fails due to a corporate firewall and you would like automatic activation to function, you will need to make exclusions in the firewall for the Office Timeline website and activation service:
- activation.officetimeline.com:443 HTTP/1.1
- www.officetimeline.com:443 HTTP/1.1