Best Practices For Companies

General

PureDesktop is optimized for commercial use. Rolling out the software, setting the project, enabling the premium features, … All this can be automated.
We will explain here how it works and what benefits you have.

1. Automatic installation
So that the IT admin does not have to make the installation manually on every PC, the installer has a silent installation. This means that the installer automatically performs the installation without anyone having to intervene.

The automatic installation works by starting the installer with the following parameters /VERYSILENT and /NORESTART. This will install the software without having to restart the PC afterwards.

2. Set configurations
Configurations are stored in 3 files (SettingsForced.dat, Settings.dat, SettingsDefault.dat).

SettingsForced.dat
The settings specified here are always enforced. This means that all changes are ignored by the user. This file must be in the program directory.

Settings.dat
This file is generated for each user and contains all user-defined settings. This file can not be edited with a text editor because this information is formatted and serialized (which is written for a word :slight_smile: ).

SettingsDefault.dat
The settings you specify here can be set to specify basic settings. If a user has not adjusted something himself, this value will be taken here. This file must be in the program directory.

3. Automatic login
These settings should be made in the SettingsForced.dat file. The following settings should be made in the file:

Username: [Your Username]
Password: [Your Password]

4. Automatic slot activation
These settings should be made in the SettingsForced.dat file. The following settings should be made in the file:

AutoActivatePremium: true

5. Disable Designer
These settings should be made in the SettingsForced.dat file. The following settings should be made in the file:

DisableDesigner: true

6. Set project rules
These settings should be made in the SettingsForced.dat file. The following settings should be made in the file:

Project Rules: [ID: [Project ID]; Default: [true, false]] [ID: [Project-ID]; Count: [Screen-count]; Width: [Screen Width]; Height: [Screen Height]] …

ID: The ID is the project folder name.
Default: If true, then this project will be used if no other rule applies
Count: The exact number of screens
Width: The exact width of the virtual screen
Height: The exact height of the virtual screen

7. (Optional) set paths
These settings should be made in the SettingsForced.dat file. The following settings should be made in the file:

ProjectPath: [path]
ExtensionPath: [path]