Synexsys allows merging both automatically and manually, PC data coming from several sources.
There are three possible cases requiring PCs data merge:
![]() | Loss of the local SID (automatic merge by the Synexsys Server) The Synexsys identification file (SID.TXT) has disappeared from a PC following a crash or disk cloning, for instance. In this case, during the next audit load, the Synexsys Server will see this PC as a potentially new machine. This is how the Synexsys Server finds the PC in the database: It first determines if the PC's SID exists. In this case, the system cannot find the file. Then, it searches for a Preliminary Key. If it exists and it is found, the Server merges the collected data with the original information. If not, it continues searching for a Merging Key. If it exists and it is found, the Server merges the collected data with the original information. If not, it creates a new PC in the database. In this case, only one solution is left: manual merging (see below). |
| |
![]() | Import via SXSimport - You have imported information on a PC with SXSimport. If a is found with the Merging Key (mandatory in an import), the merge is done automatically. If not, you will need to merge the PC manually (see below). |
| |
![]() | Manual correspondencePC creation - You have created a PC manually in order to enter administrative information. If you use a Preliminary Key such as the PC's serial number or Hostname and/or a Fusion Key, the Synexsys Server will merge the data collected from the audit with the administrative information based on the process described above (loss of SID). If you have not defined these Keys, you must merge the PCs manually (see below). |
| |
![]() | Manual merge of two PCs: select one of the two PCs you wish to merge from the Objects list and choose the option "Merge...", "Mark for merging" from the context menu (right-click). Then select the second PC and select option "Merge...", "Merge with pc_name" from the context menu. Validate the action. |
| |
![]() | IMPORTANT: The technical data collected from the original audit is replaced by the most recent audit data. The original data contained in Custom Fields is kept in case the new PC's custom fields are empty. Given their nature, the original data contained in REG/INI type fields are systematically replaced by new or empty values if no value is available (if the keys are missing, for instance). |