Dell OptiPlex VDI Blaster Edition Devon IT Terminal Operating System (DeTOS) D - Page 21

Case 1, Solution, Local Storage, Case 2, Enable Local Storage, Case 3, Enable Snapshot Storage,

Get Dell OptiPlex VDI Blaster Edition PDF manuals and user guides View all Dell OptiPlex VDI Blaster Edition manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

Case 1: "I do not want any users to mess up the thin client's configuration. I am currently using, or plan to use, Devon IT Echo Management Console Dell Edition to centrally manage my thin client." Solution: You will be utilizing strategy #1, as described earlier. Choose the No Local Storage option on the thin client and make sure you have an Echo server properly configured and accessible on your LAN. With persistence disabled, the thin client becomes stateless and relies completely on the management server for all its configurations. Case 2: "I simply want the thin client to maintain its configuration settings locally. I do not want to rely on a management server." Solution: Choose the Enable Local Storage radio button option. While running in this mode, DeTOS will write to the local DOM each and every time configurations are added, deleted, or modified. A remote management server is not needed. Case 3: "I like the idea of having a non-persistent terminal with an assigned profile, but do not want to use Devon IT Echo Management Console Dell Edition to manage my terminals. What's the alternative?" Solution: Choose the Enable Snapshot Storage radio button option, press Apply, and then reboot the terminal. Next, configure the terminal as desired, and then press the Take Snapshot button. From then on, the thin client will use the same exact configuration as when the snapshot was taken - even after being rebooted. A remote management server is not needed. NOTE: If you would like to change your configuration later, you will have to press the Take Snapshot button again to save all of the changes made to your terminal. Upon reboot, your terminal will load whichever Snapshot was is currently being used. Pressing the Clear Local Storage button will ask the terminal to clear all connections and settings saved locally, clear the current snapshot used for the reboot, and restore itself to factory settings on the next reboot. Persistence | 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
Persistence | 21
Case 1:
“I do not want any users to mess up the
thin client
’s
configuration.
I
am currently using, or plan to use, Devon IT Echo Management Console Dell
Edition to centrally manage my thin client
.”
Solution:
You will be utilizing strategy #1, as described earlier. Choose the
No
Local Storage
option on the thin client and make sure you have an Echo server
properly configured and accessible on your LAN. With persistence disabled, the
thin client becomes stateless and relies completely on the management server for
all its configurations.
Case 2:
“I simply want the
thin client to maintain its configuration settings
locally.
I do not want to rely on a management server.”
Solution:
Choose the
Enable Local Storage
radio button option. While
running in this mode, DeTOS will write to the local DOM each and every time
configurations are added, deleted, or modified. A remote management server is
not needed.
Case 3:
“I like the idea of having a non
-persistent terminal with an assigned
profile, but do not want to use Devon IT Echo Management Console Dell
Edition to manage my t
erminals.
What's the alternative?”
Solution:
Choose the
Enable Snapshot Storage
radio button option, press
Apply
, and then reboot the terminal.
Next, configure the terminal as desired,
and then press the
Take Snapshot
button.
From then on, the thin client will use
the same exact configuration as when the snapshot was taken
–
even after being
rebooted. A remote management server is not needed.
NOTE:
If you would like to change your configuration later, you will have to press the
Take Snapshot
button again to save all of the changes made to your terminal.
Upon
reboot, your terminal will load whichever Snapshot was is currently being used.
Pressing the
Clear Local Storage
button will ask the terminal to clear all connections
and settings saved locally, clear the current snapshot used for the reboot, and restore
itself to factory settings on the next reboot.