When PCs or laptops are rarely or never connected to the network, standard methods will not allow carrying out a fully automated audit.
In these cases, the Synexsys Agent will have to be run locally.
![]() | Above all, check the settings contained in the ..\config\config.ini file of the .. \client folder from which you'll execute the agent. More particularly: |
| |
SERVER=IP Address or HOSTNAME of the Synexsys Server (HOSTNAME is recommended during evaluation tests if the Synexsys server is installed on a DHCP machine) IMPORTANT: leave this parameter empty if the PC is never connected to the network or if you want to transfer the inventory files manually. | |
| |
PORT=IP Port of the Synexsys Server (5026 by default, but it can be modified). Make sure the port is accessible and there is no firewall forbidding the access. | |
TEMP=Local temporary folder: either an existing environment variable such as %temp or a local path such as "C:\SXSi\TEMP". (the path will be created automatically on the audited PC) IMPORTANT: If you need to transfer the inventory data manually, you should create a specific temporary folder to gather the generated audit files. This will generally prevent you from forgetting any file in the transfer process. | |
| |
SID=Folder where the workstation's unique identifier (SID) will be stored. It can be either an existing environment variable such as %windir or a local path such as "C:\SXSi". (the path will be created automatically on the audited PC) |
![]() | Limited connection to the network: share the Synexsys Inventory ..\client folder and launch SXSILA.EXE (agent in interactive mode) or sxsiagent.exe from the command line from the PC that is to be audited (See Login Script Deployment for more information). |
![]() | From a portable storage device : copy the Synexsys Inventory ..\client folder and its sub-folders to a portable storage device and launch SXSILA.EXE (agent in interactive mode) or sxsiagent.exe from the command line from the PC that is to be audited (See Login Script Deployment for more information). |
![]() | E-mail: Send the Synexsys Inventory ..\client folder and its sub-folders by e-mail and copy the whole tree to the local PC. Launch SXSILA.EXE (agent in interactive mode) or sxsiagent.exe from the command line (See Login Script Deployment for more information). |
During the audit, some data files are created and placed in the folder associated to the TEMP key of file..\client\config\config.ini. This data will later be processed, and the files will be compressed, renamed, and transfered to the folder corresponding to the SID key of the config.ini file. The created files (with txt, sck, inv, and keo extensions) make up the local machine's inventory. Some of this data needs to be transferred to the Synexsys Server so it can be imported into the database.
If the audited PC is connected during the inventory, the data will be transferred automatically to the Server (if available through FTP). If the machine is not connected to the network, you will need to transfer the inventory file (.inv) to the ..\Synexsys\server\inbox folder of the SXSi server. There is no need to transfer the SID.TXT file nor the KEO or filter.ini files.
![]() | File to transfer to the ..\Synexsys\server\inbox folder of the Synexsys server: *.inv |
| |
![]() | Files to keep in the local machine: SID.txt These files are required to identify the machine (SID.txt) and for future incremental audits (keo). File SXSI.SCK determines the last contact date with the PC (SXSI.SCK), while filter.ini contains a copy of the audit rules defined in the Synexsys Console. |
Deployment Via the Console (NT/2000/XP/2003)
Deployment Via Login Script (95/98/Me/NT/2000/XP/2003)