Bug 5185 - Include a profile for the HP Connection Manager ("Manticore")
Summary: Include a profile for the HP Connection Manager ("Manticore")
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client platforms (show other bugs)
Version: 4.2.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.3.0
Assignee: Peter Åstrand
URL:
Keywords: ossman_tester, relnotes
Depends on: 5194
Blocks: 5186 4496
  Show dependency treegraph
 
Reported: 2014-06-10 13:09 CEST by Peter Åstrand
Modified: 2014-10-22 17:03 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description Peter Åstrand cendio 2014-06-10 13:09:07 CEST
Modern versions of HP thin clients has a connection manager system, dubbed "Manticore". This system is used both on the "normal" thin clients (ThinPro, used on t610 etc) as well as the zero clients (SmartZero, used on t410 etc). See http://www8.hp.com/us/en/thin-clients/software-and-os.html. On ThinPro, there's typically an option to create a custom connection, which means that we can launch tlclient anyway, although with a bit of manual configuration. However, on SmartZero, there's no such option, so a Manticore profile is a requirement. This bug is about creating such a profile. Basically, we need to create:

/usr/share/manticore/plugins/thinlinc/config
/usr/share/manticore/plugins/thinlinc/default.xml

Then, at least on the SmartZero, one needs to indicate that this profile should be available, by making sure that the registry key root/ConnectionType/thinlinc/connections exists. I believe this can be done with a command such as:

mclient create root/ConnectionType/thinlinc/connections
mclient commit

Or, we could create & import an XML file.
Comment 1 Peter Åstrand cendio 2014-06-25 15:49:51 CEST
Fixed in r29079,r29102,r29105. 

Should be tested on both "standard" and "zero" versions of HP ThinPro, for example t410 and t610. Also check documentation. 

Time will be reported on bug 4496.
Comment 2 Pierre Ossman cendio 2014-10-01 14:45:39 CEST
The "zero" client works (but see bug 4496). The "standard" one had some issues though:

 - ThinLinc isn't an option in the configuration wizard
 - You cannot delete ThinLinc connections in user mode. Other types do not have this limitation.

I also got an automatic installation UI when I plugged in a USB stick with the .deb files in the root directory. Perhaps we should update our instructions? Note that this only happens on the "standard" device.
Comment 3 Peter Åstrand cendio 2014-10-06 11:20:33 CEST
(In reply to comment #2)

>  - You cannot delete ThinLinc connections in user mode. Other types do not have
> this limitation.

Should be fixed in 29464.


> I also got an automatic installation UI when I plugged in a USB stick with the
> .deb files in the root directory. Perhaps we should update our instructions?
> Note that this only happens on the "standard" device.

This is a new feature in Thinpro 5.x, but we want to stay compatible with earlier versions as well.
Comment 4 Peter Åstrand cendio 2014-10-06 14:16:23 CEST
(In reply to comment #2)
> The "zero" client works (but see bug 4496). The "standard" one had some issues
> though:
> 
>  - ThinLinc isn't an option in the configuration wizard

It turns out that the hptc-config-wizard binary contains a hardcoded list of which connection types to display. Not much we can do about this. Documented in 29465.
Comment 5 Pierre Ossman cendio 2014-10-13 14:45:22 CEST
Works fine now.
Comment 6 Pierre Ossman cendio 2014-10-21 14:46:23 CEST
Breaks client package on Solaris. Solaris runs the postinstall script through sh, which does not support test -e.
Comment 7 Peter Åstrand cendio 2014-10-21 14:51:09 CEST
(In reply to comment #6)
> Breaks client package on Solaris. Solaris runs the postinstall script through
> sh, which does not support test -e.

29528.
Comment 8 Pierre Ossman cendio 2014-10-22 11:23:34 CEST
Works on Solaris now, and still works on the HP client.

I did however notice that we do not remove our entry from that file when uninstalling the client.
Comment 9 Peter Åstrand cendio 2014-10-22 13:49:18 CEST
(In reply to comment #8)

> I did however notice that we do not remove our entry from that file when
> uninstalling the client.

Not necessary, the /etc/SysInfo/pkg_list.conf file includes all potentially installed packages.
Comment 10 Pierre Ossman cendio 2014-10-22 17:03:25 CEST
All done then.

Note You need to log in before you can comment on or make changes to this bug.