Strategy #2: Allow Configurations to be Stored Locally on the Thin
Client
The second approach for achieving persistence is to allocate a specific area of
the local DOM for reading and writing system settings and connections. DeTOS
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 Control Panel.
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 the 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.
Case Examples
The Local Storage section of the Control Panel allows you to use three
methods for local storage:
No Local Storage
Enable Local Storage
Enable Snapshot Storage
These case examples are provided below to help you decide which of these three
options will work best for you.
20 | Persistence
Need help?
Do you have a question about the OptiPlex VDI Blaster Edition and is the answer not in the manual?