This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
virtualization:otc [2012/04/30 12:42] gcooper |
virtualization:otc [2017/01/25 11:53] (current) gcooper |
||
---|---|---|---|
Line 11: | Line 11: | ||
Run with / | Run with / | ||
- | On first use, connect to the realm ' | + | :!: On first use, connect to the realm '' |
===== Supported Hardware ===== | ===== Supported Hardware ===== | ||
Line 17: | Line 17: | ||
http:// | http:// | ||
- | [[computing:monitors|Monitors/ | + | ==== Monitors/ |
+ | |||
+ | See also **[[virtualization:otc_display|Monitors / Displays]]** | ||
===== Virtual Machine ===== | ===== Virtual Machine ===== | ||
Line 25: | 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 | ||
- | * < | + | * < |
- | * you can access the OTC Manager via a web browser | + | * You can access the OTC Manager via a web browser |
* http:// | * http:// | ||
* Package management doesn' | * Package management doesn' | ||
Line 39: | 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 98: | Line 100: | ||
< | < | ||
- | 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 107: | 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 | + | |LDAP password |
- | Select ' | + | Select |
==== Install Packages ==== | ==== Install Packages ==== | ||
Line 152: | Line 154: | ||
http:// | http:// | ||
- | All configuration information is located in the apacheds-store under server\default\data. | + | All configuration information is located in the '' |
- | ===== Notes ===== | + | ==Linux== |
- | Is there a better way to get a failover server?? | + | To save the configuration on the filesystem level create |
- | Well, what I would do: | + | < |
- | - install both servers, | + | / |
- | - activate the OTC service on the primary, deactivate on the secondary, | + | </ |
- | - regularly sync apacheds-store | + | |
- | Now, in case of disaster: | + | ==Windows== |
- | - 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 | + | To save the configuration on the filesystem level create a backup of the following directory: |
- | make that seem a good idea) or just let it run and shut down the backup | + | |
- | service when the clients are down. | + | < |
+ | C: | ||
+ | </ | ||
+ | |||
+ | ===== High Availability ===== | ||
+ | |||
+ | ==== 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 ' | ||
+ | |||
+ | === 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. | ||
===== Troubleshooting ===== | ===== Troubleshooting ===== | ||
Line 184: | Line 202: | ||
In the Manager, right-click the thin client and choose ' | In the Manager, right-click the thin client and choose ' | ||
openthinclient/ | openthinclient/ | ||
- | openthinclient/ | + | openthinclient/ |
+ | |||
+ | ==== Open a Command Prompt (Shell) on the Client ==== | ||
+ | |||
+ | < | ||
+ | < | ||
+ | </ | ||
===== Notes ===== | ===== Notes ===== |