This page lists optional and situational steps. Not every upgrade or configuration may require all these tasks to do. However is recommended to quick-check these chapters below to see if you have forgotten anything.

(warning) We highly advice the following steps to be done by a Luware-trained administrator.

Related Chapters:

Backup of Topology Data

It is recommended to copy the current topology data from previous version of TM Configurator.

TM Configuration

  1. Open TM Configurator -> Topology -> Components (Server)
  2. Open the details of the AC, CR and ICH system components.
  3. Copy the topology data of the AC, CR and ICH system components.

Lync Server via Control Panel

  1. Go to the Lync Server machine.
  2. Open Microsoft Lync Server Control Panel -> Topology -> Trusted Application.
  3. Copy the topology data of the AC, CR and ICH system components.

Lync Server 2013 Control Panel

Lync Server via Management Shell

  1. Go to the Lync Server machine.
  2. Open the Lync Server Management Shell.
  3. Run Get-CsTrustedApplication command.
  4. Search for the needed component.
  5. Copy the topology data of the AC, CR and ICH system components.

Lync Server Management Shell

Prepare Migration Script for Execution after DB Upgrade

It is required to execute this step during the upgrade process from versions older than V2.6. If the currently installed version is TM V2.6 and higher, ignore this step.

It is required to change the topology data for several system components (AC, CR and ICH). This should be done after the installation of new system components using the migration script. It is more convenient to prepare the migration script before the previous system is uninstalled.

To prepare the migration script, follow the steps:

  1. Copy the current topology data from one of the following sources:
    1. from TM Configurator
    2. from Lync Server using the Lync Server Control Panel
    3. from Lync Server using the Power Shell cmdlets in the Lync Server Management Shell

  2. Replace ‘Default Pool’ value by valid [TrustedApplicationPoolName]. This value will be assigned to trusted applications on TM Configuratior -> Topology->Trusted Applications tab.
  3. Update ‘DeleteServerConfiguration’ parameter by the following data :
    1. set to 0 to add new configuration settings to the system
    2. set to 1 to clean up old server configuration without adding new values

  4. Insert the [ApplicationURN], [ApplicationUserAgent] and [Port] topology data of the AC, CR and ICH system component into the "/*Please, place configuration below */" section of the migration script
    → the script is located in the release folder TM\\12_SQLScripts\LUCS_TM_TrustedApplication_Migration.sql

  5. (warning) Do not make any changes for MM component in the script, leave it as it is.
  6. (warning) Do not make any changes in other parts of the script.

Migration Script Configuration Placement

/*Please, place configuration below */
SET @SfBTrustedApplicationPoolName='DEFAULT POOL'--desired name for default application pool
SET @DeleteServerConfiguration= 0 -- Set 1, when configuration is correct to cleanup old server configuration settings

INSERTINTO @CurrentConfig([TrustedApplicationId], [ServerType], [ApplicationURN], [ApplicationUserAgent], [Port])
         -- ApplicaionURN and ApplicationUserAgent for AC (LUCS and TM)
         -- ApplicaionURN and ApplicationUserAgent for CR (LUCS and TM)
         -- ApplicaionURN and ApplicationUserAgent for ICH, "Port" setting from Lync server (LUCS and TM)
,('895F9A9E-572E-4F2B-AF3C-AAA515469BE6','MM','urn:application:lucs_mailmanager','lucs_mailmanager', 0)
         -- ApplicaionURN and ApplicationUserAgent for MM (only for LUCS)

Note It’s recommended to run script twice with: the first time ‘DeleteServerConfiguration’ value set to  0, and then with  ‘DeleteServerConfiguration’ value set to  1.

Optional Cleanup Steps:

  • After the TM System Components were uninstalled, it is recommended to clear Event Viewer from logs remaining from previous version using a PowerShell script:

    remove-eventlog -logname TM

    (info) New logs will be written into the new Event log source, while the old ones will not be used any more and remain as trash. They may however be kept for historic / comparison reasons. The recommended size for event logs are 10MB (10240 Kb). Each setup checks the size of the current event log and tries to set it to recommended value. This limit will be increased to 10MB only when setup was run with administrative permissions, if not – it should be manually updated to 10MB.
    → To change this file size limit, open:  Event Viewer -> Application and Services Logs ->Luware-TM (Properties)

    Log Properties

Check Exchange Web Services

Before TM 2.8, the new version of Microsoft.Exchange.WebServices  2.0 (File version 15.0.516.14) were used by CI and CR components.  

If an old version of assembly was registered in GAC it might lead to exceptions on CI and CR operation. To  avoid such problems, check  GAC and register the new  version if necessary:

To make sure that your upgrade installation will run smoothly, check GAC and register the new version if necessary:

  1. Go to GAC folder C:\Windows\assembly and check if Microsoft.Exchange.WebServices exists.

    GAC folder

    GAC Folder
  2. Right click on the Exchange.WebServices.
  3. Select ‘Properties’  → A window opens
  4. In the pop-up window select Version tab -> Product Version

    Microsoft.Exchange.WebServices File Version property

    Microsoft.Exchange.WebServices File Version property

Install new EWS Version

  1. To install the new version of the assembly go to GacUtil To find the location go to C:\Program Files (x86)\Microsoft SDKs\Windows  folder and run search for ‘gacutil.exe’.
    1. If you don’t have gacutil.exe on your computer, you can download it here
  2. Copy the path to the folder where ‘exe’ is located.
  3. Run a command prompt with administrator rights.
  4. Execute a command to open the folder where ‘gacutil.exe’ is  located :

    C:\> cd C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools

    Changing directory using Windows Command Line

    Changing directory using Windows Command Line
  5. Go to the folder where TM-CI is installed and check that it contatains Exchange.WebServices.dll.  By default the following path is used C:\Program Files\Luware AG\TM-CI\
  6. Copy the path
  7. Using the copied path, execute a command to install the assembly into the global assembly cache. If an assembly with the same name already exists in the global assembly cache, the tool overwrites it.

    C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools> gacutil.exe -if "C:\Program Files\Luware AG\TM-CI\Microsoft.Exchange.WebServices.

    Registering  new version of dll using Windows Command Line

Set Install Date for Reporting

INSTALL_DATE is a value in [Reporting].[_SysSetup] table. Sessions, which started after or on this date, are included into the reporting. However, old report data may be left out by this rule and thus not appear in the reporting anymore.  

To change this date:

  1. Execute a special stored procedure:[mgt].[usp_Reporting_SysSetup_SetInstallDate with the parameter @NewINstallDate.


    EXEC [mgt].[usp_Reporting_SysSetup_SetInstallDate] @NewInstallDate = ‘20160101’

    → Result: 
    After the successful execution, the stored procedure gives the output like below:

    New Install date is set to ‘2016-01-01’
    402 Sessions added

    → This means that install date was shifted back to the past to 2016-01-01 and 402 sessions will be added into reporting after integration is completed.

  2. To ensure that any changes on Install Date are propagated to reports, run "Reporting.ups_Dataloader" method once
    → SSRS Report data should now reflect the new install date as part of the metrics .

Abvoiding (future) Date-errors in your Reporting

We recommend setting up a Job for this Dataloader method (at an interval like 10-20 min) to ensure that reports always pushed to db with the newest respective date.

If you try to shift the install date forward and integration job has already loaded sessions for that date, setting install date will fail with message like below:

Can not set Install date ‘2016-01-02’, because all Sessions beginning from ‘2016-01-01’ have already been loaded into reporting and will be not reverted.