How to Check Logon Script for Starting Clients

1. You have created two shared folders. One folder hosts the client executable files, the second one will collect the data files. These folders MUST be different from the folder where the program database is located, and from each other.


2. Make sure the client is working properly. Go to a remote test computer. Open the shared folder where the client is located. Run the nieclient.exe file.


3. A data file should appear in the folder for collecting the data files.
   If this does not happen, there may be problems with accessing the data collection folder. Copy the log of the client's operation from the test computer from the folder "C:\Users\login of the current user\AppData\Roaming\10-strike\Inventory Client\cfg\log.txt" and send it to our technical support team.
   Also, this folder should contain the <*.fld> file with the collected data (the file size must be larger than 3 KB).
   The log file contains errors about the information collection process and the process of copying the data file to the destination share.
   The main mistakes are misspellings when specifying the name of a shared folder, and lack of access rights to it.

ATTENTION! By default, the process of collecting information starts in hidden mode. Therefore, we recommend that you track its work only by checking the log file as you cannot see the client's GUI console.

4. Check the logon script operation.
   Reboot the test computer and log on to the domain. The logon script should run. The file with the data collected by the client should be copied to the shared folder.
   If this does not happen, you need to check the correctness of the logon script configuration.


5. Check the data importing.
   The data import occurs in the idle mode so as not to interfere with the administrator's work. The main program may not be running. In this case, the import will be performed by the datacollector.exe process (the network inventory information collector program).
   The import settings must contain the path specified for the folder in which the client copied the collected data files. Place an *.fld file in it, go to the "Data" tab in the program and click "Import new data". The data must get into the database and be available for viewing and reporting for that PC. After successful importing, the program deletes the data file from the importing directory (after processing the data and moving it to the inventory database). So the data file should disappear from the data collecting folder.

Check all the above steps. If any problems arise, you can write to our technical support team and ask for help.

Manual and scheduled data collection

1. Select the "Main" tab and click "Collect data" to start the data collection on the main window of the program.
   Select data groups and computers for which you want to get the information. Click "Finish". The collection status information window will be opened.
   You can also set up the PC polling schedule on the tab "Service and Settings" using the "Scheduler" button (enable the checkbox "Scheduled Data Collection").
   ATTENTION! Do not indicate a short period of time for the schedule, as well as a short interval for collecting the information. Short intervals can create a big load on the network and remote computers' CPUs.
   Apply settings.


2. When you manually start the information collection, the status window appears automatically. When using the schedule, it will not appear. You can open it using the button "Data" - "Collection State".


3. ATTENTION! The collected DATA does not appear in the inventory database immediately. This is done so that the administrator can work and collect information at the same time, as well as analyze configuration changes. The import of the data into the database occurs in the background when the computer is idle or if the main program is not running, so as not to interfere with the administrator's work.


4. To force the data importing at the moment, go to the "Data" tab in the program, and click "Import New Data". The information should get into the database and be available for viewing and reporting after that.


5. If the information from computers has not been collected, it is necessary to configure the Firewall using Group Policy. If you do not have a domain, then we recommend using the client application and the shared folder collection scheme. Despite having administrator rights in the workgroup, there are some default Windows security settings that prevent the remote processes from starting and using WMI properly. So you need to configure every remote PC for WMI to work or use clients for collecting the inventory data in workgroups.