Menu

Resources

 2017 FICHE SCANFREE PRO UK      
                                                                                       
             Scanfree Professional Edition
                          Snmp for Scanfree Pro
           Active Directory for Scanfree Pro
                        IDA for Scanfree Pro

 

 

         
                                                                                  
        Discovering Scanfree Professional Edition
            How to start inventory with Scanfree
                Discovering Snmp for Scanfree Pro
       Discovering Active Directory for Scanfree Pro
                 Discovering IDA for Scanfree Pro

 

 

                                          
Start inventory with Scanfree
Manage software with Scanfree Pro
The benefits of Scanfree Pro

 

 

logo_landpark_ombre You can install Scanfree Pro in two ways:

 

1- By using Landpark Network IP.


After installing Scnafree Pro, you can launch 3 Network IP modules. These modules must be launched in the following order: 

 

Landpark Network IP Server (launched automatically after installation and startup). 


Landpark Network IP Client (launched automatically after startup).


Landpark Network IP Console (launched manually). To set up IP Console, enter the server's IP address, enter a TCP port, specify a folder where the inventory files are to be copied, and click “Connect”. You should now see a list of connected clients, including:

 

- A row that represents the console itself.


- A row for each client computer on which you will be able to launch inventory operations.


You can alternatively use DoInventory: this executable allows you to launch inventory operations on  client computers via a connection script, without having to install the client/server modules.

 

To install the services, you must open a command prompt and type the following command:

 

C:\Program Files\Cerus\Landpark\IP Clients\ParamClient.exe 

 

This application generates a “paramclient.ini” file which must be copied to the folders where the 2 services are to be installed. To install the services you must run the executable file from a command prompt with the /install option:

 

Example C:\Program Files\Cerus\Landpark\IP Server\LpIpServiceServer.exe /install

 

To uninstall the service, you must run the same command with the /uninstall option:


Example C:\Program Files\Cerus\Landpark\IP Server\LpIpServiceServer.exe /uninstall

 

 

 

Notes :  

 

The client icon appears only if it managed to connect to the server.


If the icon does not show, the address of the server to which it tried to connect is probably incorrect. In this case, you can: 


- Stop the client process by pressing CTRL-ALT-DEL, or by looking up the LpIpClient process in order to shut it down.  


- Open C:\program files \ cerus \ landpark_eval \ IP customer \ paramclient.ini 


- Type '127.0.0.1' or any valid IP address on the first line, do not modify the second line 


- Save your changes and restart the client from the Menu


The IP address allows the client and the console to connect to a server process running on the same computer. If you want to launch a client or the console on another workstation, you must specify the server's IP address.


The client icon will not show if you choose to hide it by using the menu Client, Client Options, Secure Clients, hide Network IP Console icon.

 

You can install as many clients as you wish: you may in fact deploy them on any number of workstations using a connection script.

 

Run first Landpark IP Install (quickly install Landpark agents throughout the network).

 

 

 

 

2- By using Landpark DoInventory (different from IP deployment) 


Instead of installing remote agents on client workstations using connection scripts, Landpark DoInventory allows you to run similar inventory operations without having to install the client/server modules. 

 

DoInventory works in two different modes: 

 

By sending the files that are necessary for inventories to client workstations, provided these files are not already present on client workstations, or if they were modified on the server. High bandwidth usage can thus be avoided by transferring a minimum amount of data. This option makes it possible to benefit from more scheduling options (however, a local file on the client workstation is required to memorize the latest inventory date).


By carrying out the inventory directly using the files that are already present on the server without copying them to the client workstation. The executable files required by the inventory are transferred over the network for every inventory operation. Note however that users won't be able to enter customized information (cf documentation on inventory settings). As a consequence, result files will display every computer's network name.

 

 

DoInventory is an executable that allows you to launch remote inventories on client workstations via a connection script, without having to install the client and server modules.

 

The inventory operation can for instance be launched upon login or scheduled to run every n days.

 

The inventory engine is automatically selected according to the client operating system.

 

A log file is also created on the server in order to list the inventories that have been effectively carried out and the errors that may have occurred.