Server configuration file offers easy management of network protection settings for your client.

Instead of embedding all network protection options into protected application server configuration file can be easily created and distributed to end user.

By default, NETWORK protection settings including server unc path are embedded into application during protection process. Server unc path should be obtained from end user before protecting application in this case.

In case server configuration file feature is enabled, server unc path is still required before protecting application but you will also be able to change network protection setting including server unc path by creating and sending appropriate server configuration file to your client at any time in future.

Finally, if server configuration file feature is enabled together with "Server configuration file is required" option, both server unc path and maximum number of workstations allowed to access application options are not required prior protection. Protected application will refuse to work on remote network without valid network configuration file. In this way, you would protect your application only once and distribute appropriate server configuration file after obtaining required information from your end users. This is probably the most flexible implementation scenario.

Server configuration file structure

Server configuration file is an encrypted binary file which can hold the following information:

- All general NETWORK protection settings

- User information

- Custom counters

- IP filtering settings

Step by step example

Step 1: Protect application with NETWORK protection method with server configuration file feature enabled.

Step 2: Distribute protected application to your client.

Step 3: Get server unc path from your client.

Step 4: Load project settings used in step 1

Step 5: Open network protection settings and set server unc path and other network protection settings as required.

Step 6: Select "Server configuration file" tab and set additional options as required.

Step 7. Create configuration file by clicking on "Create configuration file" button.

Step 8: If 'Create report' option was selected appropriate report file will be created. Click on 'View report' button to view report.

Report file has the same name as configuration file with additional .LOG extension (SERVER.DAT.LOG is default report file).

Step 9: Distribute configuration file to your client. Configuration file should be located in same directory with protected application.

Notes

- Default server configuration file is named 'SERVER.DAT'

- Protected application will be able to load and handle server configuration file only if server configuration file is created with correct project settings.

- Configuration file should be located in same directory with protected application. 

- Only application protected with "Use server configuration file" option will look for server configuration file.

- Server configuration filename should be the same as the one set during protection process.

- Information stored in server configuration file can and will be changed in future. This is why each configuration file has appropriate version. You can see server configuration file version in bottom right corner of network protection settings dialog. Version number is also stored in application during protection. Application can load and use only configuration file with appropriate version number.

- Save report file for later use.

IMPORTANT: Be sure not to distribute report file to end user together with configuration file for security reasons.