Introduction
SSI stands for SummitAI System Information Agent. The SSI agent is installed on the client’s machine that helps in extracting information about the Hardware and Software. The SSI Agent reports if the machine or a device is online or offline. SSI Agent helps in connecting remote machines using stealth mode. The SSI Agent retrieves license keys and device information. The SSI Agent is written in C++. The SSI Agent is always prefixed by the number 3.x.The following section describes the various updates of the SSI Agent versions and the enhancements available with each updated version.
SSI Versions and Enhancements
The following table describes the various versions of the SSI Agent and the fixes and enhancements available in each of these versions:
Version# | Fixes and Enhancements |
| 3.0.3.10 | In this version, the WMI Event Consumer functionality is added. Also, the code optimization is done to include the following enhancements:
|
| 3.0.2.16 | In this version, the code optimization is done to include the following enhancements:
|
| 3.0.2.15 | In this version, the following issue of SIERRA SP1 HF01 B005 is fixed. AM-->SSI agent: Software details were not getting captured when an agent was getting contacted and verified in the ScanResults.xml. |
| 3.0.2.14 | In this version, the following issue of SIERRA SP1 HF01 B003 is fixed. AM-->SSI agent: Software details were not getting captured when an agent was getting contacted and verified in the ScanResults.xml. |
| 3.0.2.13 | In this version, the following issue of build v3.0.2.12 is fixed. Roaming URL functionality was not working when an IP address was changed as it was not getting updated in the Configured Proxy. |
| 3.0.2.12 | This version includes the following changes:
|
| 3.0.2.11 | This version includes the following changes: 1. Retrieving of the Software Usage Data, Logon details, Additional details, and Device manager details and license information based on the value of the key "DISABLE_SCAN" in the Online status response file. 2. Added quotes to Service Paths during installation in the Windows Registry. Note For the End Point compliance or additional information, True is given more priority. |
| 3.0.2.10 | This version provides merging of SW, HW along with the License Inventory and WinLogon details in a similar format as SAM Agent. 1. If <FileName> is empty, extract the filename from PAth or from OriginalFileName. 2. Sort the MAC addresses and change the posting type of Merged XML for both full and differential. MCPP_SCAN_DATA > AGENT_SAMCPP_SCAN_DATA_MRGD |
| 3.0.1.30 | In this version, the code optimization is done to include the following enhancements:
|
| 3.0.1.29 | In this version, the software usage and its components are discovered based on the value of flag “SW_USG_EN” as follows: 1. If “SW_USG_EN” is False, only the software details are discovered. 2. If “SW_USG_EN” is True, the software details along with usage and components of the software are discovered. Note By default, the flag value is False. Note Full and differential data functionalities work with both the values of the “SW_USG_EN” flag. |
| 3.0.1.28 | In this version, the following defects are fixed: 1. Incorrect value of the RAM Size that was caused by the use of the wrong condition in the WMI Query. 2. Incorrect value of the RAM Quantity (Number of RAM Chips) that was caused by the use of the wrong condition in the WMI Query. |
| 3.0.1.27 | In this version, the following defects that are reported in the customer Panasonic environment are fixed: 1. Unable to capture and display the value of RAM Size 2. Unable to capture and display the OS version of Microsoft Windows. Also, a double quote is added for the “SummitSystemInformation” and “SummitAgentMonitorSvc” services while installing it in the Windows Registry for the first time. |
| 3.0.1.26 | Two new tags are added. Added tag “<Agent_Type>SSI</Agent_Type >” in the Endpoint Compliance “who am I” XML. Added tag “<Agent_Type>SSI</Agent_Type >” in the Endpoint Complaince output XML, which is posted to Web Services.3.0.1.25 |
| 3.0.1.25 | This version is integrated with new version of SymRemote v 3.2.1.5. This version discovers the Windows Patches using the WMI query. |
| 3.0.1.24 | This version integrates SymRemote that displays pop up to the End User. This pop up prompts the End User to share the screen based on time interval of 0, -1, and more than 0 value. |
| 3.0.1.23 | When SSI is installed on a machine, it could not kill SymRemote.exe started by previously installed SAM Agent. Paths SymRemote.exe of SAM Agent and SSI agent are different. This version cleans the SymRemote leftovers of previously installed SAM Agent. |
| 3.0.1.22 | This version considers SymRemote v3.2.1.3 as the base version. If SymRemote with earlier version exists in the machine, the Agent detects and deletes the earlier version. |
| 3.0.1.21 | Earlier, if the "SymRemote" is installed as an application, "SymRemote" did not work on UAC-enabled machines. "SymRemote" is installed as a Service from this version and "SymRemote" works properly on UAC-enabled machines. |
| 3.0.1.20, 3.0.1.19, and 3.0.1.18 | This version provided solution to retrieve Adobe and Office 365 license keys, which the earlier versions failed to do. |
| 3.0.1.17 | Earlier, the license keys of Non-CC Adobe products were not getting discovered. Now, the license keys of Non-CC Adobe products can be discovered. Also, the Agent retrieves DigitalProductID and ProductCode of Windows OS and Internet Explorer on Windows 10 machine this version onward. |
| 3.0.1.16 | The encryption/decryption algorithm followed FIPS compliance from this version and fallback mechanism was not applied. |
| 3.0.1.15 | In the earlier versions, the WMI query was hardcoded and the results generated gave incorrect data and few Windows features were not discovered. The hardcoded WMI query was removed, the results generated gave correct information. The Windows features, which were not discovered earlier could be discovered in this version. |
| 3.0.1.14 | Enhancements are made in this version. The code in optimized to improve the speed since the Software Discovery and Last usage module was time consuming. About 15 to 30% reduction in time is achieved in this version compared to 3.0.1.13 or the previous versions. |
| 3.0.1.13 | Earlier, the Agent did not retrieve dynamic data. The Agent only retrieved static data. This version retrieved dynamic data by using Modified Endpoint Compliance. |
| 3.0.1.12 | This version includes the Endpoint Compliance module. |
| 3.0.1.11 | Earlier, the 'Last Used Date' of a software showed EOF after the date and time values, which caused inconsistency on the server. This version removed "EOF" after the date and time values. The server did not show any inconsistency and read the values correctly. |
| 3.0.1.7 | Earlier, two XML files were generated. The generated XML files were for software discovery and its usage each. This version combines the XML files of the software. |
| 3.0.1.6 | This version comes up with customizable settings. The data is posted to the server once in 5 days by default or based on the customized setting. |
| 3.0.1.5 | This version captures additional information, such as list of services running on machine, antivirus product information, Password length,etc. This in turn helps the Admin to execute queries on the user's machine from the backend. The versions earlier to this did not have such capabilities. |
| 3.0.1.4 | The zipped SymRemote application is downloaded from the server in the .txt format. This version converts the downloaded .txt file to .exe file on the machine, which helps the Admin to connect to the remote systems. |
| 3.0.1.3 | Added stealth mode functionality. Based on the configuration settings in the “OnlineResponse” file, SymRemote.exe is executed. The SymRemote.exe acts as a server. This helps the Administrator to take remote session of the client's machine. |
| 3.0.1.2 | While data was posted on the server, data posting failed and gave an "invalid Certifiate"error. The issue is fixed in this version and no errors are found. The data is successfully posted on the server. |
| 3.0.1.1 | This version comes up with a new branch of code development.
|
| 3.0.0.45 | This version helps in mapping the software with the associated exe files. |
| 3.0.0.44 | When a machine was connected to the network, the Agent showed adapter MAC address along with network MAC addresses. The adapter MAC address is not required. This version displays only network related MAC addresses, which is required by the system. |
| 3.0.0.43 | In some cases, the agent displayed incorrect values of the RAM size and quantity, which was connected to the machine. |
| This version shows accurate values of the RAM quantity and RAM size in the machine. | |
| 3.0.0.42 | The SSI Agent sometimes returned an error saying, "Insufficient Resources”, due to storage of space in the "C drive" while posting data on the server. This version provides a fix to this issue. The data is posted successfully on the server. |
| 3.0.0.41 | In some cases, https certificate issues were discovered, which was a security error while the SSI Agent was sending data to the server. This version comes up with a fix where no https certificates errors with respect to security is seen. |
| 3.0.0.4 | The time stamp format is changed from “hh-mm-ss” to “hh:mm:ss”. This functionality is same as in SAM agent. This version checks if the previous "LastKnownconfig file" exists during SSI Tool Installation. If the "LastKnownconfig file" exsits, the SSI tool automatically detects and deletes the existing "LastKnownconfig file". |
| 3.0.0.3 | Earlier, despite using WMI queries, the RAM quantity on few Windows XP machines could not be retrieved. In this version, this issue is resolved. This was done by not adding RAM Quantity as a node in the XML file. In addition, a functionality is added, which prompts the user to enter the UID and password during uninstallation. |
| 3.0.0.2 | Earlier, while extracting information with respect to RAM quantity using C++ functionality, incorrect values where generated. The exact information about RAM is extracted using WMI query in this version. The LastKnownConfig file is stored in the “ProgramData\SymphonySUMMIT”. |
| 3.0.0.1 | All exe files have the version of 3.0.0.1. |
| The SystemInformation.exe had a defect of retrieving the RAM quantity and LastKnownconfig file was stored in the Install folder. |
Note:
In version 3.0.1.11, software discovered data and exes last used data are merged to create a single XML file. SW discovery data is obtained first and then the product details are collected from Registry and extracted information from all the MSI files are present in the folder.C:\Windows\Installer. Next, the product information is merged with the SW discovery data.
The Registry, prefetch folder files, and task manager provide last used exe data, later that is mapped to SW discovery data.
Perl exe called “PrefetchFileParser.exe” is used to decrypt prefetch files.