How to get latest OES iPrint Client

[dchunt]

I am trying to find out if there is a newer iPrint client than the FTF_May2018 client. We have the problem with Symantec and Windows 10 1803 and iPrint.

On the Micro Focus Customer center, I see that there is a June 27 2018, Update 3 Recommended patch for iPrint. After downloading all of the RPM's and exploding them, I can't find the nipp.exe clients so that I can create a ZENworks bundle to install them.

Is the latest iPrint client still the FTF_May2018 client?

Thanks,

Dan

[Anonymous_User]

On 20-07-18 14:26, dchunt wrote:
>
> I am trying to find out if there is a newer iPrint client than the
> FTF_May2018 client. We have the problem with Symantec and Windows 10
> 1803 and iPrint.
>
> On the Micro Focus Customer center, I see that there is a June 27 2018,
> Update 3 Recommended patch for iPrint. After downloading all of the
> RPM's and exploding them, I can't find the nipp.exe clients so that I
> can create a ZENworks bundle to install them.
>
> Is the latest iPrint client still the FTF_May2018 client?
>
> Thanks,
>
> Dan
>
>

- Probably your issue is tid (7022947) . Symantec fixed it.
- latest client is the 6.15:
https://download.microfocus.com/Download?buildid=HUuzEb73S9o~

The FTF was just a workaround to keep iprint working till Symantec
fixed it. Once you update Symantec, you can use the moral 6.15 with no
issues

[dchunt]

I thought we were running the latest version of Symantec Endpoint Protection. What is the version of SEP that fixes this??

Thanks for the quick reply,

Dan

[Anonymous_User]

On 20-07-18 15:14, dchunt wrote:
>
> I thought we were running the latest version of Symantec Endpoint
> Protection. What is the version of SEP that fixes this??
>
> Thanks for the quick reply,
>
> Dan
>
>

tid (7022947)

[dchunt]

Oh man. You mean I have to read the TID??? <G> So I checked and we are running SEP 14.0.3929.1200. That does NOT appear to work with version 6.15 of iPrint, that's why I wanted to make sure I had the May FTF or later.

Dan

[Anonymous_User]

On 20-07-18 17:06, dchunt wrote:
>
> Oh man. You mean I have to read the TID??? <G> So I checked and we are
> running SEP 14.0.3929.1200. That does NOT appear to work with version
> 6.15 of iPrint, that's why I wanted to make sure I had the May FTF or
> later.
>
> Dan
>
>
you need the sonar engine update as well

[smflood]

On 20/07/18 13:26, dchunt wrote:

> On the Micro Focus Customer center, I see that there is a June 27 2018,
> Update 3 Recommended patch for iPrint. After downloading all of the
> RPM's and exploding them, I can't find the nipp.exe clients so that I
> can create a ZENworks bundle to install them.

The various iPrint client installers should be within the
novell-iprint-client package - for example:

$ rpm -qpl novell-iprint-client-6.15.0-0.150.1.noarch.rpm | egrep
nipp.*\.exe
warning:
/data/ISOs/iPrint/novell-iprint-client-6.15.0-0.150.1.noarch.rpm: Header
V3 RSA/SHA256 Signature, key ID 04a29db0: NOKEY
/var/opt/novell/iprint/htdocs/clients/win-7/x86/nipp-s.exe
/var/opt/novell/iprint/htdocs/clients/win-7/x86/nipp-su.exe
/var/opt/novell/iprint/htdocs/clients/win-7/x86/nipp.exe
/var/opt/novell/iprint/htdocs/clients/win-7/x86_64/nipp-s.exe
/var/opt/novell/iprint/htdocs/clients/win-7/x86_64/nipp-su.exe
/var/opt/novell/iprint/htdocs/clients/win-7/x86_64/nipp.exe
/var/opt/novell/iprint/htdocs/clients/win-8/x86/nipp-s.exe
/var/opt/novell/iprint/htdocs/clients/win-8/x86/nipp-su.exe
/var/opt/novell/iprint/htdocs/clients/win-8/x86/nipp.exe
/var/opt/novell/iprint/htdocs/clients/win-8/x86_64/nipp-s.exe
/var/opt/novell/iprint/htdocs/clients/win-8/x86_64/nipp-su.exe
/var/opt/novell/iprint/htdocs/clients/win-8/x86_64/nipp.exe
/var/opt/novell/iprint/htdocs/clients/win-vista/x86/nipp-s.exe
/var/opt/novell/iprint/htdocs/clients/win-vista/x86/nipp-su.exe
/var/opt/novell/iprint/htdocs/clients/win-vista/x86/nipp.exe
/var/opt/novell/iprint/htdocs/clients/win-vista/x86_64/nipp-s.exe
/var/opt/novell/iprint/htdocs/clients/win-vista/x86_64/nipp-su.exe
/var/opt/novell/iprint/htdocs/clients/win-vista/x86_64/nipp.exe
/var/opt/novell/iprint/htdocs/clients/win-xp/nipp-s.exe
/var/opt/novell/iprint/htdocs/clients/win-xp/nipp-sl.exe
/var/opt/novell/iprint/htdocs/clients/win-xp/nipp-sr.exe
/var/opt/novell/iprint/htdocs/clients/win-xp/nipp-su.exe
/var/opt/novell/iprint/htdocs/clients/win-xp/nipp-u.exe
/var/opt/novell/iprint/htdocs/clients/win-xp/nipp.exe

HTH.
--
Simon
Micro Focus Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------

[dchunt]

Mysterious, I just got back to the office. I searched the web and don't see a separate sonar engine update that is available for SEP.

I am running SEP 14.0 RU1 MP2, build 3929. The Sonar Framework that I have is 10.4.1.7 and the Sonar Engine is 11.5.0.166. Are these the current versions for SEP 14? Isn't the latest Sonar engine included in the overall build?

Thanks,

Dan

[Anonymous_User]

On 26-07-18 19:44, dchunt wrote:
>
> Mysterious, I just got back to the office. I searched the web and don't
> see a separate sonar engine update that is available for SEP.
>
> I am running SEP 14.0 RU1 MP2, build 3929. The Sonar Framework that I
> have is 10.4.1.7 and the Sonar Engine is 11.5.0.166. Are these the
> current versions for SEP 14? Isn't the latest Sonar engine included in
> the overall build?
>
> Thanks,
>
> Dan
>
>

Dan, i'm not working for Symantec so contact them with this questions.
This is what the tid says:


Update the Symantec software to SEP version 14.2 Build 758 or later.
Update the Sonar Engine to 11.5.0.166 or later

Both updates are needed.

All customers running this combination have reported positive feedback.
If you still have a BSOD, take a dump and verify that the Symantec
module is the offended module and contact them. I do not know how
Symantec has provided the fix/update to them.