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:

Organization Unit Updates

Since Release 2.6 the data concept behind OrganizationUnits (OU) became a mandatory field for every agent. As a result, migration steps of this field have become obsolete in newer LUCS versions.

(lightbulb)  This step is only required if updating from LUCS 2.6 or earlier.  

Service Log Cleanup

  • After the LUCS System Components were uninstalled, it is recommended to clear Event Viewer from logs remaining from previous version using PowerShell script: remove-eventlog -logname LUCS. In any cases, all the logs will be written into the new Event log source while the old one will not be used anymore and remain as trash.

  • Recommended size for event logs are 10MB (10240 Kb). Each setup checks the size of 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 access these settings, open: Windows Event Viewer -> Application and Services Logs -> Luware-LUCS (Properties)

The Log Properties

Log Properties

Set Install Date

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.

    Example

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


    → 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
    CODE

    → 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.
CODE