Virtual Architects Support Wiki

User Tools

Site Tools

You are here: start » virtualization » otc
Trace: • pihole
virtualization:otc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
virtualization:otc [2012/04/30 12:56]
gcooper 		virtualization:otc [2017/01/25 11:53] (current)
gcooper
Line 11: Line 11:
 Run with /usr/bin/javaws. Run with /usr/bin/javaws.
  
-On first use, connect to the realm 'openthinclient' using password 'secret'.+:!: On first use, connect to the realm ''openthinclient'' using password ''secret''.
  
 ===== Supported Hardware ===== ===== Supported Hardware =====
Line 19: Line 19:
 ==== Monitors/Displays ==== ==== Monitors/Displays ====
  
-See [[computing:monitors|Monitors]].+See also **[[virtualization:otc_display|Monitors / Displays]]**
  
 ===== Virtual Machine ===== ===== Virtual Machine =====
Line 27: Line 27:
   * Supports ATOM-based thin client hardware   * Supports ATOM-based thin client hardware
   * Configure VMware for VNC console access   * Configure VMware for VNC console access
-    * <file>vncviewer linus:5901</file> +    * <file>vncviewer hostname:5901</file> 
-  * you can access the OTC Manager via a web browser+  * You can access the OTC Manager via a web browser
     * http://ip.of.vm:8080     * http://ip.of.vm:8080
     * Package management doesn't work in remote Manager     * Package management doesn't work in remote Manager
Line 41: Line 41:
 ==== Verify Open Ports ==== ==== Verify Open Ports ====
  
-^Protocol^Ports^ +^Protocol ^Ports                                                                                          ^ 
-|TCP|1098, 1099, 2069, 3873, 4444, 4445, 8009, 8080 (internal webserver), 8083, 10389 (LDAP server)| +|TCP      |1098, 1099, 2069, 3873, 4444, 4445, 8009, 8080 (internal webserver), 8083, 10389 (LDAP server) | 
-|UDP|67 (DHCP proxy), 69 (TFTP server), 514 (SYSLOG server), 2069, 4011 (DHCP proxy)|+|UDP      |67 (DHCP proxy), 69 (TFTP server), 514 (SYSLOG server), 2069, 4011 (DHCP proxy)                |
  
 Check for conflicts: Check for conflicts:
Line 100: Line 100:
  
 <file> <file>
-ssh -X -l root linus+ssh -X -l root hostname
  
 java -jar openthinclient-1.0.0.jar java -jar openthinclient-1.0.0.jar
Line 109: Line 109:
 From a workstation with Java 6: From a workstation with Java 6:
  
-http://linus:8080/ (Start Manager)+http://hostname:8080/ (Start Manager)
  
 ==== Connect to Existing Realm ==== ==== Connect to Existing Realm ====
  
-LDAP password = 0pen%TC     (was 'secret')+|LDAP password |''0pen%TC'' |was 'secret'  |
  
-Select 'openthinclient' realm and click finish+Select the ''openthinclient'' realm and click ''finish''.
  
 ==== Install Packages ==== ==== Install Packages ====
Line 154: Line 154:
 http://openthinclient.org/tiki-index.php?page_ref_id=84 http://openthinclient.org/tiki-index.php?page_ref_id=84
  
-All configuration information is located in the apacheds-store under server\default\data.+All configuration information is located in the ''apacheds-store'' under ''server\default\data''.
  
-===== Notes =====+==Linux==
  
-==== OTC High Availability ====+To save the configuration on the filesystem level create a backup of the following directory:
  
-=== Failover Server Howto ===+<file> 
 +/opt/openthinclient/server/default/data/apacheds-store 
 +</file>
  
-== Setup ==+==Windows==
  
-  - install both servers, +To save the configuration on the filesystem level create a backup of the following directory:
-  - activate the OTC service on the primary, deactivate on the secondary, +
-  - regularly sync apacheds-store from primary to secondary, (... normal operation...)+
  
-== In Case of Disaster ==+<file> 
 +C:\Programme(x86)\openthinclient\server\default\data\apacheds-store 
 +</file>
  
-  - activate OTC service on backup server, +===== High Availability ===== 
-  - run OTC updates (if needed) + 
-  - boot clients...+==== Warm Spare ==== 
 + 
 +=== Setup === 
 + 
 +  - Install both servers 
 +  - During normal operation, activate the OTC service on the primary and deactivate on the secondary 
 +  - During normal operation, regularly sync 'apacheds-store' from primary to secondary 
 + 
 +=== In Case of Disaster === 
 + 
 +  - Activate OTC service on backup server 
 +  - Run OTC updates (if needed) 
 +  - Boot clients...
  
 If the primary does come up again, either sync back (if config changes make that seem a good idea) or just let it run and shut down the backup service when the clients are down. If the primary does come up again, either sync back (if config changes make that seem a good idea) or just let it run and shut down the backup service when the clients are down.
Line 188: Line 202:
 In the Manager, right-click the thin client and choose 'log' In the Manager, right-click the thin client and choose 'log'
 openthinclient/server/default/data/nfs/root/var/log/*.log openthinclient/server/default/data/nfs/root/var/log/*.log
-openthinclient/wrapper/logs/wrapper.log +openthinclient/wrapper/logs/wrapper.log 
 + 
 +==== Open a Command Prompt (Shell) on the Client ==== 
 + 
 +<file> 
 +<CTRL><ALT><SHIFT><x> 
 +</file>
  
 ===== Notes ===== ===== Notes =====
virtualization/otc.1335812214.txt.gz · Last modified: 2012/04/30 12:56 by gcooper

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki