Skip to main content

New server

Use this form to set up a new server that has Asset Management Collector installed.

Features:

  • General

    • Hostname - enter the network name of the server.
    • Description - enter a description of the server if applicable.

  • Scan

    • Scan processing

      • Scan and evaluate (evaluation scheduling will not take effect) - Select if Collector should evaluate the scanned data immediately after performing the scan. Collector writes the changes to the object tree and to Installation registry.

      • Scan and schedule evaluation - Select if Collector should perform scans but not evaluate the scanned data.Collector will only schedule the evaluation of the data.

        note

        If you want to use scheduling, we recommend using this setting.

        tip

        When deploying multiple instances of Collector on a network, you can use this option to have some instances only scan computers and, for example, one instance can evaluate the scans. This will speed up data collection (and delay data evaluation).

    • Use the PING command to determine if a computer is switched on

      • before scan with the "Agent over TCP/IP" method - select to enable the PING function to verify the presence of the computer on the network for scan by Agent over TCP/IP.
      • before scan with the "without Agent" method - select to activate verification of the computer's presence on the network using the PING function for no Agent scan.
      note

      These options are enabled by default. We recommend turning them off only if PING is not working on the network (in which case Collector would determine all computers as disabled).

    • Scan the computer again in

      • __ minutes while the computer is switched off - specify in minutes the earliest time Collector should retry to scan the computer off.
      • __ minutes in case of scan error - specify in minutes the earliest time Collector should retry to scan the computer after the last scan attempt failed.

    • Process in a single block- Collector processes tickets in blocks. It processes at most the specified number of tickets within each block and places a wait (wait state) at the end of the block.

      • __ computer scans - Specify the maximum number of scans to be performed by Collector within a block.

      • __ scan evaluation operations - enter the maximum number of scheduled evaluation operations that Collector should perform within a block.

        note
        • Collector, which performs evaluation operations, also handles the allocation and removal of software licenses that have the Automatically allocate option enabled.
        • Evaluation Operations creates Collectors with the Scan and Schedule Evaluation option enabled.
        • Evaluation Operations is also created to re-evaluate software scans when a new version of Software Product Library is loaded.

    • Waiting status between the processing of blocks - enter the length of the wait time between blocks in minutes.

    • Only perform scans for computers matching the filter - specify a filter defining the computers to be scanned by this Collector instance.

      E.g., if you want the Collector instance to scan only computers that are located somewhere in the "New York Office" object, use the filter:

      EXISTS (
      SELECT *
      FROM tblNodeParent NP 
      INNER JOIN tblNode N ON NP.lintParentNodeId=N.intNodeId
      WHERE NP.lintNodeId=D.lintComputerNodeId
       AND N.txtName=N'New York Office'
      )
      note

      This is a condition in the SQL query to the database that selects the tickets to perform the scan. The alias D appears in the sample, which represents the tblDetect table.

    • Only perform evaluation operations for computers matching the filter - Specify a filter that defines the computers for which this Collector instance should perform evaluation operations. The filter has the same format as the filter for performing scans.

      note

      Computers that are placed in a tree structure under an object of type Stock are not scanned in any case.

  • Scheduling - setup scheduling of computer scans.

    • Schedule for scans (network load)- Enable if scans are to occur only at a specific time interval.

      • Scan computers daily only in the following interval - specify from when to when scans should take place.

        note

        The intervals are stored in UTC and do not respect the transition between daylight saving time and standard time. For example, if you enter an interval in summer, it will be offset by an hour in winter and will be displayed as such in the settings.

        note

        This setting does not apply to the Autonomous Agent scan method.

      • Exceptions (the schedule does not apply to the following days)

        • Monday, ..., Sunday - Select days on which scans will be performed throughout the day (will not be subject to the scan schedule).
        tip

        By scheduling scans, it is possible to limit the load on the network, e.g. during operating hours when the full capacity of the network needs to be used.

    • Schedule for evaluations and automatic scan loading (SQL Server load) - Enable if the evaluation of scans is to be performed only at a specific time interval.

      • Evaluate scans daily only in the following interval - specify from when to when the evaluation should take place.

        note

        See note for the scan schedule above.

      • Exceptions (the schedule does not apply to the following days) - Select the days on which the evaluation will run all day (will not be subject to the evaluation schedule).

        tip

        By scheduling the evaluation of scans, it is possible to limit the load on the SQL server, for example, during operating hours when employees access the database on this SQL server. Especially the evaluation of software scan is a demanding operation that can put a lot of load on the SQL server.

        warning

        This setting also affects the automatic scan loading feature.

  • Loading files - Settings for manual computer scans.

    • Automatic loading of scan files (*.CXM)- Enable if you want the server to load manual scan files from a specific folder.

      • Load CXM files automatically from - specify the path to the folder that Collector will monitor and load new scans into the database from.

        warning

        The specified path is a folder on the configured machine, but the ... button browses folders on the local machine. Set the path to match the structure of the disks and folders as seen from the configured server.

      • If the loading process succeeded

        • Move the CXM file to the "Processed" subfolder - select if the CXM file should be moved to the "Processed" folder after the scan is loaded.
        • Delete CXM file - select if the CXM file should be deleted after the scan is loaded.

      • If loading failed

        • Move the CXM file to the "Failed" subfolder - select if the CXM file that failed to load should be moved to the "Failed" folder.
        • Delete CXM file - select if the CXM file that failed to load should be deleted.
        note

        For automatically loaded scans, objects of type Set (computer) in the "Computers from loaded scans" folder at the root of the object tree. For a computer that already exists in the tree, the existing scan is only updated.

  • SW product library - setup updates to Software Product Libraries.

    • Auto update
      • Download from the Internet- turn on if Collector should automatically download the latest software product library from the web.
        • Check for updates every (days) - specify in days how often to check if a new library of sw products is available on the manufacturer's website.
      • Load from file - this library update option is recommended to use if Collector does not have access to the Internet. Then, periodically once a week, download the https://www.alvao.com/downloads/swlib2.swl file from the web and save it to a folder on the server disk. Specify the path to the folder to match the disk and folder structure from the view of the configured server.
      • Do not update - Collector will not automatically update the library.
      • Automatically reevaluate existing scans after library update - Enable if you want to automatically evaluate existing software scans against the new library of software products.
    • Automatically send all unrecognized software for recognition - turn on if you want Collector to send requests to add a new product and unrecognized software to the ALVAO team for processing.
    • Disclaimer for sending information on unrecognized and new software
      • If you need any additional information, you can contact me at email - select if technical support staff can contact you if needed and fill in the email contact person.
      • I don't want to be contacted. I always want to send my data anonymously - select if you want to send data anonymously. Our specialists will not be able to contact you, so if some unrecognized products cannot be identified by the records you have sent, the product will not be included in the standard library.