systrack agent deployment guide

1 LAKESIDE SOFTWARE OFFICIAL INFORMATION

© Lakeside Software, LLC. 1997-2021. Last updated 10/25/2021. Lakeside Software and SysTrack are registered trademarks and/or trademarks of Lakeside Software, LLC. All other trademarks and registered trademarks are the property of their respective owners. Lakeside Software and SysTrack are protected by US patents #6,978,265, #7,257,692, #7,865,499, and #8,819,639.

Technical Documentation

SysTrack 10.0 Agent Deployment Guide

Contents SysTrack Agent Deployment ......................................................................................................................... 3

SysTrack Agent Deployment Preparation ..................................................................................................... 3

Systems Management Agent (Endpoint MSI) System Requirements ..............................................................3

Master to Endpoint Certificate Migration .......................................................................................................4

Adding the Certificate to Trusted Root on the Master ................................................................................4

Exporting Certificates ...................................................................................................................................4

Copying the Certificate to Endpoint Systems ..............................................................................................4

Non-Persistent Virtual Machines .....................................................................................................................5

Installing Agents in an Environment with Deep Freeze ....................................................................................5

Security Best Practices......................................................................................................................................5

Installation Call Preparation.............................................................................................................................5

Deployment Methods ................................................................................................................................... 6

Choosing the Method of Deployment ..............................................................................................................6

Physical Systems ..........................................................................................................................................6

Virtual Machines ..........................................................................................................................................6

Antivirus Exclusions ......................................................................................................................................8

Deep Freeze Environment............................................................................................................................8

Deploying Endpoint Systems ........................................................................................................................ 10

Adding Endpoint Systems to the Current Tree ......................................................................................... 10

MSI Deployment ........................................................................................................................................... 11



MSI: Agent Installation on Non-Persistent Terminal Servers .................................................................... 12

VDI Assessment ........................................................................................................................................... 15

License Activation .......................................................................................................................................... 16

Create the Configuration(s) ........................................................................................................................... 17

Configuration Setup for a VDI Assessment ............................................................................................... 18

Set the Default Configuration for New Systems ............................................................................................ 20

Enter Deployment Credentials ...................................................................................................................... 20

Add the Endpoint Systems ............................................................................................................................ 22

Deploy to the Endpoint Systems ................................................................................................................... 22

Deployment Troubleshooting ................................................................................................................... 22

Verifying Data Collection ............................................................................................................................... 23

Uninstalling SysTrack Agents ...................................................................................................................... 24

Frequently Asked Questions (FAQs) ........................................................................................................... 24

How much network traffic is generated? What kind of impact will there be on the network? .............. 24

How large will the SysTrack Master database grow? ............................................................................... 24

A SysTrack Tree with 1,000 reporting systems will result in a database of around 2.5 GB of data (average of 2.5 MB per system). This is scaled linearly, meaning that an environment with 10,000 systems should have a database of 25 GB. Customization of collection or modification of retention intervals may have a large impact on this size, and any changes should be validated prior to being committed. ................... 24

Is there an agent that gets installed on the endpoint systems? ............................................................... 24

Does the installation require a reboot? .................................................................................................... 25

Does SysTrack utilize security practices? .................................................................................................. 25

Next Steps ................................................................................................................................................... 26



SysTrack Agent Deployment

The SysTrack Agent can be deployed to endpoint systems in a variety of ways. Once deployed, the Agent will establish a connection with the Master System and start collecting data. Over time, the collected data will be sent to the Master System for analysis using the SysTrack tools.

This document addresses deployment of the SysTrack Agent to Windows endpoint systems. For more information regarding Agent deployment to other supported Operating Systems, see their respective Installation Guides.

SysTrack Agent Deployment Preparation

For database sizing and resource load information, see SysTrack Resource Footprint.

Systems Management Agent (Endpoint MSI) System Requirements

• Microsoft Windows 7 Service Pack 1 (SP1), with latest Windows updates • Microsoft Windows 8.1 (with Update 2919355) • Microsoft Windows 10 (version 1507 or higher) • Microsoft Windows Server 2008 SP2 • Microsoft Windows Server 2008 R2 SP1 • Microsoft Windows Server 2012 • Microsoft Windows Server 2012 R2 (with Update 2919355) • Microsoft Windows Server 2016 • Microsoft Windows Server 2019 (or higher) • Firewall setup – See SysTrack Resource Footprint for SysTrack port information.

Complete the following preparations prior to installing the SysTrack Agent.

The database server to which the SysTrack server is connected must reside in one of the following locations:

• The same domain as the SysTrack server, or • A domain that trusts the domain in which the SysTrack server resides.

1. When Symantec antivirus exists on the endpoint system, file and printer sharing must be enabled in the antivirus application.

2. For Push Deployment, file and printer sharing must be enabled on each endpoint system and a user account credential defined with proper rights for the agent to be installed on the endpoint system.

https://portal.lakesidesoftware.com/docs/SysTrack_9.0_Resource_Footprint.pdf




Deploying the agent software can be done through an Enterprise Software Delivery system such as SCCM. Instructions for this type of deployment are in SystemsManagementAgent.pdf, which can be found within the Installation Media.

Master to Endpoint Certificate Migration

If the associated master is using a self-signed certificate, then you need to migrate that certificate to the endpoint systems. Complete the following steps to add the certificate to Trusted Root Certification Authorities and export it for endpoint system use.

Adding the Certificate to Trusted Root on the Master

1. Open MMC.exe. 2. Copy and paste the certificate created from Personal > Certificates to Trusted Root Certification

Authorities > Certificates.

Exporting Certificates

1. Navigate to Personal > Certificates. 2. Right-click All Tasks > Export. 3. Click Next twice. 4. Select Base-64 encoded and click Next. 5. Select Browse. 6. Name the file (example: <master>Cert.cer) and save it under Downloads. 7. Click Next and then click Finish.

Copying the Certificate to Endpoint Systems

1. Move the certificate to the endpoint machine’s file system. Using Error! Hyperlink reference not valid. is recommended.

2. Open MMC.exe. 3. Right-click Certificates under Trusted Root Certification Authorities. Then select All Tasks > Import. 4. Click Next. 5. Browse for the certificate you want to import. 6. Click Next twice, and then click Finish.



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-persistent system when it starts up. This Golden Image cannot be used on a persistent VM interchangeably.

Installing Agents in an Environment with Deep Freeze

You will need to follow special instructions when installing SysTrack in an environment utilizing Deep Freeze. Refer to Deep Freeze Environment for more information about deploying in a deep freeze environment.

Security Best Practices

For information regarding SysTrack security best practices and minimum-security requirements, see the SysTrack Security Best Practices document on the Lakeside Software customer portal.

Installation Call Preparation

Complete the following preparation steps prior to the installation call with Lakeside Support.

1. Download and unzip the SysTrack installation package and place it on the master system. 2. Use the local Administrator Account to load software. 3. For push deployment installations, file and print sharing must be enabled on the endpoint systems

prior to attempting installation. For MSI installations, file and print sharing does not need to be enabled. See SysTrack Resource Footprint for port information.

https://portal.lakesidesoftware.com/docs/SysTrack_Security_Best_Practices.pdf




Deployment Methods

There are several options to choose from to deploy the SysTrack Agent to endpoint systems. The Agent is responsible for all data collection and moving data to the next highest level in the tree. The Agent is usually deployed to Windows systems without manual interaction from the system administrator. An endpoint system only requires a reboot to complete installation in the rare instance when a system needs an updated MDAC or WMI. If a reboot is required, it will not be forced as part of the installation process and will instead take place automatically at the time of the next reboot.

Choosing the Method of Deployment

This section describes how to select the correct method of deployment for two types of endpoint systems: physical systems and virtual machines.

Physical Systems

• Push Deployment is the default method of deployment due to its simplicity. As the name implies, the master system pushes the installation files down to the endpoint system. When using this method, the following requirements must be met:

• Credentials with sufficient level of access must be provided • File/Print sharing must be enabled

• MSI Deployment is the most convenient method for large volumes of deployment. This method does not have file and print sharing requirements. Deployment occurs either through a Software Distribution Tool or by running a script through GPO.

Virtual Machines

Non-Pooled virtual machines (those not being cloned from a Golden Image/system) can be deployed in the exact same manner as physical systems.

For pooled virtual machines, there are two types of pooled desktops:

• Persistent Pooled Desktops • Non-Persistent Pooled Desktops

For any operating system that supports more than one user being logged in and active at a time from Server OS to Windows Virtual Desktop, see Non-Persistent Multi-Session Virtualization.



Persistent Pooled Desktops

This deployment method depends on how new images will be spun up from the Golden Images. There are two possible scenarios:

• If the cloned system SID changes (physical, SysPreped systems generally change SIDs), the agent is installed on a Golden Image and keeps running. Every time a new system is spun up, the agent will request a new GUID for the cloned system. It will be seen as a new endpoint by the master. The procedure of this deployment in described in the Systems Management Agent - MSI Installation Instructions document on the portal.

• If the cloned system SID does not change, there are three options:

• Non-Persistent desktop requires SQL Server 2008 R2 Service Pack 1 and above (no Express versions) for the master database and increased endpoint-master connectivity dependence. Data is collected on a per-user basis rather than per-system.

• Regular MSI or Push Deployments involve performing the installation after the persistent systems have been created without having the Golden Image involved in the process.

• Pooled DB mode deployment is similar to the non-persistent terminal server use case.

Non-Persistent Pooled Desktops

In this deployment method, the agent is installed on the Golden Image using a special MSI deployment method. Once the installation is complete, the agent stops immediately and resides passively on the Golden Image. Once a new image is spun up from the Golden Image, the agent starts on the cloned image. By reading the property fields it has been installed with (for example, “POOLEDDB”), it sends information up to the top based on the user account (not the system name). The cloned image will appear in the Deployment Tree as a user account (not as a system name).

Non-Persistent Multi-Session Virtualization

You can use this deployment method if you are using a Server OS VDI with no persistent storage.

Important: Do not use the Jet (MDB) database on a file share; doing so will corrupt the database.

Lakeside Software supports the use of the LocalDB option (a SQL Server database option) on a file share. To use the LocalDB option on a file share, complete the following steps.

1. Map a drive to a location (for example, \\server\share\%COMPUTERNAME%). You’ll need to map the drive as a system so that the location is available when the server starts up. To map the drive, you can create a start-up script with the following commands.

a. Run an elevated cmd window

https://portal.lakesidesoftware.com/docs/SystemsManagementAgent_9.0.pdf

https://portal.lakesidesoftware.com/docs/SystemsManagementAgent_9.0.pdf



b. psexec -i -s cmd.exe

c. whoami To make sure you are nt authority

d. net use L: \\server\share\%COMPUTERNAME% /persistent:yes

2. Install the agent to use LocalDB on the new drive.

3. Seal the Golden Image.

Antivirus Exclusions

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

• File and Print Sharing should be enabled on the target endpoint systems, along with Remote Registry Service.

Make sure to check that the following antivirus settings are excluded in the antivirus console:

• Endpoint 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 Block Applications from running option is enabled in the SEP policy, exceptions will have to be made to the Application and Device Control settings. Additionally, the SysTrack agent and associated utilities must be allowed to run to collect data.

Deep Freeze Environment

For the SysTrack agent to be installed on a Deep Freeze device, the device needs to be thawed. Next, redirect the local database to the thawed partition. After the agent is installed and communicating to the master system, the main drive can be frozen again, and the data will write to the other partition. The agent can be deployed via an MSI using a pooled db model which will direct the database to the thawed drive.

Use the following command line syntax for installing the SysTrack agents on the endpoint systems via MSI.

1. For 32-bit and 64-bit operating systems, use the following command for the runtime executable required by the SysTrack agent (the log is optional):

vc_redist_x86.exe /q /norestart /log <enter path to a temp folder>\VCx86.log

2. For 64-bit operating systems only, use the following command for the runtime executable required by the SysTrack agent (the log is optional):




3. Complete the SysTrack agent installation. Use this command to install the agent into a thawed folder on the machine. Replace “D:\<path>” with the actual location where you would like to install the agent:

msiexec.exe /qn /i “<path to install files\Systems Management Agent_x32.msi” ALLUSERS=1 REBOOT=R MASTERNAME=<MASTER NAME> INSTALLDIR=”D:\<path>\SysTrack”

4. Use the following command to place the SysTrack agent in the default directory of C:\Program Files (x86)\SysTrack and put the SysTrack local database on a thawed drive:

msiexec.exe /qn /i “<path to install files\Systems Management Agent_x32.msi” ALLUSERS=1 REBOOT=R MASTERNAME= <MASTER NAME> POOLDB=”<path to thawed drive>”

Refer to MSI Deployment for more information about MSI.



Deploying Endpoint Systems

This section describes the deployment of the Systems Management Agent to endpoint systems via the SysTrack Configure web application.

Adding Endpoint Systems to the Current Tree

Complete the following steps to assign the appropriate credentials to the software prior to deploying the agent to monitored systems.

1. In SysTrack Configure, navigate to the Systems tab on the Assignments page and use the + (plus) icon to add a system to the tree.



2. Add the name of the system in the dialog and click the Add button.

3. After all systems have been added to the tree, if updates are not currently running, mark the Allow Updates checkbox in the menu bar and click the Play button to update endpoint systems in the tree.

MSI Deployment

MSI is an installer package file format used by Windows. Its name comes from the program’s original title, Microsoft Installer, which has since changed to Windows Installer. A SysTrack MSI installation is driven by



the endpoint system. For a detailed guide on MSI installation, refer to the Systems ManagementAgent.pdf in the Installation Packages folder in the SysTrack installation directory on the master system.

MSI: Agent Installation on Non-Persistent Terminal Servers

Special steps are required to successfully install the SysTrack endpoint agent using MSI to a pool of non- persistent terminal servers. Note that these terminal servers must have a persistent drive associated with them for the endpoint database location.

Prior to SysTrack version 6.1.520, installation and upgrades required the use of the STServerPrep utility. That utility is no longer needed.

Complete the following steps to install and configure the SysTrack agent.

1. Perform MSI installations to the Golden (master) Image (see SystemsManagementAgent.pdf in the Installation Packages folder for more detailed instructions. Follow the Pooled System section of the SystemsManagementAgent installation):

a. Copy the following files from the SysTrack master system to the master image. These files are located in the InstallationPackages folder of the SysTrack installation directory.

• vc_redist_x86.exe – 32 bit and 64-bit operating systems • vc_redist_x64.exe – 64-bit operating systems only • Systems Management Agent_x32.msi (Standard, Or non-persistent desktop)

Lakeside Software requires the latest supported Visual C++ downloads. See Microsoft’s latest supported Visual C++ downloads article for more information.

b. Open a command prompt window (Run as Administrator). Navigate to the directory where the above files were copied.

You must install VC runtime before installing Systems Management Agent_x32.msi.

2. For 32-bit and 64-bit operating systems, enter the following command and follow the prompts (the log is optional):


3. For 64-bit operating systems, enter the following command and follow the prompts (the log is optional):

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads




4. Enter the following command and follow the prompts:

msiexec.exe /i “Systems Management Agent_x32.msi” ALLUSERS=1 REBOOT=R MASTERNAME=name_of_the_SysTrack_master POOLDB=”K:\SysTrack\Database\%SYSTEMNAME%\“/L*v <enter path to a temp folder>\ChildAgentMSI.log

You can change the POOLDB location, but you should use %SYSTEMNAME% (all capital letters) to prevent duplication of data across cloned/copied systems. For example:

Jet only:

(LOCALDB=0) POOLDB=”K:\SysTrack\Database\%SYSTEMNAME%\”

Terminal Server only (where “K” is an example drive letter):

(LOCALDB=1) POOLDB=”LocalDB:K:\SysTrack\Database\%SYSTEMNAME%\”

5. Navigate to C:\Program Files (x86)\SysTrack\LsiAgent. Open LsiAgent1.log and verify that it contains a line stating “Pooled System.”

For 32-bit OS, use C:\Program Files\SysTrack\LsiAgent.

6. Open regedit and navigate to the following registry location:

• For 32-bit: HKLM\Software \Lakeside Software\Deploy

• For 64-bit: HKLM\Software\Wow6432Node\Lakeside Software\Deploy

7. Verify that the PoolDB entry contains a valid file location accessible from this machine by the local system account. A path should be assigned to the persistent storage location/directory where the database will be stored and should not include the file name.



8. Clean up the Golden Image:

a. Stop the Systems Management Agent service.

b. Delete the existing log files:

• For 64-bit: C:\Program Files (x86)\SysTrack\LsiAgent\*.log

• For 32-bit: C:\Program Files\SysTrack\LsiAgent\*.log

c. Delete the existing collection database folder:

K:\SysTrack\Database\%SYSTEMNAME%\

9. Important: After a successful Pooled System installation on the Golden Image, delete the Settings registry key (if it exists) for potentially better results on virtual systems before cloning:

• For 64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Lakeside Software\LsiAgent\Settings

• For 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Lakeside Software\LsiAgent\Settings

10. Important: Beginning with SysTrack Version 8.2.312, new registry keys are available to redirect all logs and files written by SysTrack to the write cache directly. After a successful Pooled System (POOLDB) installation on the Golden Image, complete the following manual steps:

a. Open regedit on the PVS Golden Image.

b. Navigate to the following location:

• For 64-bit: HKEY_LOCAL_SYSTEM\SOFTWARE\Wow6432Node\Lakeside Software\Deploy

• For 32-bit: HKEY_LOCAL_SYSTEM\SOFTWARE\Lakeside Software\Deploy

c. Edit/Create the string registry values named PoolDB_LogFolder and PoolDB_WriteFolder to have the same information as the registry value named PoolDB. If a different value is selected, the directory in the registry value must already exist.

After these steps are completed and verified, the image may be used to provision new systems.



VDI Assessment

This section describes how to configure SysTrack for a basic VDI assessment.

After the master system installation (Master Setup, Web Services, and Administrative Tools) and activating licenses, there are three basic steps required to configure SysTrack:

1. Create the configuration(s).

2. Set the default configuration.

3. Enter deployment credentials for pushing the SysTrack agent to the endpoint systems. After configuring, endpoint systems are added to the tree and the agent is deployed.



License Activation

The SysTrack master system must be restarted before using SysTrack Deploy for the first time.

The Customer Information window will display the first time SysTrack Deploy runs.

1. Enter the customer ID assigned by the Lakeside Software Sales department. 2. After entering the valid ID, complete the remaining fields on the left side of the window. The

number and types of licenses assigned are shown in the Initial Purchase area at the top right of the window.

3. Enter the same numbers in the Licenses to assign to this tree area and duplicate these numbers for the VMP licenses to assign. For example, if the Initial Purchase area shows 1 Server, 100 Workstations, and 5 Terminal Servers, enter 1 Server, 100 Workstations, 5 Terminal Servers, 1 VMP Server, 100 VMP Workstations, and 5 VMP Terminal Server licenses.

4. After the data collection period is over and the Virtual Machine Planner tool runs, the VMP licenses must be activated.

5. Leave the default settings for the Desktop Level and SysLock fields. 6. Click Register via Internet.



If internet registration fails, a Manual Licensing Registration window displays. You can take a screenshot of this window and send an email to [email protected] or call the Lakeside Software Technical Support department at 248-686-1702. Leave this window open until you receive an activation code.

Create the Configuration(s)

Make sure to restart the SysTrack master server before using the Deployment Tool for the first time.

1. Launch SysTrack Deploy.

2. Select Configuration > Alarming and Configuration from the menu bar.

mailto:[email protected]



3. At the Select Configuration window, click Create New.

Configuration Setup for a VDI Assessment

1. For all VDI assessments, name the configuration.

2. Expand Base Roles in the Available Factory Roles area, select the Windows Desktop role, and click the >> button to move that role to the Applied Factory Roles area.

3. Scroll down in Available Roles and expand the Assessment category. Select VMP and move it to the Applied Factory Roles area.



4. Click OK, and then OK again to save the configuration.



Set the Default Configuration for New Systems

1. Select Deployment > Set Default Configuration for New Systems from the menu bar.

2. From the Configuration drop-down, select the configuration you created and then click OK.

Enter Deployment Credentials

Credentials are required for all Push deployments from the Deployment Tool. Credentials are not required for MSI installations.

1. Select Deployment > Deployment Credentials and Methods from the menu bar.



2. Click the Add button.

3. Enter the credentials of an account that has administrative rights on the endpoint systems, such as a domain admin account.

4. Click OK. More than one set of credentials may be added if needed. For each endpoint system, the deployment process will cycle through the credentials until it finds a set that has rights on that system.



Add the Endpoint Systems

When deploying the SysTrack agent to the endpoint systems using MSI installation manually or through a software distribution system, the endpoint systems will automatically be added to the SysTrack tree upon successful installation.

If pushing the agent to the endpoint systems from SysTrack Configure, you will need to add the endpoint systems to the tree on the Assignments page in SysTrack Configure.

Deploy to the Endpoint Systems

Once all endpoint systems have been added to the tree (if required), make sure updates are running on the Assignments page in SysTrack Configure.

The Install Status of each system will change as the installation process progresses. Once a system indicates a status of Installed, it is collecting data.

Systems that are deployed via MSI installation will automatically appear in the tree after successful installation.

Deployment Troubleshooting

Issues related to systems that do not successfully install the SysTrack Agent are almost always easily resolved. In a typical SysTrack deployment, approximately 10% of the systems will result in an Install Status other than Installed. Most of the issues associated with an Install Status of Install Pending or Upgrade Pending are a result of a connection problem.

The following is a list of items to troubleshoot:

1. Make sure File & Print Sharing is enabled. 2. Make sure the deployment credential you defined is valid. 3. Ping systems from the SysTrack master to ensure they are powered on, communicating on the

network, and reachable from the master system. 4. Connect from the master system using UNC Path with the username and password defined in the

Deployment Tool: \\<system name>\C:\Program Files. This ensures that the Deployment Tool has access to the Admin Share on the endpoint system.



5. If any or all of the above work as expected, RDP into the endpoint system and see if you can ping back to the Master.

If none of the above is determined to be the problem, we recommend that you contact Lakeside Software Technical Support for assistance.

Verifying Data Collection

Verify that data is being collected on any endpoint system with a status of Installed by using SysTrack Resolve. The SysTrack Master will contact the endpoint agent to collect information on what is happening on that system at that moment.



Uninstalling SysTrack Agents

You can uninstall the SysTrack Agent from the client systems in one of three ways:

• From the Assignments page in SysTrack Configure • From SysTrack Deploy • By using a command delivered to the client systems through a batch file or startup script

For assistance with the uninstall process, contact SysTrack Customer Support at [email protected].

Frequently Asked Questions (FAQs)

How much network traffic is generated? What kind of impact will there be on the network?

We employ a patented Distributed Database Architecture in which the data is distributed across each of the individual monitored systems. SysTrack condenses and sends approximately 150 KB of data up to the top-level master once per day per monitored system. Data is randomized and is not sent from all the systems at the same time. We do not employ a Central Data Store model, which means we are able to scale in an enterprise environment to more than 100,000 monitored systems.

How large will the SysTrack Master database grow?

A SysTrack Tree with 1,000 reporting systems will result in a database of around 2.5 GB of data (average of 2.5 MB per system). This is scaled linearly, meaning that an environment with 10,000 systems should have a database of 25 GB. Customization of collection or modification of retention intervals may have a large impact on this size, and any changes should be validated prior to being committed.

Is there an agent that gets installed on the endpoint systems?

Yes. The agent executable is installed on the endpoint system and maintains a very small resource footprint, consuming less than 0.5% of CPU on average. Memory Usage of the agent varies based on the system. There are no Kernel Mode components, so the agent will not cause blue screens or destabilize the system. See the SysTrack Resource Footprint document for more information.

mailto:[email protected]




Does the installation require a reboot?

Only the initial Master system installation requires a reboot. The agent installation on endpoint systems does not require a reboot. In fact, there will be no disruption to end users when deploying the SysTrack agent; it installs silently in the background without impact, and users can continue any tasks unhindered. Users will be unable to detect that SysTrack resides on their systems.

Does SysTrack utilize security practices?

Yes, SysTrack supports authentication and encryption, utilizing Package Negotiator, NTLM, and Kerberos. SysTrack is designed to easily bolt on to an existing AD security infrastructure. SysTrack also has its own built-in Tool Access Control to further monitor the product features and capabilities to which users have access.



Next Steps

For detailed information on the features and functions of SysTrack, refer to the knowledge base, product support documents, and videos available on the Lakeside Software customer portal at http://portal.LakesideSoftware.com/Support. These sources can help you diagnose installation or operational issues and understand how the components of SysTrack operate.

Lakeside Software, LLC 40950 Woodward Avenue Bloomfield Hills, Michigan 48304 www.LakesideSoftware.com +1 248 686 1702 (Americas) +55 800 878 1210 (Brazil/Latin America) +44 (0) 1753 260081 (EMEA) +61 (2) 8413 0944 (ANZ)

http://portal.lakesidesoftware.com/Support/

http://www.lakesidesoftware.com/

systrack agent deployment guide

Documents