Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Export the CardioLog registry key to a *.reg file:
    • 32-bit machine  - HKEY_LOCAL_MACHINE\SOFTWARE\Intlock\CardioLog  
    • 64-bit machine  - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intlock\CardioLog
  2. Edit the CardioLog registry key (*.reg file):

    "DATABASEINSTANCE"="[database server name]"

    "TARGETDIR"="[CardioLog Installation Folder]"

      [database server name] - The database server name that currently hosts the CardioLog database.
      [CardioLog Installation Folder] -  Edit the database server name Edit the installation folder path to match the new server path that now hosts the CardioLog application will be installed on, on the new server.

  3. Import the CardioLog registry key to the new server by copying the *.reg file to the new server and double clicking on it.
  4. Disable both CardioLog windows services, CardioLog Diagnostics Service and CardioLog Scheduling Service, on the old CardioLog application server.
  5. Run the CardioLog installer on the new server using the credentials of your CardioLog service account. Follow the Installation Wizard steps.
  6. Contact us to receive the required licenses for the new server and apply them using the License Admin tool (copy the Microsoft.Licensing.LicAdmin.exe tool from [CardioLog Installation Directory]\Setup Files\SLPS\ to [CardioLog Installation Folder]\CardioLogScheduleServices\ and execute it from there).
  7. In the CardioLog database, edit the server name in the tab_management and tab_global_settings tables by executing the following SQL script (edit the old and new CardioLog server name):

    Use CardioLog

    declare @oldName varchar(max) = 'CardioLog old machine name'; declare @newName varchar(max) = 'CardioLog new machine name'; --== 1. tab_management table update tab_management set url = replace(url, @oldName, @newName), serverName = @newName; --== 2. Global settings --== 2.1. CardioLog.Host exec [dbo].[stp_global_settings_upsert] @Category = 'CardioLog', @Name = 'Host', @Value = @newName, @ReplaceIfExists = 1; --== 2.2. PdfExport.CardioLogPdfRoot declare @value varchar(max) = (select Value from tab_global_settings where Category = 'PdfExport' and Name = 'CardioLogPdfRoot'); if (@value is not null) begin set @value = replace(@value, @oldName, @newName); update tab_global_settings set Value = @value where Category = 'PdfExport' and Name = 'CardioLogPdfRoot'; end
    --== 3. tab_agent_params table
    update tab_agent_params
    set str1 = replace(str1, @oldName, @newName) 
    where AgentId in (2,4,6)
  8. If you have implemented the CardioLog Analytics SharePoint Feature on your Web Front Ends (WFEs), edit all instances of the CardioLog server name (eg., http://[CardioLog server name:port]/ ) in the /_layouts/CardioLogAgent/web.config file, located on the SharePoint WFEs respectively:

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\CardioLogAgent\web.config

    Otherwise, edit the CardioLog Java Script tracking code embedded within a common Java Script file, located on your SharePoint WFEs. The code is located at the end of the file, between the comments: //Intlock tracking code start and  //Intlock tracking code end

    For MOSS 2007 only:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033\core.js

    For SharePoint 2010 only:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033\init.js

    For SharePoint 2013 only:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\init.js

    For SharePoint 2016 only:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\init.js

  9. If you have implemented the CardioLog HTTP Module for SharePoint on your Web Front Ends (WFEs), for each web site, modify the SharePoint Web.config file and edit the CardioLog server name (eg., http://[CardioLog server name:port]/ )  in the following key value:

    <add key="CardioLog.API.EventsServiceUrl" value="http://[CardioLog server:port]/CardioLogAPI/Events.asmx"/> 

migrate sp farm
migrate sp farm
How to Configure CardioLog When Migrating a SharePoint Farm


  1. In the Administration pane, click System Configuration, and then select SharePoint Tree Adaptor.
  2. Select your SharePoint farm .
  3. In the SharePoint Tree Adaptor dialog, edit the following fields:
    • Database Server - The SharePoint database instance name.
    • SharePoint Configuration Database Name - The SharePoint configuration database name. eg. "SharePoint_Config"
    • Authentication - Database authentication type: Windows Integrated, or SQL Authentication.
    • SharePoint TEMPLATE Directory - this is the full path for the SharePoint 'TEMPLATE' directory. eg. \\<sharepoint server name>\C$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\" (Where XX - 12 for MOSS 2007; 14 for SharePoint 2010; 15 for SharePoint 2013, 16 for SharePoint 2016)
  4. Click Apply.
  5. Select the web applications you would like to monitor, then click Save.
  6. After the next run of Portal Tree Updates, the updated tree structure will be available in the Analysis Center and Object Explorer.
    Image Removed
    System Configuration - SharePoint Tree Adaptor
In versions lower than, follow these steps:If the SharePoint databases are moved to a new server, edit the SharePoint database connection string in the [CardioLog Installation Folder]\SP20XXTree\Web.config file  (Where XX is 07 for MOSS 2007; 10 for SharePoint 2010; 13 for SharePoint 2013):


<add name="configDB" connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=[SharePoint Configuration Database Name];Data Source=

[SharePoint Database Server Name]" />

<add name="contentDB" connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog={0};Data Source={1}" />


           [SharePoint Configuration Database Name] - Your SharePoint configuration database name
           [SharePoint Database Server Name] - Your SharePoint database server name

If the SharePoint web application root URL was modified or the SharePoint web application is hosted on new WFE servers, edit the following keys in the [CardioLog Installation Folder]\SP20XXTree\Web.config file (Where XX is 07 for MOSS 2007; 10 for SharePoint 2010; 13 for SharePoint 2013)

<add key="includedWebApps" value="[SharePoint web application root URL]" />

<add key="SharePointTemplatePath" value="[SharePoint TEMPLATE path]" />

           [SharePoint web application root URL] - A star '*' separated list of the monitored SharePoint web applications in the farm
           [SharePoint TEMPLATE path] - Your SharePoint TEMPLATE folder path, which should be: 
           \\SharePoint WFE server name\C$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\ (Where XX is 12 for MOSS 2007; 14 for SharePoint 2010; 15 for SharePoint 2013) 

  1. and edit the configuration settings accordingly (for more details see this guide for SharePoint 2013 or lower or this guide for SharePoint 2016 or higher). 

configure collection
configure collection
Configure Event Collection


Install the CardioLog Analytics Tracking Agent


In the Administration pane, click System Configuration and select Usage Tracking Code and then select your SharePoint version.

feature on the migrated farm as detailed in this guide