SysTrack 8.3 Installation Guide

(1)

SysTrack 8.3 Installation Guide

Introduction

This document provides bothpre-installation preparation informationand detailed instructions for installing SysTrack. So that you may better understand the installation process, an overview of the SysTrack architectureis also included.

This document also provides the following instructions that apply after the SysTrack installation is complete:

n Using SysTrack Deploy toadd SysTrack agents to any Child Systems you wish to monitor, toset up and apply roles and configurations, and toset up SysTrack Web Services

n Completing theSysTrack reporting configuration

Installing SysTrack Master and Web Services Suite on laptop chassis systems will result in poor functionality and will not be supported by Lakeside Software.

If you need assistance with the installation, please refer to theWhere to Go from Heresection of this document for Technical Support contact information.

4

(5)

Supported Operating Systems and Prerequisites

SysTrack Master Setup / SysTrack Web Services:

n 64-bit only

n Must have a static IP or a DNS reservation

n Cannot be a domain controller

n Microsoft Windows Server 2012

n Microsoft Windows Server 2012 R2

n Microsoft .NET Framework 4.6.1 (Full)

n Microsoft Access Database Engine 2010 (x64)

n Cannot have any IIS applications installed

n Microsoft SQL Server 2012 Native Client (only if NOT installing Microsoft SQL Server on the Master server)

n Microsoft Visual C++ 2017 (x86) Redistributable

n Microsoft URL Rewrite module 2.0 for IIS 7 (x64) SysTrack Administrative Tools:

n Microsoft Windows 7 Service Pack 1

n Microsoft Windows 8

n Microsoft Windows 8.1

5

(6)

SysTrack Agent:

n Microsoft Windows 7 Service Pack 1

n Microsoft Windows 8.1

n Microsoft Windows Server 2008 R2 Service Pack 1

n Microsoft Windows Server 2016 Supported Browsers:

n Microsoft IE9 to IE11 and newer

n Chrome 42.0.2311 and newer

n Firefox 48 and newer

n Edge 48.14393 (Anniversary Update version) and newer Prerequisites

SysTrack Master Server:

n Static IP or an DNS reservation.

n Microsoft .NET Framework 4.6.1

n Roles and Features (See SysTrack Requirements_8.3.pdf)

n Microsoft SQL Server 2012 Native Client SysTrack Web Services:

n Microsoft Access Database Engine 2010 (x64)

6

(7)

n Microsoft URL Rewrite Module 2.0 for IIS7 (x64)

n Cannot have any IIS applications installed SysTrack Administrative Tools:

n IE 6.0 or above SysTrack Agent:

7

(8)

SysTrack Product Architecture

The SysTrack product architecture consists of one or more SysTrack deployment trees, each of which operates independently. At the head of each tree is a SysTrack server often referred to as the Master System. This system is responsible for the deployment of the SysTrack agents onto endpoint systems (often referred to as Child Systems) within that tree.

The structure of the tree is determined using SysTrack Deploy. Once you have created the tree using this tool, the SysTrack Master System deploys software and configuration instructions necessary to create the desired tree structure.

Each monitored Child System in your SysTrack tree has an associated database. For most Child Systems, this is a local Microsoft Jet database. You can choose to use LocalDB for more active Child Systems such as a terminal server

The LocalDB database may be recommended for certain Terminal Server environments (such as large load-balanced systems). Requires up to 1 GB RAM overhead using LocalDB in default

configuration. Contact Lakeside Software Technical Support to discuss if it is recommended for your environment.

The Master System will use a SQL Server Express or a SQL Server database. SQL Server is not included with SysTrack. SQL Server Express is part of the SysTrack Download image.

Child systems in the SysTrack tree periodically send a subset of their data from their local database to their parent system’s database. In the case of non-persistent systems the database association is slightly different and makes use of a pooled system or user hosting model.

SysTrack requires MSI installs for non-persistent virtual machines for a given pool. The Golden Image used for this process has a specially prepared agent installed on it such that the agent knows it is on a non-persistent system when it starts up. This Golden Image cannot be used on a persistent VM interchangeably.

The structure of the tree that you create with SysTrack Deploy determines the child-parent relationships.

SysTrack is very flexible in this regard. If you install multiple SysTrack trees, you may use SysTrack Deploy’s uplink feature to link entire trees to higher level trees. This allows transparent navigation and reporting across tree boundaries.

8

(9)

9

(10)

Pre-Installation Preparation

This information is provided to give you an opportunity to prepare for the SysTrack installation before your scheduled meeting with Lakeside Software Support. As part of that preparation, there areprerequisites you should install in advance to decrease the time needed for the actual SysTrack installation.

This section includes information on the following:

n SysTrack Upgrades

n SQL Server 2016 Installation

n Database Preparation

n SysTrack Master Preparation

n SysTrack Agent Deployment Preparation

n Anti-Virus Exclusions

n Microsoft SQL Server Reporting Services Installation

n Non-Persistent Virtual Machines

n Uninstalling SysTrack Agents

n SysTrack Resource Footprint

SysTrack Upgrades

For customers who find it necessary to maintain two versions of the SysTrack Agent running for a period of time, the following method of upgrade is recommended instead of conducting an in-place upgrade:

1. Setup parallel master servers and migrate systems from the old to the new server as they are upgraded.

2. If you decide to pursue this method of upgrade and have limited resources, it is likely that you will need at least one new server to complete the process. You can then migrate and upgrade child systems from one old server to the one new server.

3. Once the old server is empty, it can be upgraded, and child agents can be migrated to it.

4. Repeat this process until the upgrade is complete at which time you will no longer need the new server.

For assistance please contact SysTrack Customer Support:[email protected]

10

(11)

Upgrading Uplinked Masters

When performing upgrades on uplinked Masters, it is recommended that you upgrade from the top-level down:

1. Upgrade the top-level Master.

2. When the top-level Master upgrade is complete, upgrade the second-level Master (next down).

Continue this process until all your uplinked Masters are upgraded.

SQL Server Express 2016 Installation

The SysTrack installer installs SQL Server 2016 SP1 Express with Advanced Services. As a best practice we recommend you only use the included SQL Express for SysTrack installations that have less than 1500 non-load balanced users. If the database load becomes too great, you may have to switch to a different edition of SQL server in the future.

The SysTrack installer does not upgrade previously installed older versions of SQL Express to

SQL Server 2016. If you need assistance with this, please contact Lakeside Software Technical Support.

11

(12)

On Server 2012, Server 2012 R2, or Server 2016 operating systems:

1. SysTrack Setup installs SQL Server 2016 SP1 Express with Advanced Services if selected.

2. Clean (1st time) SysTrack installations will display the dialog to have you either select an existing SQL Server database OR select to install SQL Server 2016 SP1 Express with Advanced Services:

12

(13)

Database Preparation

The SysTrack database currently supports Latin collation sequences. In the United States, the United Kingdom, and Australia, it is recommended that the SQL database collation should be set to: SQL_Latin1_General_CP1_CI_AS.

Customers in countries other than those listed above should refer to the SQL Server Collation Compatibility SysTrack Knowledge Base article for further information, or contact SysTrack Customer Support.

1. Database Hardware should be configured and communicating on the network.

2. As a best practice we recommend you only use the included SQL Express for SysTrack installations that have fewer than 1500 non-load balanced users. If the database load becomes too great, you may have to switch to a different edition of SQL Server in the future.

In addition to the SQLEngine and Tools features, the Reporting Services feature is also installed with the SYSMGMT_DB instance of SQL Express installed by SysTrack Setup.

3. For SysTrack installations that have more than 1500 non-load balanced users or less:

a. Install SQL Server 2008 R2 SP3 and above prior to SysTrack installation. IMPORTANT:

To view SQL reporting data requires the Reporting Services feature installed with your SQL Server installation.

The minimum database requirement is Microsoft SQL Server 2008 R2 SP3

SQL Server is not supported for virtualized and non-persistent XenApp servers

b. Beginning with the release of Microsoft SQL Server 2016, Microsoft removed the installation of Microsoft SQL Server Management Studio (SSMS) from the main SQL Server installation process.

SSMS will need to be installed separately.

c. After SQL Server installation:

i. Verify that TCP is enabled and Named Pipes protocols are enabled.

ii. Verify Windows and SQL authentication are enabled.

iii. Create a SQL database to be used as the SysTrack database and make sure that the recovery mode is set to Simple.

13

(14)

iv. To use the SysTrack reporting tools such as SysTrack Dashboard, SysTrack Visualizer, and SQL Server Reporting Services reports, you need to set up aReporting User Account. This should be a Windows domain account (not a SQL or SA account). The Reporting User account needs ‘Allow Logon Locally’ permissions to the SysTrack server and the server where SSRS is hosted (the SQL server in most cases).

14

(15)

SysTrack Master Preparation

SysTrack Master is installed on a 64-bit operating system following theSupported Operating System guidelines.

1. SysTrack installation package downloaded, unzipped, and placed on the Master System.

2. Master System prerequisites:

n Must have a static IP or a DNS reservation

n Cannot be a domain controller

n Cannot have any IIS applications installed

n **Microsoft .NET Framework 4.6.1 (Full)

n ***Microsoft Access Database Engine 2010 (x64)

n Microsoft SQL Server 2012 Native Client (if NOT installing Microsoft SQL Server on the Master server)

n Microsoft URL Rewrite module 2.0 for IIS 7 (x64)

** If not previously installed, Microsoft .NET Framework 4.6.1, and Microsoft Access Database Engine 2010 (x64) will be installed during the SysTrack installation. Having these installed prior to installation is strongly urged, this will greatly decrease the time needed for your SysTrack installation.

*** If not previously installed, Microsoft .NET Framework 4.6.1 will be installed during the SysTrack Web Services installation. A .NET Framework 4.6.1 installation will take several minutes to install (>15 minutes is not uncommon). For Server 2012 R2 operating systems, there are several prerequisites that will also take several minutes to install (>15 minutes combined is not uncommon) and will require a reboot before being able to continue with the .NET Framework 4.6.1 install. These prerequisites must be installed in a specific order.

Having this installed prior to SysTrack installation is strongly urged, as this will greatly decrease the time needed for your SysTrack installation.

15

(16)

3. For database sizing and resource load information please refer to the SysTrack Resource Footprint document available from the Lakeside Support Portal.

While installing prerequisites the system will reboot multiple times as necessary.

4. Use a local administrator Account to load software.

5. For Push Deployment installations “file and print sharing” must be enabled on the child system before installation is attempted.

For Pull Deployment and MSI installations “file and print sharing” does NOT need to be enabled.

Once the SysTrack services are installed it will automatically add rules for TCP/UDP port 57632 to the windows fire wall on the child system. If a different firewall is used the customer is responsible for adding an exception for the TCP/UDP port 57632 once installation is completed so SysTrack Tools can connect to the child systems. SeeSysTrack Resource Footprintbelow for port information.

6. SysTrack utilizes Microsoft Package Negotiator for authentication and encryption (Kerberos or NTLM).

7. Verify that the Master System is in the same domain as the Child Systems, or that 2-way trust exists between the master and child domains.

SysTrack Agent Deployment Preparation

1. File and printer sharing must be enabled on each Child System and a user account credential defined with proper rights in order for the agent to be installed on the Child System.

2. If the Child Systems are not on the same domain as the Master System, a two way trust must exist.

3. When Symantec Anti-Virus exists on the Child System, file and printer sharing must be enabled.

Deploying the agent software can be done through an Enterprise Software Delivery system such as SCCM.

Instructions for this type of deployment are in the SystemsManagementAgent.pdf, with the source setup CDImage (e.g. SysTrack\MSI\SystemsManagementAgent.pdf), or installed on the SysTrack Master server (e.g. C:\Program Files\SysTrack\InstallationPackages\SystemsManagementAgent.pdf).

16

(17)

Anti-Virus Exclusions

Regardless of the deployment method used, for a successful deployment to child systems certain Anti- Virus software contains separate file and printer sharing options that may override the local machine settings and also need to be configured.

n File and Print Sharing should be enabled on the target child systems along with Remote Registry Service.

n The Windows client firewall should be disabled for the deployment or an exception created to allow traffic on port 57632. If there is a network firewall, IP addresses need to be routable and allow TCP and UDP traffic on port 57632.

Make sure to check that the following anti-virus settings are excluded in the anti-virus console if the Agent does not install correctly:

Child Systems

Exclude all items listed under \Program Files (x86) \SysTrack\LsiAgent SysTrack Master Server

Exclude all items listed under \Program Files\SysTrack\Agent\

For some SEP configurations, additional steps must be taken. If the following option is turned on in the SEP policy, exceptions will have to be made to the Application and Device Control settings:

n Block Applications from running

The SysTrack Agent and associated utilities must be allowed to run to collect data.

Microsoft SQL Server Reporting Services Installation

A report server is the central component of a Microsoft SQL Server Reporting Services (SSRS) installation.

SSRS installation is a requirement for including the Analyze Reports in various SysTrack applications such as SysTrack Visualizer and Transform.

Refer to theMicrosoft websitefor SSRS installation instructions.

Non-Persistent Virtual Machines

SysTrack requires MSI installations for non-persistent virtual machines for a given pool. The Golden Image used for this process has a specially prepared agent installed on it such that the agent knows it is on a non-

17

(18)

persistent system when it starts up. This Golden Image cannot be used on a persistent VM interchangeably.

Uninstalling SysTrack Agents

Uninstalling the SysTrack agent from the client systems can be done through SysTrack Deploy or through a command delivered to the client systems through a batch file or startup script.

18

(19)

SysTrack Resource Footprint

19

(20)

If you will be deploying from the master system using a push method, the installation files are sent via standard RPC (TCP 135) file and print sharing ports (TCP ports 139 and 445, and UDP ports 137 and 138).

MSI installations do not have this file and print sharing requirement.

20

(21)

Master Agent Services

In SysTrack 8.3 and higher there is no data collection on the Master system. The Master Agent includes the following services:

21

(22)

Service Name Executable Description

SysTrack Server LsiServer.exe n 3 copies running

n Functionality of each is based on the command line

n All 3 copies run the socket thread listening on one of the ports SysTrack Server - Core

(LsiServerCore)

LsiServer.exe -k Core n Listens on port 57632

n Provides core functionality

n Contains most of the master only threads from the original agent

n Handles all tool connections

n Provides files during push install

n Sends vScape (child UDP) data through the uplink every 5 minutes

SysTrack Server - Database prep (LsiServerDatabasePrep)

LsiServerDatabasePrep.exe ⁿ Listens on port 57632

n

n Run automatically by LsiServer-Core during first time install and after each upgrade. The other services wait until this has successfully finished.

n

n Creates/updates the database schema

n

n This is a service vs. an application and needs to run as system

n

n Runs Reporting.DatabaseSetup.exe and

ImagePlanner.DatabaseSetup.exe

22

(23)

SysTrack Server - Data Processor

(LsiServerDataProcessor)

LsiServerDataProcessor.exe ⁿ Processes condensed zip files

SysTrack Server- Data Receiver

(LsiServerDataReceiver)

LsiServer.exe -k DataReceiver ⁿ Listens on port 57630

n Receives condensed zip files from child agents

SysTrack Server - Pooled Users

(LsiServerPooledUsers)

LsiServer.exe -k PooledUsers ⁿ Listens on port 57631

n Sends/Receives pooled user data (collect.mdb and LsiAgent.reg in a zip file)

SysTrack Server - Push Deployment

(LsiServerPushDeployment)

LsiServerPushDeployment.exe ⁿ Executes Push deployment to child systems

SysTrack Server - Uplink Processor

(LsiServerUplinkProcessor)

LsiServerUplinkProcessor.exe ⁿ Performs daily bulk uplink

n Moves zip files between masters

23

(24)

Calculating Memory for SQL Server for a SysTrack Master

To calculate the Memory needed for SQL server for a given SysTrack Master (global, regional or dc) use the following formula:

n Desktops: Number of Physical or Virtual desktop systems divided by 1,000 =GB of RAM *

n Load Balanced Terminal Servers: (Number of load balanced users * number of terminal servers)/40,000 = GB of RAM *

n Dedicated Terminal Servers: (Number of users)/1,000 = GB of RAM *

For regional, global or other masters that have uplinked masters below them, count all child systems on lower nodes and current node.

Add the above numbers for each child calculation. A minimum of 16 GB is required.

24

(25)

SysTrack with fewer than 1,500 Agents (and up to 3,500 Agents)

For installations of fewer than 1,500 agents (and in certain limited cases up to 3,500) a server is

recommended that provides both the SysTrack services as well as the Express version of Microsoft SQL services:

If agents are deployed to non- persistent virtual machines then the SQL component must be hosted on a remote server.

SysTrack and Microsoft SQL Server

Item Quantity/ Description

CPU 2 x vCPU

Memory 12 GB

Operating System Microsoft Windows Server 2016 (Recommended)

Disk 60 GB

Microsoft Components IIS roles and features .NET 4.6.1

SQL Server Microsoft SQL Server 2016 SP1 Express (installed as part of SysTrack install) SysTrack Components SysTrack Master Server

SysTrack Web Services SysTrack Administrative Tools

25

(26)

SysTrack with between 3,500 - 6,000 Agents

For installations of between 3,500 - 6,000 agents it is strongly recommended that the infrastructure be tiered with a separate SQL server:

SQL Server

Item Quantity/Description

CPU 2 x vCPU

Memory 12 GB

Disk Disk space:

n Base OS + SQL = ~60 GB

n Database space = ~30 GB

n Temp DB space = ~50 GB (should be located on a separate LUN where possible)

Total: ~140GB

Operating System Microsoft Windows Server 2016 recommended SQL Server Microsoft SQL Server 2016 SP1 recommended

If using a shared SQL server, then a separate instance with the specification listed above is required for SysTrack

26

(27)

SysTrack Server

CPU 2 x vCPU

Memory 8 GB

Disk 60 GB

Operating System Microsoft Windows Server 2016 recommended Microsoft Components IIS roles and features

.NET 4.6.1

SysTrack Components SysTrack Master Server SysTrack Web Server

SysTrack Administration Tools

27

(28)

SysTrack with above 6,000 - 15,000 Agents

For installations with between 6,000 - 15,000 agents it is strongly recommended that the infrastructure be tiered with a separate SQL server:

SQL Server

CPU 4 x vCPU

Memory 16 GB

Disk Disk space:

n Base OS + SQL = ~60 GB

n Database space = ~60 GB

n Temp DB space = ~100 GB (should be located on a separate LUN where possible)

Total: ~220 GB

Operating System Microsoft Windows Server 2016 recommended SQL Server Microsoft SQL Server 2016 SP1 recommended

If using a shared SQL server, then a separate instance with the specification listed above is required for SysTrack

28

(29)

SysTrack Server

CPU 2 x vCPU

Memory 8 GB

Disk 60 GB

Operating System Microsoft Windows Server 2016 Microsoft Components IIS roles and features

.NET 4.6.1

SysTrack Components SysTrack Master Server SysTrack Web Server

SysTrack Administration Tools

If you are using SysTrack Virtual Machine Planner then additional hardware is required specifically for this component. These details can be found in the supporting documentation included in the SysTrack VDI Install Bundle pack available through the Lakeside Software portal.

29

(30)

Installing SysTrack

The SysTrack installation program allows you to install remotely to other systems. This is particularly convenient for handling remotely managed sites. After installing a Master System at the remote site via your WAN (a one-time process), all further agents at that site install from the local Master System image.

All SysTrack Administrative Tools are designed to allow both local and remote operation.

Installing SysTrack is a two-part process:

1. Installing the SysTrack server softwareusing the SysTrack Installation Wizard and Prerequisite Checker.

This includes the master server components, web services and SysTrack Deploy.

2. Using SysTrack Deployto add SysTrack agents to any child systems you wish to monitor; setting up and applying roles and configurations, and creating and making available the data required to allow Web Services to function.

30

(31)

SysTrack Installation - Getting Started

To begin the SysTrack installation:

1. Download the installation package from the Lakeside Software Inc. FTP site.

2. Extract the installation files to a location on your SysTrack master system.

3. Right-click on the Setup application and select Run as administrator from the resulting menu.

31

(32)

4. At the Welcome dialog, select the check box to accept the terms in the software license agreement.

6. Click the Next button to continue.

32

(33)

Selecting Installation Options

To complete the SysTrack installation, a number of installation options are presented on the Installation Options dialog. Default settings are shown below:

n Install SysTrack Services - installs the software for the SysTrack Master server including the services and database.

33

(34)

o Fully functional SysTrack Server Typical choice (default)

o Client Tools only SysTrack Server Connects to existing live SysTrack database

o Passive SysTrack Server Connects to offline copy of SysTrack database

n Install SysTrack Web Services - installs the files for web-based SysTrack applications such as SysTrack Visualizer, SysTrack Resolve etc.

n Install SysTrack Deploy - installs SysTrack Deploy used to configure and deploy the child system agents.

Optionally install SysTrack Analyze. Please note that this is a legacy product that is no longer supported or maintained.

34

(35)

1. Select the language to be used for SysTrack web-based applications.

Languages other than English are currently in Technical Preview mode and undergoing continuing improvements.

2. Click the Next button.

35

(36)

Selecting the Database Type

Clean (first time) SysTrack installations will display the Database Type dialog to have you either select an existing SQL Server database, or select to install SQL Server 2016 SP1 Express with Advanced Services for the SysTrack database. As a best practice we recommend you only use the included SQL Express for SysTrack installations that have less than 1500 systems.

1. Select the type of database you wish to connect. If you have an existing SQL Server database which has been configured prior to the SysTrack installation, select Connect to existing SQL Server to allow SysTrack services to connect the database.

For installations that include Non-Persistent Pooled Desktops, a full installation of Microsoft SQL Server will be required; SQL Server Express cannot be used. A “Pool” is a resource pool defined in the VM hosting farm (e.g. VMWare). This pool of resources simply claims a portion of the

CPU/Memory and other resources and designates them for use by the virtual machines that are assigned to that pool. These VMs can be persistent or non-persistent.

In SysTrack, the product can be configured to handle MSI installs for non-persistent virtual machines for a given pool. The Golden Image used for this process has a specially prepared config placed on it such that the agent knows it is in a non-persistent system when it starts up. This Golden Image cannot be used on a persistent VM interchangeably.

OR

2. Select SQL Server Express to install SQL Server Express 2016 (installations of less than 1500 systems). The SQL Express installation installs the following features:

n SQL Server Database Engine (SQLEngine)

n Client tools, SQL Server Books Online components (Tools)

n Reporting Services components (RS)

The SysTrack installer does not upgrade previously installed older versions of SQL Express to SQL Server 2016. If you need assistance with this, please contact Lakeside Software Technical Support.

Beginning with the release of Microsoft SQL Server 2016, Microsoft has removed the installation of Microsoft SQL Server Management Studio (SSMS) from the main SQL Server installation process. SSMS will be installed separately.

3. Provide a SQL Server system administrator (SA) account password following the password guidelines.

36

(37)

37

(38)

The SA password must follow strong SA password guidelines:

1. A strong SA password must:

a. Be at least 8 characters in length

b. Satisfy at least 3 of the following 4 required criteria:

n English UPPERCASE characters (A through Z)

n Base 10 digits (0 through 9)

n English lowercase characters (a through z)

n Non-alphanumeric characters (e.g. ! $ # %), excluding the following invalid characters:

o ( = ) equal sign

o ( ; ) semicolon

o ( ‘ ) single-quote

o ( “ ) double-quote 2. A strong SA password cannot:

a. Use empty spaces b. Prohibited words:

n password

n admin

n administrator

n sa

n sysadmin

c. Be associated with the installation computer:

n Login user

n Server name

4. If you have more than 1500 systems, select Connect to existing SQL Server. Information regarding the name of the server, instance, and database will be specified in theDatabase Specificationsdialog later in the install process.

5. Click the Next button.

38

(39)

Selecting a Reporting User Account

A reporting user account is needed for the following functionality:

n Ability to use the SysTrack reporting tools such as SysTrack Dashboard, SysTrack Visualizer

n Ability to access the SQL Server Reporting Services data source (to extract data from the SysTrack database for the reports)

n Ability to execute SQL requests from SysTrack dashboards if you don’t specify connection information

n Ability to open SSRS reports from SysTrack dashboards

1. Optionally enter domain user account credentials for the SysTrack Reporting User.

The Reporting User Account can only be an existing Domain user account; it cannot be a SQL account or a System Admin (SA) account. This account provides access to the SQL views that SysTrack creates in the SysTrack database and needs Allow Logon Locally permissions to the SysTrack server where SSRS is hosted. These views are created for reporting purposes. See Setting up a Reporting User Account below for setup information.

39

(40)

2. If you do not want to add a Reporting User Account at this time, leave the fields blank and click Skip. You will be able to add a Reporting User Account later. SeeSetting up a Reporting User Accountfor more information.

3. To add the optional Reporting User Account:

40

(41)

a. In the Reporting User field enter a Windows domain account and user name in the following format: <domain>\<user>.

b. Enter a password in the Password field.

c. Click the Test Credentials button to verify the credentials.

d. Click Next .

41

(42)

Setting up a Reporting User Account

If you do not add a Reporting User Account during the SysTrack install you can add a Reporting User Account by completing the following steps:

1. Add the permissions necessary for SSRS:

a. Open SysTrack Deploy, and click the ellipsis (...) next to the Master System’s Connection Type. Select the Reporting tab from the resulting Select Database Location window, and complete the Reporting fields. Click Test to test the connection.

b. Create an account in SQL Server Management Studio (SSMS) that is mapped to the SysTrack database.

c. In SysTrack Deploy open the Reporting Services Configuration Manager and select the Database Location dialog and check the report server data source for the reports, make sure the account used for the data source is the right account. If not, change it.

d. In SysTrack Deploy, select Configuration - Tools Access Security and grant user access as appropriate.

If necessary, you can laterchange the settings for Reporting User Accountvia SysTrack Deploy.

42

(43)

Installing the SysTrack Web Services

SysTrack Web Services (SysTrack Visualizer, SysTrack Resolve, SysTrack Dashboard etc) is installed on a 64-bit operating system following theSupported Operating Systemguidelines.

43

(44)

1. Enable the HTTPS (SSL) protocol, if desired by clicking the check box.

IMPORTANT: Choosing to enable HTTPS (SSL) protocol will require additional complex manual configuration steps after completion of this product install. Pleasecontact Lakeside Supportfor details before choosing to enable SSL.

2. Edit the Web Services logging path to change the location in which to store web service log files if you wish it to be different from the default of C:\Logs.

3. Click Next to continue.

44

(45)

Checking for and Installing Software Prerequisites

At the Software Prerequisites dialog the SysTrack installation determines which required software is already on the system, and which needs to be installed. SeeSupported Operating Systems and Prerequisitesfor details.

1. Wait while the prerequisite check runs. A list of prerequisites already installed and those still needing to be installed (if necessary) displays.

45

(46)

2. If prerequisites need to be installed, click the Install Prerequisites button.

Multiple system reboots might occur during this process. Wait until these have

completed. The Install Wizard will redisplay at the correct stage in the install process to continue.

3. Click the Next button when the prerequisite check and/or installation process is complete.

46

(47)

Verifying Database Specifications

1. At the Database Specifications dialog, enter or verify the SQL server database connection settings.

2. If you are using the SQL Express option, the fields will be pre-populated with default information, as well as the login and password you provided on theDatabase Typedialog.

3. If you selected the Connect to existing SQL Server option, specify the Login, Password, and Database you created during thedatabase preparation.

47

(48)

4. If instead you will be accessing the SQL Server database using Windows integrated security, select the Integrated Security... radio button. You must have a local system account to use this type of security. Integrated security uses the current Windows identity established on the operating system thread to access the SQL Server database. Since the Agent runs under the local system account, testing this connection will typically fail. This is because the installation program is running under your current user account. If the SQL Server is not on the Master System, the following computer account must be added as a valid login within SQL Server: [Master Domain Name]\MasterName$.

If the database you specified doesn't exist, one will be created automatically. However, it is highly recommended that you create the database and login beforehand. (SeeDatabase Preparation) 5. Click the Test Database Connection button. The SysTrack Installation verifies the database connection

and displays a status progress table as shown below.

48

(49)

6. If any of the database specifications do not pass the test, follow the recommendations listed in the Description column next to the failed item(s).

7. To continue with the install process, click the Next button.

49

(50)

Configuring the Reporting Server

1. A SQL Report Server is the central component of a Microsoft SQL Server Reporting Services (SSRS) installation. Using a SQL Report Server allows you to display various reports in SysTrack applications such as SysTrack Visualizer and Transform. Information aboutinstalling SSRSis included in the Pre-Installation Preparation topic.

If you will be using a SQL Report Server, you need to setup your report server and ensure that it is working correctly before completing this step.

If you selected to install SQL Sever Express, then the reporting services were installed automatically as part of the operation.

50

(51)

After the server is working correctly, you have two options:

n Select the Enter individual components to create a Report Server URL option, and then complete the information for each field for this option.

n If you know your report server's URL, select the Enter a Report Server URL option, and then enter the URL in the provided field.

51

(52)

TO COMPLETE THE SYSTRACK REPORTING CONFIGURATION:

Refer toCompleting the SysTrack Reporting Configurationfor information about modifying the connection/credentialsandchanging the report server used by a SysTrack Master System.

2. Enter an optional SSRS configuration User account to be used as a secondary account for a successful connection test to the report server.

3. Enter a password in the Password field.

4. Optionally, enter a windows domain user or group account to the SSRS Content Manager role in the optional Group or user name field.

5. Click the Test Report Server URL button to verify the connection.

6. Click Next to continue.

52

(53)

Processing the Installation Selections

1. At the Installation Summary dialog, click the Process Selections button to proceed with the installation.

2. Wait while the SysTrack services, Web Services, and Administrative tools (SysTrack Deploy) are installed.

The system will reboot to complete the installation. The SysTrack Installation Wizard will automatically restart and continue processing where it left off.

3. Continue with steps forconfiguring the agents and deploying them to the systemsto be monitored.

53

(54)

Using SysTrack Deploy

Afterinstalling the SysTrack software, your first task will be to add SysTrack agents to any systems you wish to monitor. This can be achieved using SysTrack Deploy.

1. Start SysTrack Deploy. The Address field automatically populates with the last Master System selected. If you want to change the Master System or if the Address field is blank, you will need to enter the system name or IP address of the Master System to which you wish to connect. Click OK to continue.

To successfully open SysTrack Deploy to connect to the master database requires the agent to finish creating tables etc. and initializing all threads.

2. Demonstration software users only: Each time you open SysTrack Deploy you are asked if you have purchased a non-demo version. Click No to continue with your trial period.

3. The first time you run Deploy, you will need to complete the Customer Information screen.

a. Any field with an asterisk (*) is required information. Demonstration software users will have the Customer ID filled in automatically. Full version users will need to supply the ID they were provided when purchasing the software.

IMPORTANT! You will not be able to run SysTrack Deploy, Analyze, or the SysTrack web applications until you have supplied the Customer Information (below) and registered your SysTrack licenses.

b. Select the number of licenses to assign this tree.

54

(55)

c. Click the Register via Internet button. If a connection cannot be made to the license server via the internet, click the Register via Telephone button and you will be provided with a telephone number to call to obtain an activation code.

55

(56)

Installing Agent Software on Child Systems

1. SysTrack Deploy opens. The Master System will be listed in the Systems pane, with an Install Status of Installed.

56

(57)

2. Before deploying to a remote Child System, you will need to supply SysTrack Deploy with proper administrative credentials that will allow installation on the remote systems. To do this, open the Deployment menu and select Deployment Credentials and Methods from the resulting list. Click Add to enter new credentials.

For this push deployment mechanism in SysTrack to work, File and Print Sharing must be enabled on the endpoints to which the agent will be deployed.

57

(58)

3. Complete the Administrative Credentials settings.

a. Select whether these credentials apply to a Domain, Logical Group, or specific System.

b. Enter a name for this credential set.

c. Enter the User ID, Password, and then Confirm the password.

d. Repeat the above steps for each Credential Type.

e. Click OK when you are finished.

58

(59)

4. Add the Child Systems that the Master System will monitor.

a. Use the trees on the left to select Child Systems for this master. Use <Ctrl> + click or <Shift> + click to highlight multiple systems.

b. Drag the system(s) from the tree to the Systems pane.

59

(60)

c. You will be prompted to select the appropriate credentials and database type for the systems being selected. The Lakeside Software, Inc. Services team recommends using Jet for most installations.

60

(61)

5. The status for these new systems will be Install Pending. Deploy periodically checks to install agents to systems in the tree. To install to the selected system(s) click the green play button. This forces Deploy to verify the current status of all systems in the tree. Attempts to deploy to all pending installs are completed at this time.

61

(62)

Alarms and Configurations

1. Selecting a system and then clicking on the ellipsis button (…) next to the configuration name will open the Alarms and Configuration screen. This screen allows you to edit system configuration settings such assetting up and applying roles and configurations.

62

(63)

2. Once a configuration has been saved, you can then select it from the drop-down list of available configurations for each Child System. Configurations are read by Child Systems once every 24 hours by default.

3. Right click on a system and select Read Configuration Now to immediately apply the updated configuration to the Child System.

Setting Up and Applying Roles and Configurations

For a more detailed explanation of Configurations and Roles, please refer to theSysTrack Configurations and Rolesdocument available on the Lakeside Software Support Portal.

To create a new configuration with roles:

1. Open SysTrack Deploy.

2. Open the Configuration menu and then select Alarming and Configuration from the resulting list.

63

(64)

3. Select Create New from the Select Configuration window.

4. Enter a meaningful Configuration name for the new configuration.

5. Review the list of available factory Roles by expanding each item. Click to highlight a desired role and then use the right arrows to move it to the Applied Factory Roles pane. Repeat this step until you have added all applicable factory roles.

6. Click the OK button to add the roles to the new configuration.

64

(65)

7. A window opens that allows you to review and change the configuration. Click OK when you are satisfied with the configuration.

65

(66)

8. To apply the role to a system: select a system, open the Configuration Name drop-down menu and select the new configuration from the resulting list.

9. Configurations are read by Child Systems once every 24 hours by default. Right click on a system and select Read Configuration Now to immediately apply the configuration to the Child System.

66

(67)

To add roles to an existing configuration:

1. Open SysTrack Deploy.

2. Open the Configuration menu and then select Alarming and Configuration from the resulting list.

3. Use the Configuration drop-down menu to select the configuration you want to add roles to and then click Edit.

4. After the Roles configuration window opens, use the right arrows to add roles.

5. Click Apply and then OK.

6. When the configuration edit is complete, it can then be attached to a specific Child System or group of systems in Deploy. The configurations that have already been applied to systems will now have the additional roles.

67

(68)

Setting Up SysTrack Web Services

After SysTrack Web Services have been successfully installed, you will need to configure SysTrack Deploy to create and make available the data required to allow Web Services to function. The following is the required SysTrack Deploy setup process.

1. Open SysTrack Deploy.

2. Open the Configuration menu and select Global Configuration Items from the resulting list.

68

(69)

3. Select the Visualizers tab. This tab allows you to enable the Enterprise and Desktop Visualizer processes.

Ensure that the Visualizer Enabled check boxes are checked for Enterprise Visualizer and Desktop Visualizer. (SysTrack Resolve is enabled by default.)

4. The Windows Desktop role (the default role) enables the Child System's View data to be condensed for the Enterprise and Desktop Visualizers. Refresh the SysTrack Enterprise and Desktop Visualizers by right- clicking on the Master System in the SysTrack Tree and selecting Refresh Visualizers Now from the resulting menu.

69

(70)

5. For the SysTrack vScape web application to function correctly, you must also set up the connection to the VM Management (VCenter/SCVMM) server(s).Deployment Credentials and Methods.

a. Open the Deployment menu, and then select Deployment Credentials and Methods from the resulting list.

70

(71)

b. On the Manage Deployment Credentials screen, select the Virtual Machine Managers tab, and then click the Add button.

71

(72)

c. Using the resulting Administrative Credentials screen, select the Credential Type. Enter the server's System Name, the User ID, Password, and then Confirm the password. Click OK.

d. Click Test to confirm that the connection to server works.

e. Click OK on the Administrative Credentials screen to return back to the main screen.

72

(73)

f. The Child Systems will need to read the updated configuration before they begin pulling host information. Configurations are read once every 24 hours by default. Right-click on a Child System and select Read Configuration Now from the list to send the new configuration to the Child System database immediately.

This will complete the setup of SysTrack Web Services in SysTrack Deploy. The SysTrack Web Services allow SysTrack Web Applications (described in the following table) to be opened and run on systems in the SysTrack Tree.

73

(74)

SysTrack Web Applications

Description

App Vision Provides a web-based interface for comparing real-time application performance data across a system or enterprise. Real-time data is updated every 10 minutes and includes CPU and memory.

Ask SysTrack A workspace analytics insight engine integrated into SysTrack web-based products and powered by IBM Watson that finds answers using natural language queries.

Configure Web-based interface for managing the SysTrack Agent including, Roles, Profiles, Configurations, Tools Access Security, Privilege Sets and Groups.

Enterprise Visualizer A module in SysTrack Visualizer that measures and reports on the quality of the end user experience -– providing a CIO perspective, by delivering a real time, C-level picture of what is happening within key organizational groups and across the entire desktop landscape.

Community Visualizer A module in SysTrack Visualizer that allows you to compare your systems' data with SysTrack industry averages. This feature will only be made accessible to SysTrack Community subscribers.

Desktop Visualizer A module in SysTrack Visualizer that measures and reports on the quality of the end user experience, and provides an IT Manager perspective of specific systems and users and in- depth problem diagnostics.

Persona Visualizer A module in SysTrack Visualizer that provides abstract models of real users based on work patterns, behaviors and tools of actual users in the environment to allow IT to distill users down to a manageable number of user types and understand what a persona requires from a hardware, security, and software perspective.

Risk Visualizer A module in SysTrack Visualizer that provides views to assist in identifying areas of potential security risk including details of application configurations and inventory, hardware, and systems configurations, and installed packages.

Server Visualizer A module in SysTrack Visualizer that presents metrics relevant to the various servers in an organization and allows the analysis of capacity, usage, and performance.

74

(75)

SysTrack Web Applications

Description

Virtual Infrastructure Visualizer

Provides information on how virtual hosts are performing. Key data points are provided to analyze host usage and understand which hosts are over/under utilized with the organization.

Resolve Provides heightened visibility into physical and virtual user desktops to allow IT to quickly diagnose and resolve problems.

Transform Generates real-time, dynamically updating analytics, reporting dashboards and workflow to facilitate management of transformation projects from initial design/architecture through steady state.

Operations Provides a high-level view and complete drill-down of all alarms across the enterprise.

Details of other performance metrics are available via drill down to SysTrack Resolve.

vScape Presents the health status of all managed systems in a dashboard format, showing multiple systems at once in a color-coded display that is updated in real-time.

Image Planner Provides a blueprint for implementation of VDI desktop pools and golden images for non VDI environments. Analyzes actual application license demand by tracking the use of application packages by users.

Dashboard Provides customized views of real-time data, offering insights into SysTrack data as well as external databases. Dashboards are created using the SysTrack Dashboard Builder.

SysTrack dashboards can be viewed from the SysTrack Dashboard Viewer and in Share Point.

Report Center Contains a centrally located library of reports that provide a customizable analysis of the latest SysTrack collected data created using SQL Server Reporting Services (SSRS). Each report is categorized by the SysTrack tool used to generate the data. For example, Image Planner reports contain a detailed breakout of software packages assigned to each Image within a Model.

Survey Survey Builder available from SysTrack Configure, provides a way to create customized surveys to present to end users and obtain feedback based on predetermined events.

Visualizer SysTrack tool that includes Desktop, Enterprise, Server, Risk, Virtual Infrastructure, Persona, and Community Visualizers.

75

(76)

Enabling SysTrack Direct Access

In SysTrack 8.3, the SysTrack communication layer was enhanced to support IPv6. This change allowed the child agent to condense data up to the master, and the master to request data from the child and issue commands over IPv6, and by extension, Direct Access.

To enable this:

1. In SysTrack Deploy, select Configuration – Global Configuration Items from the menu bar.

2. Select the Tree Settings tab.

3. Select Connect Using – System Name as shown below, and click the OK button.

MSI deployment is required. For more information contact Lakeside Support.

76

(77)

SysTrack Reporting Configuration

A SQL Report Server is the central component of a Microsoft SQL Server Reporting Services (SSRS) installation. Using a SQL Report Server allows you to include the Analyze Reports in various SysTrack applications such as SysTrack Visualizer and Transform.

Information aboutinstalling SSRSis included in thePre-Installation Preparationtopic.

Refer to theSetting up the SysTrack Web Servicestopic for instructions forsetting up the SQL Report Server.

To configure SysTrack Reporting Data Source credentials from the reporting services Configuration Manager:

1. Open the Reporting Services Configuration Manager.

2. Connect to the SSRS.

77

(78)

3. If the Reporting Service is not running, press the Start button.

78

(79)

4. Select the Report Manager URL located in the left pane, and then click the URL link in the right pane.

URL link example: http://<ReportServer>/Reports_SYSMGMT_DB You may need to add the following sites to the intranet zone:

http://localhost http://<ServerName>

79

(80)

5. Before you can complete the remaining steps, you will need the appropriate role assignment. The Browser role is the lowest user level; the level you assign depends on how you will be using SSRS. The location for role assignment depends on the version of SQL you are using. For example, if you are using SQL Server 2008 R2, role assignment is configured under Folder Settings as shown below.

Assign users or groups that will have access to the reports. The Domain Users or Everyone group can be assigned and then access controlled through SysTrack Deploy's Tools Access Security.

If you are using the Domain Users or Everyone group (as opposed to specific users or groups), and a user has direct SSRS Report links, they will be able to access the reports even if they haven't been granted access via SysTrack Deploy's Tools Access Security.

6. When you have completed assigning roles, click OK.

7. Click Home in the upper right corner.

8. Click on <ServerName> to open the root folder.

9. Click on Analyze Reports.

10. Click on Datasources .

80

(81)

11. Click on SysTrack Reporting.

12. Using the resulting form, make sure the Data Source is correct in the Connection string.

If SQL was installed using default instance: Data Source=<SQL Server Name>

If SQL was installed using a named instance: Data Source = <SQL Server Name>\<InstanceName>

(e.g. SYSMGMT_DB or Data Source=<SQL Server Name>\SYSMGMT_DB)

13. Set the correct security for connecting to the SysTrack database. Your selection depends on your database security. You can complete the set up for a specific reporting user, or you can use any of the other security options. In a typical install, you should use theReporting User Accountset up during the Master Setup installation.

14. Click the Test Connection button to test the connection.

81

(82)

15. Click Apply to apply the configuration after the settings are correct.

82

(83)

Reports should now be available in SysTrack Visualizer Reporting (as shown below), and in Transform.

83

(84)

To change the report server used by a SysTrack Master System:

1. Open SysTrack Deploy.

2. Select (highlight) a Connection Type. Click the ellipsis (...) to the right of the connection type.

You can select a Provider Type value for any system in the deployment tree table. Any changes made to the report server URL apply to all systems in the table.

3. Using the resulting Select Database Location dialog box:

a. Select the Reporting tab.

b. Update the Report Server URL using the following format:

http://<ReportServerName>/ReportServer/<ServerRootFolder>

c. Enter the User name and Password.

d. Click Test to test the updated URL and validate the entered User name and Password.

84

(85)

e. After the Test passes, click OK to save your changes.

85

(86)

Installing the SysTrack Dashboard SharePoint Plugin

If you are intending to use SysTrack Dashboard with Microsoft SharePoint you need to install the SharePoint Dashboard Plugin on the system that hosts your SharePoint server.

Only SharePoint 2013 in a Farm configuration is supported.

The SharePoint Dashboard Plugin is an integration tool for SysTrack Dashboard and the Microsoft

SharePoint Web app platform. It allows the user to create and view SysTrack Dashboards in SharePoint by clicking the SharePoint button in the SysTrack Dashboard builder. The user can also assemble SharePoint Dashboards manually from within SharePoint, editing individual Web Parts to link to external Dashboard parts.The SharePoint Dashboard maintains it's link to the original indefinitely, refreshing its content to reflect the original every time it is loaded. This effectively allows another method of viewing SysTrack Dashboards and integrating them into a standard SharePoint workflow.

Installing plugins to a SharePoint site requires Owner/Full Control Administrative privileges, particularly to Farms and Site Collections.

Plugin Files Location

The plugin files are located in the downloaded SysTrack installation package in the

CDImage/SysTrack/program files/SysTrack/SharePoint Plugins folder and are installed on the Master server where the SysTrack Master Setup is installed (e.g . C:\Program Files\SysTrack\SharePoint

Plugins). The files include two PowerShell scripts, lsi-spInstall.ps1 and lsi-spRemove.ps1, that automate the installation process. Both operate on the last plugin file, SysTrackDashboards.wsp.

If any of the installation files are moved, you must ensure all files are still in the same folder.

Before you Begin

You will need to know the following information before you begin:

n The name of the SharePoint server (e.g. lsi_sp)

n The SharePoint site on the SharePoint server (e.g: "http://lsi_sp")

n The SharePoint Web Application hosting the SharePoint site (e.g. "SharePoint - 80")

n The name of the machine on which the SysTrack Master is installed (e.g: "http://<machinename>)

86

(87)

Installation Instructions

To install the SharePoint Dashboard Plugin:

1. On your SharePoint system, run the SharePoint Management Shell as an Administrator. (It is important that the shell has access to your credentials, as they allow editing of the SharePoint site).

2. In the SharePoint Management Shell, navigate to the folder containing the plugin files.

3. If there is already a SharePoint Dashboard Plugin installation running on your system, you need to remove it using the following uninstall command:

.\lsi-spremove <SysTrack api machine> <SharePoint server>substituting actual names appropriate to your systems (e.g. .\lsi-spremove http://d72gm http://lsisp2)

4. Install the plugin solution using the install command:

.\lsi-spinstall <SysTrack api machine> <SharePoint server><SharePoint web app><SharePoint site>

substituting actual names as appropriate to your systems (e.g .\lsi-spinstall http://d72 lsi_sp "SharePoint - 80" http://lsi_sp)

The install script adds the solution file (WSP), deploys it to the web application selection (SharePoint), and enables the SysTrack Dashboard SharePoint display feature for the selected site. The SharePoint button in Display icon on the top right of the SysTrack Dashboard Builder will be enabled.

Script Help

For more in-depth information on the install and remove scripts use the get-help command. (For example:

get-help .\lsi-spinstall.ps1 -full

SysTrack 8.3 Installation Guide