Highlighted
Absent Member.
Absent Member.
862 views

iPRint Appliance 1.1 Patch 3-- 6.02 client?

We are currently on iPrint ppliance 1.1 patched to 416. That patch
level introduces windows client 6.01, replacing the 6.0 client that
was available earlier.

We have turned off automatic updating of the client due to the problem
we have with end users, under the new client, being asked to interact
with the client the first time the ipp page is accessed after
installing the new client. Starting a printer install results in a
dialog box asking the user to select an application for processing
printer installations, and tick a box to indicate the selection should
be remembered. This happens in both FF and Chrome, but at least with
the 6.01 client printer installations DO complete when done in Chrome.

Our problem stems from the facts that A) our end users are NOT local
admins on their machines, and B) the selection must be made in each
browser individually and C) the dialog and selections are
profile-specific, so have to be done by each and every user touching
the machine. This absolutely does not work for us in a lab setting!

So my questions are:

1. Why is this behavior appearing, and why is it deemed necessary? We
have never had to have ANY end user interaction before other than
their selecting a printer to install from the ipp page.

2. Does the 6.02 client exhibit the same behavior? And is this
behavior going to be an ongoing "feature" in future clients?

During the brief time period when we had auto-update turned on, we
received enough negative feedback on the change in user experience to
trip off a movement to start researching options to iPrint--that
directive has now landed on my desk. I've asked about this client
issue before, in this and other locations, but no one from Novell has
addressed it. Are we the only ones seeing this behavior, is it our
personal 800lb-gorilla in the room that no one wants to talk about, or
???

Information would be appreciated.

Best,

DG
0 Likes
4 Replies
Highlighted
Absent Member.
Absent Member.

Re: iPRint Appliance 1.1 Patch 3-- 6.02 client?

Hi!

I am only guessing, but from what i have seen it may be related to a change
in the plugin api used.
The new client installs a completely different plugin.
Obviously this new plugin has to play by the (security) rules of the
browser.
In Firefox it needs to be an allowed mime-extension in the browser
application settings.

Which are BTW for Firefox stored in the user profile in the file
mimetypes.rdf

So being a non-admin should not be a problem, but you have to add

2 descriptions

<RDF:Description RDF:about="urn:scheme:handler:iprint"
NC:useSystemDefault="true" NC:alwaysAsk="false" />
<RDF:Description RDF:about="urn:scheme:iprint"
NC:value="iprint"><NC:handlerProp
resource="urn:scheme:handler:iprint"/></RDF:Description>
and in the RDF:Seq tag
<RDF:li RDF:resource="urn:scheme:iprint"/>

in the mimetypes.rdf (or you manage the one time configuration setting
manually)

AND you have to allow popups as well.

I do not feel that this change presents a significant impact. Starting stuff
without confirmation by a browser is IMO a very bad thing. I prefer to know
what is going on. So the current solution is much cleaner...

Manually clicking in a browser is far from any good user experience i can
imagine.
Why no automatically install the required printer? (ZCN, iprntcmd, etc.) and
do involve the user not at all?

Georg

>>>

> We are currently on iPrint ppliance 1.1 patched to 416. That patch
> level introduces windows client 6.01, replacing the 6.0 client that
> was available earlier.
>
> We have turned off automatic updating of the client due to the problem
> we have with end users, under the new client, being asked to interact
> with the client the first time the ipp page is accessed after
> installing the new client. Starting a printer install results in a
> dialog box asking the user to select an application for processing
> printer installations, and tick a box to indicate the selection should
> be remembered. This happens in both FF and Chrome, but at least with
> the 6.01 client printer installations DO complete when done in Chrome.
>
> Our problem stems from the facts that A) our end users are NOT local
> admins on their machines, and B) the selection must be made in each
> browser individually and C) the dialog and selections are
> profile-specific, so have to be done by each and every user touching
> the machine. This absolutely does not work for us in a lab setting!
>
> So my questions are:
>
> 1. Why is this behavior appearing, and why is it deemed necessary? We
> have never had to have ANY end user interaction before other than
> their selecting a printer to install from the ipp page.
>
> 2. Does the 6.02 client exhibit the same behavior? And is this
> behavior going to be an ongoing "feature" in future clients?
>
> During the brief time period when we had auto-update turned on, we
> received enough negative feedback on the change in user experience to
> trip off a movement to start researching options to iPrint--that
> directive has now landed on my desk. I've asked about this client
> issue before, in this and other locations, but no one from Novell has
> addressed it. Are we the only ones seeing this behavior, is it our
> personal 800lb-gorilla in the room that no one wants to talk about, or
> ???
>
> Information would be appreciated.
>
> Best,
>
> DG

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: iPRint Appliance 1.1 Patch 3-- 6.02 client?

In a BYOD world, this is definitely a big item--users who make the
wrong initial selection generate a lot of calls to the help desk. We
DO push printers to known equipment that we own--labs, staff desktops,
etc.--but the ability for end users to easily manage their own print
needs has long been a major selling point for iPrint. With the new
dialog box, end users are confronted with "Choose an Application" with
no associated guidance as to how to respond (Most common question to
the help desk: What Application Do I Choose and How DO I Choose
It?"). Given that we are dealing with OUR print infrastructure inside
the confines of our own network--we don't make iPrint available from
outside the firewall--we are much more concerned with reliability and
ease of operation than security wrt iPrint.

Our preference would be to have a way to have the dialog not appear at
all. Second best would be to have the "remember my choice" tick box
already checked, and a line in the dialog telling users to just click
OK unless they are being instructed otherwise by the help desk. I
guess that's where we are going now--to see if we can modify the
dialog box or the images used within so that our end users, especially
those on BYOD laptops, will have enough onboard guidance to tick the
box and OK the selection.

:^(

DG

On Fri, 02 Oct 2015 09:03:49 GMT, "Georg Fritsch" <gfritsch@fcp.at>
wrote:

>Hi!
>
>I am only guessing, but from what i have seen it may be related to a change
>in the plugin api used.
>The new client installs a completely different plugin.
>Obviously this new plugin has to play by the (security) rules of the
>browser.
>In Firefox it needs to be an allowed mime-extension in the browser
>application settings.
>
>Which are BTW for Firefox stored in the user profile in the file
>mimetypes.rdf
>
>So being a non-admin should not be a problem, but you have to add
>
>2 descriptions
>
><RDF:Description RDF:about="urn:scheme:handler:iprint"
>NC:useSystemDefault="true" NC:alwaysAsk="false" />
><RDF:Description RDF:about="urn:scheme:iprint"
>NC:value="iprint"><NC:handlerProp
>resource="urn:scheme:handler:iprint"/></RDF:Description>
>and in the RDF:Seq tag
><RDF:li RDF:resource="urn:scheme:iprint"/>
>
>in the mimetypes.rdf (or you manage the one time configuration setting
>manually)
>
>AND you have to allow popups as well.
>
>I do not feel that this change presents a significant impact. Starting stuff
>without confirmation by a browser is IMO a very bad thing. I prefer to know
>what is going on. So the current solution is much cleaner...
>
>Manually clicking in a browser is far from any good user experience i can
>imagine.
>Why no automatically install the required printer? (ZCN, iprntcmd, etc.) and
>do involve the user not at all?
>
>Georg
>
>>>>

>> We are currently on iPrint ppliance 1.1 patched to 416. That patch
>> level introduces windows client 6.01, replacing the 6.0 client that
>> was available earlier.
>>
>> We have turned off automatic updating of the client due to the problem
>> we have with end users, under the new client, being asked to interact
>> with the client the first time the ipp page is accessed after
>> installing the new client. Starting a printer install results in a
>> dialog box asking the user to select an application for processing
>> printer installations, and tick a box to indicate the selection should
>> be remembered. This happens in both FF and Chrome, but at least with
>> the 6.01 client printer installations DO complete when done in Chrome.
>>
>> Our problem stems from the facts that A) our end users are NOT local
>> admins on their machines, and B) the selection must be made in each
>> browser individually and C) the dialog and selections are
>> profile-specific, so have to be done by each and every user touching
>> the machine. This absolutely does not work for us in a lab setting!
>>
>> So my questions are:
>>
>> 1. Why is this behavior appearing, and why is it deemed necessary? We
>> have never had to have ANY end user interaction before other than
>> their selecting a printer to install from the ipp page.
>>
>> 2. Does the 6.02 client exhibit the same behavior? And is this
>> behavior going to be an ongoing "feature" in future clients?
>>
>> During the brief time period when we had auto-update turned on, we
>> received enough negative feedback on the change in user experience to
>> trip off a movement to start researching options to iPrint--that
>> directive has now landed on my desk. I've asked about this client
>> issue before, in this and other locations, but no one from Novell has
>> addressed it. Are we the only ones seeing this behavior, is it our
>> personal 800lb-gorilla in the room that no one wants to talk about, or
>> ???
>>
>> Information would be appreciated.
>>
>> Best,
>>
>> DG

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: iPRint Appliance 1.1 Patch 3-- 6.02 client?

AFAIK MicroFocus has moved the 'install' functionality from the plugin to
the application level.

To keep the plugin working on the latest browser versions was a constant
fight due to changes in the browsers.
(but it had the advantage of not being presented of any browser specific
interactions to allow the access of local applications directly from a
webpage)

The new application approach solves the 'the iprint plugins does no lonager
work with Chrome version x /Firefox version y' problem, but requires the
browser to invoke a local application.

You could deploy the required changes to user profiles to managed devices.
But i do see a problem with (unmanaged) BYOD scenarios.

I have added an enhancement request/idea.
https://ideas.microfocus.com/MFI/novell-iprint/Idea/Detail/1213
Vote for it.

Georg

>>>

> In a BYOD world, this is definitely a big item--users who make the
> wrong initial selection generate a lot of calls to the help desk. We
> DO push printers to known equipment that we own--labs, staff desktops,
> etc.--but the ability for end users to easily manage their own print
> needs has long been a major selling point for iPrint. With the new
> dialog box, end users are confronted with "Choose an Application" with
> no associated guidance as to how to respond (Most common question to
> the help desk: What Application Do I Choose and How DO I Choose
> It?"). Given that we are dealing with OUR print infrastructure inside
> the confines of our own network--we don't make iPrint available from
> outside the firewall--we are much more concerned with reliability and
> ease of operation than security wrt iPrint.
>
> Our preference would be to have a way to have the dialog not appear at
> all. Second best would be to have the "remember my choice" tick box
> already checked, and a line in the dialog telling users to just click
> OK unless they are being instructed otherwise by the help desk. I
> guess that's where we are going now--to see if we can modify the
> dialog box or the images used within so that our end users, especially
> those on BYOD laptops, will have enough onboard guidance to tick the
> box and OK the selection.
>
> :^(
>
> DG
>
> On Fri, 02 Oct 2015 09:03:49 GMT, "Georg Fritsch" <gfritsch@fcp.at>
> wrote:
>
>>Hi!
>>
>>I am only guessing, but from what i have seen it may be related to a

> change
>>in the plugin api used.
>>The new client installs a completely different plugin.
>>Obviously this new plugin has to play by the (security) rules of the
>>browser.
>>In Firefox it needs to be an allowed mime-extension in the browser
>>application settings.
>>
>>Which are BTW for Firefox stored in the user profile in the file
>>mimetypes.rdf
>>
>>So being a non-admin should not be a problem, but you have to add
>>
>>2 descriptions
>>
>><RDF:Description RDF:about="urn:scheme:handler:iprint"
>>NC:useSystemDefault="true" NC:alwaysAsk="false" />
>><RDF:Description RDF:about="urn:scheme:iprint"
>>NC:value="iprint"><NC:handlerProp
>>resource="urn:scheme:handler:iprint"/></RDF:Description>
>>and in the RDF:Seq tag
>><RDF:li RDF:resource="urn:scheme:iprint"/>
>>
>>in the mimetypes.rdf (or you manage the one time configuration setting
>>manually)
>>
>>AND you have to allow popups as well.
>>
>>I do not feel that this change presents a significant impact. Starting

> stuff
>>without confirmation by a browser is IMO a very bad thing. I prefer to

> know
>>what is going on. So the current solution is much cleaner...
>>
>>Manually clicking in a browser is far from any good user experience i can
>>imagine.
>>Why no automatically install the required printer? (ZCN, iprntcmd, etc.)

> and
>>do involve the user not at all?
>>
>>Georg
>>
>>>>>
>>> We are currently on iPrint ppliance 1.1 patched to 416. That patch
>>> level introduces windows client 6.01, replacing the 6.0 client that
>>> was available earlier.
>>>
>>> We have turned off automatic updating of the client due to the problem
>>> we have with end users, under the new client, being asked to interact
>>> with the client the first time the ipp page is accessed after
>>> installing the new client. Starting a printer install results in a
>>> dialog box asking the user to select an application for processing
>>> printer installations, and tick a box to indicate the selection should
>>> be remembered. This happens in both FF and Chrome, but at least with
>>> the 6.01 client printer installations DO complete when done in Chrome.
>>>
>>> Our problem stems from the facts that A) our end users are NOT local
>>> admins on their machines, and B) the selection must be made in each
>>> browser individually and C) the dialog and selections are
>>> profile-specific, so have to be done by each and every user touching
>>> the machine. This absolutely does not work for us in a lab setting!
>>>
>>> So my questions are:
>>>
>>> 1. Why is this behavior appearing, and why is it deemed necessary? We
>>> have never had to have ANY end user interaction before other than
>>> their selecting a printer to install from the ipp page.
>>>
>>> 2. Does the 6.02 client exhibit the same behavior? And is this
>>> behavior going to be an ongoing "feature" in future clients?
>>>
>>> During the brief time period when we had auto-update turned on, we
>>> received enough negative feedback on the change in user experience to
>>> trip off a movement to start researching options to iPrint--that
>>> directive has now landed on my desk. I've asked about this client
>>> issue before, in this and other locations, but no one from Novell has
>>> addressed it. Are we the only ones seeing this behavior, is it our
>>> personal 800lb-gorilla in the room that no one wants to talk about, or
>>> ???
>>>
>>> Information would be appreciated.
>>>
>>> Best,
>>>
>>> DG

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: iPRint Appliance 1.1 Patch 3-- 6.02 client?

Vote cast!

Thx,

DG

On Thu, 08 Oct 2015 06:58:57 GMT, "Georg Fritsch" <gfritsch@fcp.at>
wrote:

>AFAIK MicroFocus has moved the 'install' functionality from the plugin to
>the application level.
>
>To keep the plugin working on the latest browser versions was a constant
>fight due to changes in the browsers.
>(but it had the advantage of not being presented of any browser specific
>interactions to allow the access of local applications directly from a
>webpage)
>
>The new application approach solves the 'the iprint plugins does no lonager
>work with Chrome version x /Firefox version y' problem, but requires the
>browser to invoke a local application.
>
>You could deploy the required changes to user profiles to managed devices.
>But i do see a problem with (unmanaged) BYOD scenarios.
>
>I have added an enhancement request/idea.
>https://ideas.microfocus.com/MFI/novell-iprint/Idea/Detail/1213
>Vote for it.
>
>Georg
>
>>>>

>> In a BYOD world, this is definitely a big item--users who make the
>> wrong initial selection generate a lot of calls to the help desk. We
>> DO push printers to known equipment that we own--labs, staff desktops,
>> etc.--but the ability for end users to easily manage their own print
>> needs has long been a major selling point for iPrint. With the new
>> dialog box, end users are confronted with "Choose an Application" with
>> no associated guidance as to how to respond (Most common question to
>> the help desk: What Application Do I Choose and How DO I Choose
>> It?"). Given that we are dealing with OUR print infrastructure inside
>> the confines of our own network--we don't make iPrint available from
>> outside the firewall--we are much more concerned with reliability and
>> ease of operation than security wrt iPrint.
>>
>> Our preference would be to have a way to have the dialog not appear at
>> all. Second best would be to have the "remember my choice" tick box
>> already checked, and a line in the dialog telling users to just click
>> OK unless they are being instructed otherwise by the help desk. I
>> guess that's where we are going now--to see if we can modify the
>> dialog box or the images used within so that our end users, especially
>> those on BYOD laptops, will have enough onboard guidance to tick the
>> box and OK the selection.
>>
>> :^(
>>
>> DG
>>
>> On Fri, 02 Oct 2015 09:03:49 GMT, "Georg Fritsch" <gfritsch@fcp.at>
>> wrote:
>>
>>>Hi!
>>>
>>>I am only guessing, but from what i have seen it may be related to a

>> change
>>>in the plugin api used.
>>>The new client installs a completely different plugin.
>>>Obviously this new plugin has to play by the (security) rules of the
>>>browser.
>>>In Firefox it needs to be an allowed mime-extension in the browser
>>>application settings.
>>>
>>>Which are BTW for Firefox stored in the user profile in the file
>>>mimetypes.rdf
>>>
>>>So being a non-admin should not be a problem, but you have to add
>>>
>>>2 descriptions
>>>
>>><RDF:Description RDF:about="urn:scheme:handler:iprint"
>>>NC:useSystemDefault="true" NC:alwaysAsk="false" />
>>><RDF:Description RDF:about="urn:scheme:iprint"
>>>NC:value="iprint"><NC:handlerProp
>>>resource="urn:scheme:handler:iprint"/></RDF:Description>
>>>and in the RDF:Seq tag
>>><RDF:li RDF:resource="urn:scheme:iprint"/>
>>>
>>>in the mimetypes.rdf (or you manage the one time configuration setting
>>>manually)
>>>
>>>AND you have to allow popups as well.
>>>
>>>I do not feel that this change presents a significant impact. Starting

>> stuff
>>>without confirmation by a browser is IMO a very bad thing. I prefer to

>> know
>>>what is going on. So the current solution is much cleaner...
>>>
>>>Manually clicking in a browser is far from any good user experience i can
>>>imagine.
>>>Why no automatically install the required printer? (ZCN, iprntcmd, etc.)

>> and
>>>do involve the user not at all?
>>>
>>>Georg
>>>
>>>>>>
>>>> We are currently on iPrint ppliance 1.1 patched to 416. That patch
>>>> level introduces windows client 6.01, replacing the 6.0 client that
>>>> was available earlier.
>>>>
>>>> We have turned off automatic updating of the client due to the problem
>>>> we have with end users, under the new client, being asked to interact
>>>> with the client the first time the ipp page is accessed after
>>>> installing the new client. Starting a printer install results in a
>>>> dialog box asking the user to select an application for processing
>>>> printer installations, and tick a box to indicate the selection should
>>>> be remembered. This happens in both FF and Chrome, but at least with
>>>> the 6.01 client printer installations DO complete when done in Chrome.
>>>>
>>>> Our problem stems from the facts that A) our end users are NOT local
>>>> admins on their machines, and B) the selection must be made in each
>>>> browser individually and C) the dialog and selections are
>>>> profile-specific, so have to be done by each and every user touching
>>>> the machine. This absolutely does not work for us in a lab setting!
>>>>
>>>> So my questions are:
>>>>
>>>> 1. Why is this behavior appearing, and why is it deemed necessary? We
>>>> have never had to have ANY end user interaction before other than
>>>> their selecting a printer to install from the ipp page.
>>>>
>>>> 2. Does the 6.02 client exhibit the same behavior? And is this
>>>> behavior going to be an ongoing "feature" in future clients?
>>>>
>>>> During the brief time period when we had auto-update turned on, we
>>>> received enough negative feedback on the change in user experience to
>>>> trip off a movement to start researching options to iPrint--that
>>>> directive has now landed on my desk. I've asked about this client
>>>> issue before, in this and other locations, but no one from Novell has
>>>> addressed it. Are we the only ones seeing this behavior, is it our
>>>> personal 800lb-gorilla in the room that no one wants to talk about, or
>>>> ???
>>>>
>>>> Information would be appreciated.
>>>>
>>>> Best,
>>>>
>>>> DG

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.