OptiPlex FX130: Persistence Configurations

OptiPlex FX130: Persistence Configurations

Article Summary: Article describes an overview of persistence configuration settings.

Table of Contents:
  1. Persistence Configurations



Persistence, within the scope of thin client computing, refers to the continuing existence of connections and settings after the terminal has been rebooted.

By default, or after resetting the terminal to default factory settings, DeTOS is set to persistent mode. This means that any configuration change you make will persist across reboots. This can be changed to a stateless mode where the thin client settings and connections are dynamically "pulled" from the management server, or a snapshot mode where the network administrator defines the desired configuration and prevents users from making any changes. These options are all configured in the DeTOS Control Panel, under System Settings, in a section called Local Storage.

The Local Storage section of the DeTOS control panel allows you to use three methods for local storage:
  • No Local Storage
  • Enable Local Storage
  • Enable Snapshot Storage

  • There are two strategies for achieving persistence in DeTOS-based thin clients:

    Maintain Profiles via Remote Management Server
    DeTOS thin clients can be centrally managed using the Echo Thin Client Management software. Using Echo, administrators can create several connections and settings and then group them together to form one single collection called a profile. This profile can then be pushed or assigned to one or more thin clients using a web browser. With a profile properly configured, each time a terminal is booted up and discovered by Echo, all connections and system settings according to its assigned profile are immediately applied - or "pushed" out - to that terminal.

    Allow Configurations to be Stored Locally on the Terminal
    The second approach for achieving persistence is to allocate a specific area of the local DOM for reading and writing of system settings and connections. DeTOS not only provides for this type of feature, but actually allows for even greater flexibility by offering two variations of this strategy.

    Enable Local Storage - While running in this mode, DeTOS will write to the local DOM each and every time configurations are added, deleted or modified under the DeTOS Control Panel.

    NOTE: By default, this is the selected mode for brand new or recently reflashed DeTOS thin clients.

    Enable Snapshot Storage - When this mode is selected, DeTOS allows writes to the local DOM, but in a more finely controlled manner. An administrator can configure the settings and then store the current configurations to the DOM by clicking Take Snapshot. The only settings and connections that will persist across reboots are the ones captured during the snapshot. The terminal essentially falls back into a non-persistent operating mode after the snapshot and discards any new configurations from here on out - until th administrator clicks Take Snapshot again, and a new snapshot is used as the primary configuration. In some ways, this mode can be thought of as a hybrid of the standard Enable Local Storage and No Local Storage modes.

    Click the button below to Tweet feedback or request assistance on anything in the above article. Twitter

    Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate caution. Dell shall not be liable for any loss, including but not limited to loss of data, loss of profit or loss of revenue, which customers may incur by following any procedure or advice set out in the Quick Tips.

    Article ID: SLN284512

    Last Date Modified: 01/07/2014 12:00 AM

    Rate this article

    Easy to understand
    Was this article helpful?
    Yes No
    Send us feedback
    Comments cannot contain these special characters: <>()\
    Sorry, our feedback system is currently down. Please try again later.

    Thank you for your feedback.