Scripting provides users with a powerful tool for the centralized configuration of LANCOM devices, and thus a wide range of potential applications:
- Read-out device configurations in a form that is easy to read and save The configuration files generated by LANconfig are not intended for processing with other tools; users will only get an overview of the complete configuration from a print-out of the configuration file. The scripting functions can output the configuration as ASCII text to be saved as a text file.
- Edit the configuration with a simple text editor If offline configuration with LANconfig is not possible or not desired, a configuration file generated by scripting can be edited with a text editor and then uploaded to the device again.
- Edit sections of the configuration Instead of the entire configuration, smaller sections of it can be read out from a device instead (e.g. just the firewall settings). Just as with complete configurations, sections can be edited and transferred to one or more devices. This allows the particular settings in a device to be uploaded to other models or devices with a different version of the firmware.
- Automized configuration updates The centralized storage of configuration scripts in combination with scheduled LCOS commands (cron jobs) can be used to keep vital sections of the configuration in multiple devices up to date, e.g. the encryption settings for a WLAN.
- Convenient roll-out for larger installations The installation of multiple devices at different locations can be very easily controlled from a central location. Even employees without administrator rights can then set up the devices with a single command.
- Storage of configuration to volatile memory only Scripting commands can store configuration changes in RAM only, whereby storage of configuration information to the non-volatile flash memory is prevented. This ensures that the configuration is available only until the next system boot, so that in case of theft, for example, sensitive elements of the configuration cannot fall into the wrong hands.
- Configuration changes in test mode The same mechanism allows changes to the configuration in test mode. A script triggers a time-delayed system boot; the intervening time period can be used to change and test the device's configuration without risk. Should the changes lead to a failure, the device automatically reboots after the time delay and is reset to its original configuration. Comparable to the FirmSafe function, this variation is a type of "ConfSafe". Changes to the configuration after a firmware update can, on occasion, be impossible to edit in the case of a later downgrade to an older firmware version. If, however, the configuration subsequent to the firmware upgrade is stored in test mode only, then downgrading and subsequently re-booting the system will result in the restoration of the original firmware and its configuration.